ALLINONE
  1. API
ALLINONE
  • AIO Solution Brief
  • Overview
  • Getting Started
  • Supported Blockchain Networks and Tokens
  • Subaddresses and collection
  • Fund Pool and Withdrawal
  • Funds flow
  • Registration
  • Subaddress transactions
  • API
    • API Basics
    • API Encryption Transmission
    • Create Sub-Address
      POST
    • Create Multiple Subaddresses
      POST
    • Get Sub-Address List
      GET
    • Get Sub-Address Transaction
      GET
    • Create Withdraw Transaction
      POST
    • Direct Withdrawal Transaction
      POST
    • Get Withdraw Transaction details
      GET
    • Get Supported Blockchains and Tokens
      GET
  • Description
    • Collection Instructions
    • Withdrawal Instructions
    • 2-FA Authentication
    • TG Bot
    • Webhook
  • User Experience
    • Overview
    • Registration/Signup
    • Login/Signin
    • Enable TOTP
    • Reset Forgotten Password
    • Subaddress
    • Subaddress transactions
    • Collection Address
    • Fund Pool Addresses
    • Gas Management addresses
    • Settings
      • API Keys and Data encryption
      • IP Whitelisting in API Keys
      • IP Whitelisting - Dashboard
      • Webhooks
  • 用户体验
    • 注册
    • 登录
    • TOTP
    • 忘記密碼
    • 子地址
    • 子地址详情
    • 收款地址概览 (Collection Addresses)
    • 资金池概览 (FundPool Addresses)
    • 燃气管理地址 (Gas Management Addresses)
    • 设置
      • API密钥和数据加密
      • API 密钥中的 IP 白名单
      • AIO仪表板IP白名单
      • 用于通知的 Webhooks
  1. API

API Encryption Transmission

After this function is enabled, API requests and responses are encrypted using the AES-CBC algorithm to ensure data security during transmission.

Unlock Encryption transmission#

Enter the API Key page and switch to the encrypted transmission mode when the function is enabled.
Get the aes_key for encrypted transmission:

AES-CBC(Cipher Block Chaining) mode#

Each plaintext block gets XOR-ed with the previous ciphertext block prior to encryption. An initialization vector is used to make sure each encryption has a different ciphertext result.

Request/Response Format#

The request body and the response body have the same formatting parameters, Request body encryption exists only in POST requests, and the specific parameters are as follows:
iv: The Initialization Vector originally used to create the object.
encrypted_data: Encrypt data with the key and the parameters set at initialization.
They're going to look something like this:
{
	"iv": "7DJ9PJKPXVlPRMaBaf0HAA==", 
	"encrypted_data": "VOuk64ypjBrX2ZweEJgpMWIXtG6Vr0OB5dtfaHjfWYEOIzO3MfNNMlOza63zjG87"
}

Transmission example#

Here Create Sub-Address is used as a reference
The code is for reference only. Adjust it according to the actual service

Implementation in Python#

Implementation in Golang#

Previous
API Basics
Next
Create Sub-Address
Built with