Capital

Endpoint

All Coins' Information (USER_DATA)

Get information of coins (available for deposit and withdraw) for user.

GET

/sapi/v1/capital/config/getall

https://api.binance.com

All Coins' Information (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

All Coins' Information (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight10

All Coins' Information (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

All Coins' Information (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

recvWindow

integer · int64 · max: 60000

Example: 5000

All Coins' Information (USER_DATA) › Responses

200

All Coins' Information

object

coin

string

Example: 1MBABYDOGE

depositAllEnable

boolean

Example: true

withdrawAllEnable

boolean

Example: true

name

string

Example: 1M x BABYDOGE

free

string

Example: 34941.1

locked

string

Example: 0

freeze

string

Example: 0

withdrawing

string

Example: 0

ipoing

string

Example: 0

ipoable

string

Example: 0

storage

string

Example: 0

isLegalMoney

boolean

Example: false

trading

boolean

Example: true

object[]

network

string

Example: BSC

coin

string

Example: 1MBABYDOGE

withdrawIntegerMultiple

string

Example: 0.01

isDefault

boolean

Example: false

depositEnable

boolean

Example: true

withdrawEnable

boolean

Example: true

depositDesc

string

shown only when "depositEnable" is false.

Example:

withdrawDesc

string

shown only when "withdrawEnable" is false.

Example:

specialTips

string

Example:

specialWithdrawTips

string

Example:

name

string

Example: BNB Smart Chain (BEP20)

resetAddressStatus

boolean

Example: false

addressRegex

string

Example: ^(0x)[0-9A-Fa-f]{40}$

memoRegex

string

Example:

withdrawFee

string

Example: 10

withdrawMin

string

Example: 20

withdrawMax

string

Example: 9999999999

withdrawInternalMin

string

Minimum internal transfer amount

Example: 0.01

depositDust

string

Example: 0.01

minConfirm

integer · int64

min number for balance confirmation

Example: 5

unLockConfirm

integer · int64

confirmation number for balance unlock

Example: 0

sameAddress

boolean

Obsoleted, recomment to use withdrawTag

Example: false

withdrawTag

boolean

If the coin needs to provide memo to withdraw

Example: false

estimatedArrivalTime

integer · int64

Example: 1

busy

boolean

Example: false

contractAddressUrl

string

Example: https://bscscan.com/token/

contractAddress

string

Example: 0xc748673057861a797275cd8a068abb95a902e8de

denomination

integer · int64

1 1MBABYDOGE = 1000000 BABYDOGE

Example: 1000000

GET/sapi/v1/capital/config/getall

curl --request GET \
  --url 'https://api.binance.com/sapi/v1/capital/config/getall?timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

[
  {
    "coin": "1MBABYDOGE",
    "depositAllEnable": true,
    "withdrawAllEnable": true,
    "name": "1M x BABYDOGE",
    "free": "34941.1",
    "locked": "0",
    "freeze": "0",
    "withdrawing": "0",
    "ipoing": "0",
    "ipoable": "0",
    "storage": "0",
    "isLegalMoney": false,
    "trading": true,
    "networkList": [
      {
        "network": "BSC",
        "coin": "1MBABYDOGE",
        "withdrawIntegerMultiple": "0.01",
        "isDefault": false,
        "depositEnable": true,
        "withdrawEnable": true,
        "depositDesc": "",
        "withdrawDesc": "",
        "specialTips": "",
        "specialWithdrawTips": "",
        "name": "BNB Smart Chain (BEP20)",
        "resetAddressStatus": false,
        "addressRegex": "^(0x)[0-9A-Fa-f]{40}$",
        "memoRegex": "",
        "withdrawFee": "10",
        "withdrawMin": "20",
        "withdrawMax": "9999999999",
        "withdrawInternalMin": "0.01",
        "depositDust": "0.01",
        "minConfirm": 5,
        "unLockConfirm": 0,
        "sameAddress": false,
        "withdrawTag": false,
        "estimatedArrivalTime": 1,
        "busy": false,
        "contractAddressUrl": "https://bscscan.com/token/",
        "contractAddress": "0xc748673057861a797275cd8a068abb95a902e8de",
        "denomination": 1000000
      }
    ]
  }
]

json

application/json

Deposit Address(supporting network) (USER_DATA)

Fetch deposit address with network.

GET

/sapi/v1/capital/deposit/address

https://api.binance.com

Deposit Address(supporting network) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Deposit Address(supporting network) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight10

Deposit Address(supporting network) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Deposit Address(supporting network) (USER_DATA) › Query Parameters

coin

string · required

coin refers to the parent network address format that the address is using

Example: BTC

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

network

string

Example: null

amount

number · float

Example: 1.0

recvWindow

integer · int64 · max: 60000

Example: 5000

Deposit Address(supporting network) (USER_DATA) › Responses

200

Deposit Address

address

string

Example: 1HPn8Rx2y6nNSfagQBKy27GB99Vbzg89wv

coin

string

Example: BTC

tag

string

Example:

url

string

Example: https://btc.com/1HPn8Rx2y6nNSfagQBKy27GB99Vbzg89wv

Deposit History (supporting network) (USER_DATA)

Fetch deposit history.

GET

/sapi/v1/capital/deposit/hisrec

https://api.binance.com

Deposit History (supporting network) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Deposit History (supporting network) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

Deposit History (supporting network) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Deposit History (supporting network) (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

includeSource

boolean

return sourceAddress field when set to true

Example: false

Default: false

coin

string

Example: BTC

status

integer · enum · int64

0: pending, 1: success, 2: rejected, 6: credited but cannot withdraw, 7: Wrong Deposit, 8: Waiting User confirm

Enum values:

Example: 0

startTime

integer · int64

Default: 90 days from current timestamp

Example: 1623319461670

endTime

integer · int64

Default: present timestamp

Example: 1641782889000

offset

integer · int64

Example: 0

Default: 0

limit

integer · int64 · max: 1000

Example: 1000

Default: 1000

recvWindow

integer · int64 · max: 60000

Example: 5000

txId

string

Example: 1

Deposit History (supporting network) (USER_DATA) › Responses

200

Deposit History

object

id

string

Example: 769800519366885376

amount

string

Example: 0.001

coin

string

Example: BNB

network

string

Example: BNB

status

integer · int64

Example: 1

address

string

Example: bnb136ns6lfw4zs5hg4n85vdthaad7hq5m4gtkgf23

addressTag

string

Example: 101764890

txId

string

Example: 98A3EA560C6B3336D348B6C83F0F95ECE4F1F5919E94BD006E5BF3BF264FACFC

insertTime

integer · int64

Example: 1661493146000

completeTime

integer · int64

represents deposit completion datetime, available for deposits after 6-Mar-2025.

Example: 1661493146000

transferType

integer · int64

Example: 0

confirmTimes

string

Example: 1/1

unlockConfirm

integer · int64

Example: 0

walletType

integer · int64

Example: 0

travelRuleStatus

integer · int64

0: travel rule not required OR info already provided and funds ready to use, 1: travel rule required to provide deposit info

Example: 0

Fetch deposit address list with network (USER_DATA)

Fetch deposit address list with network.

GET

/sapi/v1/capital/deposit/address/list

https://api.binance.com

Fetch deposit address list with network (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Fetch deposit address list with network (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight10

Fetch deposit address list with network (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Fetch deposit address list with network (USER_DATA) › Query Parameters

coin

string · required

Coin name

Example: BTC

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

network

string

If network is not send, return with default network of the coin. You can get network and isDefault in networkList in the response of Get /sapi/v1/capital/config/getall

Example: null

Fetch deposit address list with network (USER_DATA) › Responses

200

Fetch deposit address list with network

object

coin

string

coin here means network address space, ETH for all EVM-like network

Example: ETH

address

string

Example: 0xD316E95Fd9E8E237Cb11f8200Babbc5D8D177BA4

tag

string

Example:

isDefault

integer · int64

'isDefault' is 1 means the address is default, same as shown in the app.

Example: 0

Fetch withdraw address list (USER_DATA)

Fetch withdraw address list

GET

/sapi/v1/capital/withdraw/address/list

https://api.binance.com

Fetch withdraw address list (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Fetch withdraw address list (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight10

Fetch withdraw address list (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Fetch withdraw address list (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

Fetch withdraw address list (USER_DATA) › Responses

200

Fetch withdraw address list

object

address

string

Example: 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa

addressTag

string

Example:

coin

string

Example: BTC

name

string

is a user-defined name

Example: Satoshi

network

string

Example: BTC

origin

string

if originType != 'others', this value is blank, otherwise the origin is manually filled in by the user

Example: bla

originType

string

Address source type, including but not limited to: type Exchange Address: Binance, CoinBase, HTX, Bitfinex, OKX, Bithumb, Kraken, Kucoin, Gemini, Bitget, Bybit, Upbit, Gate.io; type Wallet Address: Binance Web3 Wallet, Trust Wallet, MetaMask, Rabby Wallet, Phantom, OKX Web 3 Wallet, Coinbase Wallet, Bitget Wallet; type Others: others(multilanguage support)

Example: others

whiteStatus

boolean

Is it whitelisted

Example: true

Fetch withdraw quota (USER_DATA)

Fetch withdraw quota

GET

/sapi/v1/capital/withdraw/quota

https://api.binance.com

Fetch withdraw quota (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Fetch withdraw quota (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight10

Fetch withdraw quota (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Fetch withdraw quota (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

Fetch withdraw quota (USER_DATA) › Responses

200

Fetch withdraw quota

wdQuota

string

User's total withdrawal quota in the past 24 hours (including on-chain withdrawal and internal transfer), unit in USD

Example: 10000

usedWdQuota

string

User withdrawal quota usage in the past 24 hours, unit in USD

Example: 1000

One click arrival deposit apply (for expired address deposit) (USER_DATA)

Apply deposit credit for expired address (One click arrival)

POST

/sapi/v1/capital/deposit/credit-apply

https://api.binance.com

One click arrival deposit apply (for expired address deposit) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

One click arrival deposit apply (for expired address deposit) (USER_DATA) › Request Weight

This endpoint consumes IP-based request weight. Heavier endpoints consume more of your IP rate limit capacity.

Learn more in the Rate limits section.

IP Weight1

One click arrival deposit apply (for expired address deposit) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

One click arrival deposit apply (for expired address deposit) (USER_DATA) › Request Body

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

depositId

integer · int64

Deposit record Id, priority use

Example: 1

txId

string

Deposit txId, used when depositId is not specified

Example: 1

subAccountId

string

Sub-accountId of Cloud user

Example: 1

subUserId

integer · int64

Sub-userId of parent user

Example: 1

One click arrival deposit apply (for expired address deposit) (USER_DATA) › Responses

200

One click arrival deposit apply

code

string

Example: 000000

message

string

Example: success

data

boolean

Example: true

success

boolean

Example: true

Withdraw (USER_DATA)

Submit a withdraw request

POST

/sapi/v1/capital/withdraw/apply

https://api.binance.com

Withdraw (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Withdraw (USER_DATA) › Request Weight

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight900

Withdraw (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Withdraw (USER_DATA) › Request Body

coin

string · required

Example: BTC

address

string · required

Withdrawal address

Example: null

amount

number · float · required

Amount

Example: 1.0

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

withdrawOrderId

string

client side id for withdrawal, if provide here, can be used in GET /sapi/v1/capital/withdraw/history for query.

Example: 1

network

string

Withdrawal network

Example: null

addressTag

string

Secondary address identifier for coins like XRP,XMR etc.

Example: null

transactionFeeFlag

boolean

When making internal transfer, true for returning the fee to the destination account; false for returning the fee back to the departure account. Default false.

Example: true

name

string

Example: null

walletType

integer · int64

The wallet type for withdraw，0-spot wallet ，1-funding wallet. Default walletType is the current "selected wallet" under wallet->Fiat and Spot/Funding->Deposit

Example: 0

recvWindow

integer · int64 · max: 60000

Example: 5000

Withdraw (USER_DATA) › Responses

200

Withdraw

id

string

Example: 7213fea8e94b4a5593d507237e5a555b

Withdraw History (supporting network) (USER_DATA)

Fetch withdraw history

GET

/sapi/v1/capital/withdraw/history

https://api.binance.com

Withdraw History (supporting network) (USER_DATA) › Authorization

This is a signed endpoint and a signature must be included in the request parameters.Learn more about how to generate a valid signature in the Endpoint Security Type

Withdraw History (supporting network) (USER_DATA) › Request Weight

This endpoint consumes account (UID)-based request weight. Heavier endpoints consume more of your account rate limit capacity.

Learn more in the Rate limits section.

Account Weight

18000 (10 requests per second)

Withdraw History (supporting network) (USER_DATA) › Headers

X-MBX-APIKEY

string · required

An API Key is required to access this endpoint and must be included in the request headers. To create an API Key, refer to: https://www.binance.com/en/support/faq/detail/360002502072.

Example: API_KEY

Withdraw History (supporting network) (USER_DATA) › Query Parameters

timestamp

integer · int64 · required

Unix timestamp in milliseconds used to sign the request. The value must reflect the current client time and is validated by the server for signed endpoints.

Example: 1770736694138

coin

string

Example: BTC

withdrawOrderId

string

client side id for withdrawal, if provided in POST /sapi/v1/capital/withdraw/apply, can be used here for query.

Example: 1

status

integer · int64

0(0: Email Sent, 2: Awaiting Approval 3: Rejected 4: Processing 6: Completed)

Example: 0

offset

integer · int64

Default: 0

Example: 0

limit

integer · int64 · max: 1000

Example: 1000

Default: 1000

idList

string

id list returned in the response of POST /sapi/v1/capital/withdraw/apply, separated by ,

Example: null

startTime

integer · int64

Default: 90 days from current timestamp

Example: 1623319461670

endTime

integer · int64

Default: present timestamp

Example: 1641782889000

recvWindow

integer · int64 · max: 60000

Example: 5000

Withdraw History (supporting network) (USER_DATA) › Responses

200

Withdraw History

object

id

string

Withdrawal id in Binance

Example: b6ae22b3aa844210a7041aee7589627c

amount

string

withdrawal amount

Example: 8.91000000

transactionFee

string

transaction fee

Example: 0.004

coin

string

Example: USDT

status

integer · int64

Example: 6

address

string

Example: 0x94df8b352de7f46f64b01d3666bf6e936e44ce60

txId

string

withdrawal transaction id

Example: 0xb5ef8c13b968a406cc62a93a8bd80f9e9a906ef1b3fcf20a2e48573c17659268

applyTime

string

UTC time

Example: 2019-10-12 11:12:02

network

string

Example: ETH

transferType

integer · int64

1 for internal transfer, 0 for external transfer

Example: 0

withdrawOrderId

string

will not be returned if there's no withdrawOrderId for this withdraw.

Example: WITHDRAWtest123

info

string

reason for withdrawal failure

Example: The address is not valid. Please confirm with the recipient

confirmNo

integer · int64

confirm times for withdraw

Example: 3

walletType

integer · int64

1: Funding Wallet 0 Wallet

Example: 1

txKey

string

Example:

completeTime

string

complete UTC time when user's asset is deduct from withdrawing, only if status = 6(success)

Example: 2023-03-23 16:52:41

GET/sapi/v1/capital/withdraw/history

curl --request GET \
  --url 'https://api.binance.com/sapi/v1/capital/withdraw/history?timestamp=%3Cnumber%3E' \
  --header 'X-MBX-APIKEY: <string>'

Example Responses

[
  {
    "id": "b6ae22b3aa844210a7041aee7589627c",
    "amount": "8.91000000",
    "transactionFee": "0.004",
    "coin": "USDT",
    "status": 6,
    "address": "0x94df8b352de7f46f64b01d3666bf6e936e44ce60",
    "txId": "0xb5ef8c13b968a406cc62a93a8bd80f9e9a906ef1b3fcf20a2e48573c17659268",
    "applyTime": "2019-10-12 11:12:02",
    "network": "ETH",
    "transferType": 0,
    "withdrawOrderId": "WITHDRAWtest123",
    "info": "The address is not valid. Please confirm with the recipient",
    "confirmNo": 3,
    "walletType": 1,
    "txKey": "",
    "completeTime": "2023-03-23 16:52:41"
  }
]

json

application/json