Retrieve cryptocurrency deposit history for a Binance account, with optional filters for asset, status and time range.
/sapi/v1/capital/deposit/hisrec
This endpoint returns cryptocurrency deposit records associated with a Binance account. It can be used to monitor incoming blockchain deposits and reconcile them with internal application records.
The request can optionally be filtered by cryptocurrency, deposit status and a specific time range. This makes the endpoint useful for applications that need to periodically synchronize deposit activity.
Parameters accepted by the endpoint.
| Parameter | Type | Required | Description |
|---|---|---|---|
coin |
STRING | Optional | Cryptocurrency symbol used to filter deposit records, such as BTC, ETH or USDT. |
status |
INT | Optional |
Deposit status filter: 0 pending,
6 credited but cannot withdraw,
1 success.
|
startTime |
LONG | Optional | Start of the requested time range as a UTC timestamp in milliseconds. |
endTime |
LONG | Optional | End of the requested time range as a UTC timestamp in milliseconds. |
offset |
INT | Optional | Number of records to skip before returning results. |
limit |
INT | Optional | Maximum number of records returned. Default is 1000 and the maximum is 1000. |
recvWindow |
LONG | Optional | Defines the period during which the signed request remains valid. |
timestamp |
LONG | Required | Current request timestamp in milliseconds. |
When using startTime and endTime,
make sure the requested interval complies with Binance API
time-range limitations. For historical synchronization,
applications should process deposits in manageable time
windows.
Example request using cURL.
curl -X GET \
'https://api.binance.com/sapi/v1/capital/deposit/hisrec?coin=USDT×tamp=YOUR_TIMESTAMP&signature=YOUR_SIGNATURE' \
-H 'X-MBX-APIKEY: YOUR_API_KEY'
Never place your Binance API secret in browser-side code, public repositories or client applications where it can be exposed.
Example response returned by the API.
[
{
"amount": "8.73234",
"coin": "BNB",
"network": "BSC",
"status": 1,
"address": "0xd709f9d0bbc6b0e746a13142dfe353086edf87c2",
"addressTag": "",
"txId": "0xa9ebf3f4f60bc18bd6bdf4616ff8ffa14ef93a08fe79cad40519b31ea1044290",
"insertTime": 1638342348000,
"transferType": 0,
"confirmTimes": "0/0"
}
]
| Field | Type | Description |
|---|---|---|
amount |
STRING | Amount of cryptocurrency deposited into the Binance account. |
coin |
STRING | Cryptocurrency symbol associated with the deposit. |
network |
STRING | Blockchain network used for the deposit. |
status |
INT | Current status of the deposit. |
address |
STRING | Binance deposit address associated with the transaction. |
addressTag |
STRING | Additional destination identifier when required by the selected asset or network. |
txId |
STRING | Blockchain transaction identifier associated with the deposit. |
insertTime |
LONG | Time when the deposit record was detected, represented as a timestamp in milliseconds. |
transferType |
INT | Indicates the type of transfer associated with the deposit record. |
confirmTimes |
STRING | Blockchain confirmation progress for the deposit. |
Typical flow for retrieving Binance deposit history.
For automated deposit monitoring, store the transaction ID and deposit status in your application database. This makes it possible to detect new deposits and track confirmation progress without repeatedly processing the same records.
Monitor incoming cryptocurrency deposits and their confirmation status.
Match Binance deposit records with transactions stored in an external application or accounting system.
Automatically detect new deposits and trigger application workflows after confirmation.
This article is part of our complete learning guide covering professional cross-exchange cryptocurrency arbitrage.
Explore the Spot Arbitrage Guide →This article is part of our complete learning guide covering Binance P2P automation, merchant tools, and automated trading.
Explore the Binance P2P Automation Guide →