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

Get Transfer History between Sub-Wallet and Prime Wallet

GET/open-api/v1/subwallet/transfer/history

This method allows you to get transfer history between Prime Wallet and Sub Wallets (Only applicable to Prime wallet structure)

API Key permission group : Enable Enquiry

Request

Query Params
walletId
string 
required

Wallet id

Example:
1325589336357780500
coinSymbol
string 
optional

Coin Symbol (in capital letters)

Example:
ETH
direction
integer 
optional

Transfer Direction:10: prime wallet -> sub wallet, 20: sub wallet -> prime wallet, 30: sub wallet -> sub wallet, 40: prime wallet -> prime wallet

Example:
20
status
integer 
optional

Status:10: Pending; 20: Processing; 30: Send success; 99: Failed

Example:
10
startTime
integer 
required

Start time (timestamp in milliseconds)

Example:
1640995200000
endTime
integer 
required

End time (timestamp in milliseconds)

Example:
1640995200000
pageLimit
integer 
optional

Page limit, min: 1, max: 500

Example:
25
pageNo
integer 
optional

Page number, min: 1

Example:
1
timestamp
integer 
required

Current Timestamp in millisecond

Example:
1640995200000
Header Params
open-apikey
string 
required

OpenAPI key string

signature
string 
required

Signature of the request

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
object  | null 
optional

response data, maybe null

data
array[object (Transfer) {9}] 
required
totalPage
integer 
required
pageNo
integer 
required
pageLimit
integer 
required
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": {
    "data": [
      {
        "orderViewId": "24073634100151542086240001",
        "direction": 40,
        "fromWalletId": 370387818289426400,
        "toWalletId": 327283192690466800,
        "createTime": 1715100144000,
        "coinSymbol": "BTC",
        "amount": "151.00000000",
        "status": 20,
        "requestId": null
      },
      {
        "orderViewId": "24073601652851542064000001",
        "direction": 10,
        "fromWalletId": 370387818289426400,
        "toWalletId": 377611271366909950,
        "createTime": 1715825610000,
        "coinSymbol": "USDT",
        "amount": "1.00000000",
        "status": 30,
        "requestId": "7"
      }
    ],
    "totalPage": 1,
    "pageNo": 1,
    "pageLimit": 25
  },
  "code": "000000",
  "message": "Success"
}
Last modified: 6 months ago