Ceffu OpenAPI Documentation Platform
  • ChangeLog
  • Getting Started
  • System Endpoints
  • Wallet Endpoints
  • Sub-Wallet Endpoints
    • Get Sub-Wallet List (V2)GET
    • Get Sub-Wallet Asset DetailsGET
    • Get Sub-Wallet Asset SummaryGET
    • Get Sub-Wallet Deposit AddressGET
    • Get Deposit History under Sub-WalletGET
    • Get Deposit Address List under Prime Wallet GET
    • Get Sub-Wallet Deposit History By Prime WalletGET
    • Get Transfer History between Sub-Wallet and Prime WalletGET
    • Get Transaction Details of Prime Wallet Internal TransferGET
    • Create Sub-WalletPOST
    • Update Sub-Wallet DetailsPOST
    • Transfer between Sub Wallet and Prime WalletPOST
  • MirrorX Endpoints
  • Webhook
  • Archive
logoPowered by Apifox
  1. Sub-Wallet Endpoints

Transfer between Sub Wallet and Prime Wallet

POST/open-api/v1/subwallet/transfer

This method allows you to transfer asset between Sub Wallet and Prime Wallet
Restriction: Only applicable to Prime wallet structure.
Sub-wallets with auto-collection enabled do not support transfers. If you wish to perform transfers, please disable the auto-collection feature first.

API Key permission group : Enable Internal Transfer

Request

Header Params
open-apikey
string 
required

OpenAPI key string

signature
string 
required

Signature of the request

Body Params application/json
coinSymbol
string 
Coin symbol
required

Coin symbol

Example:
ETH
amount
number 
Transfer amount
required

Transfer amount

Example:
10.2
fromWalletId
integer <int64>
From wallet ID
required

Source wallet id

Example:
1325589336357780500
toWalletId
integer <int64>
To wallet ID
required

Destination wallet id

Example:
1325589336357780500
requestId
integer <int64>
Client request identifier
required

Client provided Unique Identifier. (Max 70 characters)

Example:
1640995200000
timestamp
integer <int64>
Current timestamp in millisecond
required

Current timestamp in millisecond

Example:
1640995200000
Example
{
  "coinSymbol": "ETH",
  "amount": 10.2,
  "fromWalletId": 1325589336357780500,
  "toWalletId": 1325589336357780500,
  "requestId": 1640995200000,
  "timestamp": 1640995200000
}

Request samples

Responses

The operation succeeded(200)
Business error(200)
The client request is invalid(400)
Authentication failed (e.g., invalid token specified by the Authorization header)(401)
Authentication failed, but the operation is not allowed(403)
Requested resource does not exist(404)
Client request rate exceeded the limit(429)
System error(500)
The operation succeeded
HTTP Code: 200
Content Type : JSONapplication/json
Data Schema
data
optional

response data, maybe null

Any of
orderViewId
string 
required

Transfer transaction Id

status
enum<integer> 
TransactionStatus
required
Allowed values:
1020304099
direction
enum<integer> 
TransferDirection
required
Allowed values:
1020304070
code
string 
required

'000000' indicates success, while any others indicate failure.

message
string 
required

When the code is '000000' (success), it represents the details of the response. Otherwise, it represents the details of the error.

Example
{
  "data": {
    "orderViewId": "24073601652851542064000001",
    "status": 10,
    "direction": 10
  },
  "code": "000000",
  "message": "Success"
}
Last modified: 7 months ago