Get Sub Deposit Records (on-chain)

Query subaccount's deposit records by main UID's API key.

tip

endTime - startTime should be less than 30 days. Queries for the last 30 days worth of records by default.

HTTP Request

GET /v5/asset/deposit/query-sub-member-record

Request Parameters

Parameter	Required	Type	Comments
id	false	string	Internal ID: Can be used to uniquely identify and filter the deposit. When combined with other parameters, this field takes the highest priority
txID	false	string	Transaction ID: Please note that data generated before Jan 1, 2024 cannot be queried using txID
subMemberId	true	string	Sub UID
coin	false	string	Coin, uppercase only
startTime	false	integer	The start timestamp (ms) Note: the query logic is actually effective based on second level
endTime	false	integer	The end timestamp (ms) Note: the query logic is actually effective based on second level
limit	false	integer	Limit for data size per page. [1, 50]. Default: 50
cursor	false	string	Cursor. Use the nextPageCursor token from the response to retrieve the next page of the result set

Response Parameters

Parameter	Type	Comments
rows	array	Object
> id	string	Unique ID
> coin	string	Coin
> chain	string	Chain
> amount	string	Amount
> txID	string	Transaction ID
> status	integer	Deposit status
> toAddress	string	Deposit target address
> tag	string	Tag of deposit target address
> depositFee	string	Deposit fee
> successAt	string	Last updated time
> confirmations	string	Number of confirmation blocks
> txIndex	string	Transaction sequence number
> blockHash	string	Hash number on the chain
> batchReleaseLimit	string	The deposit limit for this coin in this chain. "-1" means no limit
> depositType	string	The deposit type. 0: normal deposit, 10: the deposit reaches daily deposit limit, 20: abnormal deposit
> fromAddress	string	From address of deposit, only shown when the deposit comes from on-chain and from address is unique, otherwise gives ""
> taxStatus	string	This field is used for tax purposes by Bybit EU (Austria) users 0: No reporting required 1: Reporting pending 2: Reporting completed
> taxDepositRecordsId	string	This field is used for tax purposes by Bybit EU (Austria) users
nextPageCursor	string	Refer to the cursor request parameter

---

Request Example

HTTP

GET /v5/asset/deposit/query-sub-member-record?coin=USDT&limit=1&subMemberId=592334 HTTP/1.1
Host: api-testnet.bybit.com
X-BAPI-SIGN: XXXXX
X-BAPI-API-KEY: xxxxxxxxxxxxxxxxxx
X-BAPI-TIMESTAMP: 1672192441294
X-BAPI-RECV-WINDOW: 5000

Python

from pybit.unified_trading import HTTP
session = HTTP(
    testnet=True,
    api_key="xxxxxxxxxxxxxxxxxx",
    api_secret="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
)
print(session.get_sub_deposit_records(
    coin="USDT",
    limit=1,
    subMemberId=592334,
))

Node.js

const { RestClientV5 } = require('bybit-api');

const client = new RestClientV5({
  testnet: true,
  key: 'xxxxxxxxxxxxxxxxxx',
  secret: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
});

client
  .getSubAccountDepositRecords({
    coin: 'USDT',
    limit: 1,
    subMemberId: '592334',
  })
  .then((response) => {
    console.log(response);
  })
  .catch((error) => {
    console.error(error);
  });

Response Example

{
    "retCode": 0,
    "retMsg": "success",
    "result": {
        "rows": [],
        "nextPageCursor": ""
    },
    "retExtInfo": {},
    "time": 1672192441742
}