Change Log
Important Documentation Notice
Binance has launched its new API Documentation Portal. The existing GitHub API documentation is now deprecated(2024-06-17) and set to go offline in the upcoming few months following user migration; the exact date will be determined and communicated in due course.
During this transition phase, both sites will be maintained. However, any new services will only be published in the new portal moving forward.
Here's a reference table of the links for the current and new API documentation:
2024-10-18
REST and WebSocket API:
- Reminder that SBE 1:0 schema will be disabled on 2024-10-25, 6 months after being deprecated, as per our SBE policy.
- The SBE lifecycle for Prod has been updated to reflect this change.
2024-10-17
Changes to Exchange Information (i.e. GET /api/v3/exchangeInfo
from REST and exchangeInfo
for WebSocket API).
- A new optional parameter
showPermissionSets
can be used to hide the permissions frompermissionsSets
; This can be used for a reduced payload size. - A new optional parameter
symbolStatus
can now be used to only show symbols with the specified status. (e.g.TRADING
,HALT
,BREAK
).
2024-09-02
- Spot Unfilled Order Count Rules have been updated to explain how to decrease your unfilled order count when placing orders.
2024-08-16
Notice: The changes below are being rolled out gradually, and may take approximately a week to complete.
SPOT API: * New error message have been added when quote quantity market orders (aka reverse market orders) are rejected in low-liquidity situations.
2024-07-22
SPOT API
- Fixed a bug where klines had incorrect timestamps.
- REST API:
GET /api/v3/klines
andGET /api/v3/uiKlines
withtimeZone
parameter - WebSocket API:
klines
anduiKlines
withtimeZone
parameter - WebSocket Streams:
<symbol>@kline_<interval>@+08:00
streams
- REST API:
2024-06-11
- On June 11, 05:00 UTC, One-Triggers-the-Other (OTO) orders and One-Triggers-a-One-Cancels-The-Other (OTOCO) orders will be enabled. (Note this may take a few hours to be rolled out to all servers.)
For more information, please refer to the following pages: - On June 18, 05:00 UTC, Buyer order ID
b
and Seller order IDa
will be removed from the Trade Streams (i.e.<symbol>@trade
). (Note that this may take a few hours to be rolled out to all servers.)- WebSocket Streams has been updated regarding this change.
- To monitor if your order was part of a trade, please listen to the User Data Streams.
2024-06-06
This will be available by June 6, 11:59 UTC.
SPOT API
orderRateLimitExceededMode
has been added toPOST /api/v3/order/cancelReplace
.
2024-06-04
- New Copy Trading Endpoint:
GET /sapi/v1/copyTrading/futures/userStatus
: get futures lead trader statusGET /sapi/v1/copyTrading/futures/leadSymbol
: get futures lead trading symbol whitelist
- Wallet Endpoints adjustment: for internal transfers, the txid prefix has been replaced to “Off-chain transfer”on 28 May 2024. “internal transfer” flag is no longer available in the TXID field, including historical transactions, the following endpoints are impacted:
GET /sapi/v1/capital/deposit/hisrec
GET /sapi/v1/capital/withdraw/history
GET /sapi/v1/capital/deposit/subHisrec
2024-05-30
WebSocket Streams
- Kline/Candlestick streams can now support a UTC+8:00 timezone offset. (e.g.
btcusdt@kline_1d@+08:00
)
2024-05-22
- Update Sub Account Endpoint:
GET /sapi/v1/sub-account/transfer/subUserHistory
: update response fieldfromAccountType
andtoAccountType
. Return USDT_FUTURE/COIN_FUTURE in order to differentiate 2 futures wallets.
- New Wallet Endpoint:
GET /sapi/v1/account/info
: To fetch the “VIP Level”, “whether Margin account is enabled” and “whether Futures account is enabled”
2024-04-18
- New Wallet Endpoint:
GET /sapi/v1/capital/withdraw/address/list
: Fetch withdraw address list
2024-04-10
The following changes have been postponed to take effect on April 25, 05:00 UTC
- Symbol permission information in Exchange Information responses has moved from field
permissions
to fieldpermissionSets
. - Field
permissions
will be empty and will be removed in a future release. - Previously,
"permissions":["SPOT","MARGIN"]
meant that you could place an order on the symbol if your account hadSPOT
orMARGIN
permissions.
The equivalent is"permissionSets":[["SPOT","MARGIN"]]
. (Note the extra set of square brackets.)
Each array of permissions inside thepermissionSets
array is called a "permission set". - Symbol permissions can now be more complex.
"permissionSets":[["SPOT","MARGIN"],["TRD_GRP_004","TRD_GRP_005"]]
means that you may place an order on the symbol if your account has SPOT or MARGIN permissions andTRD_GRP_004
orTRD_GRP_005
permissions.
There may be an arbitrary number of permission sets in a symbol'spermissionSets
. otoAllowed
will now appear onGET /api/v3/exchangeInfo
, that indicates if One-Triggers-the-Other (OTO) orders are supported on that symbol.
SBE
- A new schema 2:0 spot_2_0.xml has been released. The current schema 1:0 spot_1_0.xml will thus be deprecated, and retired from the API in 6 months as per our schema deprecation policy.
- When using schema 1:0 on REST API or WebSocket API, group "permissions" in message "ExchangeInfoResponse" will always be empty. Upgrade to schema 2:0 to find permission information in group "permissionSets". See General changes above for more details.
- Deprecated OCO requests will still be supported by the latest schema.
- Note that trying to use schema 2:0 before it is actually released will result in an error.
2024-04-08
Update Gift Card Endpoint:
POST /sapi/v1/giftcard/createCode
: add response fieldexpiredTime
POST /sapi/v1/giftcard/buyCode
: add response fieldexpiredTime
Update Wallet Endpoint:
GET /sapi/v1/capital/config/getall
: will remove response fieldresetAddressStatus
on 2024-05-16
2024-04-02
Notice: The changes below are being rolled out gradually, and will take approximately a week to complete.
GET /api/v3/account
has a new optional parameteromitZeroBalances
, which if enabled hides all zero balances.- The weight of the following requests has been increased from 10 to 25 (This will take effect on April 4, 2024):
GET /api/v3/trades
GET /api/v3/historicalTrades
- The
POST /api/v3/order/oco
endpoint is now deprecated on the REST API. You should use the newPOST /api/v3/orderList/oco
endpoint instead. Note that this new endpoint uses different parameters.
User Data Stream:
- New event
listenKeyExpired
that will be emitted in the streams if thelistenKey
expired.
The following will take effect approximately a week after the release date:
- Symbol permission information in Exchange Information responses has moved from field
permissions
to fieldpermissionSets
. - Field
permissions
will be empty and will be removed in a future release. - Previously,
"permissions":["SPOT","MARGIN"]
meant that you could place an order on the symbol if your account hadSPOT
orMARGIN
permissions.
The equivalent is"permissionSets":[["SPOT","MARGIN"]]
. (Note the extra set of square brackets.)
Each array of permissions inside thepermissionSets
array is called a "permission set". - Symbol permissions can now be more complex.
"permissionSets":[["SPOT","MARGIN"],["TRD_GRP_004","TRD_GRP_005"]]
means that you may place an order on the symbol if your account has SPOT or MARGIN permissions andTRD_GRP_004
orTRD_GRP_005
permissions.
There may be an arbitrary number of permission sets in a symbol'spermissionSets
. otoAllowed
will now appear onGET /api/v3/exchangeInfo
, that indicates if One-Triggers-the-Other (OTO) orders are supported on that symbol.
SBE
- A new schema 2:0 spot_2_0.xml has been released. The current schema 1:0 spot_1_0.xml will thus be deprecated, and retired from the API in 6 months as per our schema deprecation policy.
- When using schema 1:0 on REST API or WebSocket API, group "permissions" in message "ExchangeInfoResponse" will always be empty. Upgrade to schema 2:0 to find permission information in group "permissionSets". See General changes above for more details.
- Deprecated OCO requests will still be supported by the latest schema.
- Note that trying to use schema 2:0 before it is actually released will result in an error.
2024-02-28
This will take effect on March 5, 2024.
Simple Binary Encoding (SBE) will be added to the live exchange, both for the Rest API and WebSocket API on SPOT.
For more information on SBE, please refer to the FAQ.
2024-02-27
Following the latest upgrade on Binance Loans
- Binance Loans has added the following /v2 SAPI endpoints at 2024-02-27 08:00 (UTC). Users may utilize v2 SAPI endpoints to place, repay, and manage new Binance Loans (Flexible Rate) orders created after 2024-02-27 08:00 (UTC).
POST /sapi/v2/loan/flexible/borrow
GET /sapi/v2/loan/flexible/ongoing/orders
GET /sapi/v2/loan/flexible/borrow/history
POST /sapi/v2/loan/flexible/repay
GET /sapi/v2/loan/flexible/repay/history
POST /sapi/v2/loan/flexible/adjust/ltv
GET /sapi/v2/loan/flexible/ltv/adjustment/history
GET /sapi/v2/loan/flexible/loanable/data
GET /sapi/v2/loan/flexible/collateral/data
- In addition, Binance Loans will be retiring its /v1 SAPI endpoints at the following timings:
- At 2024-02-27 08:00 (UTC):
POST /sapi/v1/loan/flexible/borrow
GET /sapi/v1/loan/flexible/loanable/data
GET /sapi/v1/loan/flexible/collateral/data
- At 2024-04-24 03:00 (UTC):
GET /sapi/v1/loan/flexible/ongoing/orders
POST /sapi/v1/loan/flexible/repay
POST /sapi/v1/loan/flexible/adjust/ltv
- Binance Loans will also continue to maintain the following /v1 SAPI endpoints for users to check their Binance Loans (Flexible Rate) order history before 2024-02-27 08:00 (UTC).
GET /sapi/v1/loan/flexible/borrow/history
GET /sapi/v1/loan/flexible/repay/history
GET /sapi/v1/loan/flexible/ltv/adjustment/history
- Binance Loans has added the following /v2 SAPI endpoints at 2024-02-27 08:00 (UTC). Users may utilize v2 SAPI endpoints to place, repay, and manage new Binance Loans (Flexible Rate) orders created after 2024-02-27 08:00 (UTC).
2024-02-23
- New Endpoints for Convert:
GET /sapi/v1/dci/product/list
: Get Dual Investment product listPOST /sapi/v1/dci/product/subscribe
: Subscribe Dual Investment productsGET /sapi/v1/dci/product/positions
: Get Dual Investment positions (batch)GET /sapi/v1/dci/product/accounts
: Check Dual Investment accountsPOST /sapi/v1/dci/product/auto_compound/edit-status
: Change Auto-Compound status
2024-02-08
The SPOT WebSocket API can now support SBE on SPOT Testnet.
The SBE schema has been updated with WebSocket API metadata without incrementing either schemaId
or version
.
Users using SBE only on the REST API may continue to use the SBE schema with git commit hash 128b94b2591944a536ae427626b795000100cf1d
or update to the newly-published SBE schema.
Users who want to use SBE on the WebSocket API must use the newly-published SBE schema.
The FAQ for SBE has been updated.
2024-01-24
- New Endpoints for Convert:
POST /sapi/v1/convert/limit/placeOrder
: Place convert limit orderPOST /sapi/v1/convert/limit/cancelOrder
: Cancel convert limit orderGET /sapi/v1/convert/limit/queryOpenOrders
: Query convert limit open orders
2024-01-19
According to the announcement, Binance Earn will disable the following BSwap SAPI endpoints and websocket at 2024-01-26 04:00 (UTC):
GET /sapi/v1/bswap/pools
GET /sapi/v1/bswap/liquidity
POST /sapi/v1/bswap/liquidityAdd
POST /sapi/v1/bswap/liquidityRemove
GET /sapi/v1/bswap/liquidityOps
GET /sapi/v1/bswap/quote
POST /sapi/v1/bswap/swap
GET /sapi/v1/bswap/swap
GET /sapi/v1/bswap/poolConfigure
GET /sapi/v1/bswap/addLiquidityPreview
GET /sapi/v1/bswap/removeLiquidityPreview
GET /sapi/v1/bswap/unclaimedRewards
POST /sapi/v1/bswap/claimRewards
GET /sapi/v1/bswap/claimedHistory
-
wss://api.binance.com/sapi/wss
for BSwapstreams earn_swapprice_<poolid>
andearn_swapprice_all
According to the announcement, Binance Earn disable the following Staking SAPI endpoints at 2024-01-09 06:00 (UTC):
GET /sapi/v1/staking/productList
POST /sapi/v1/staking/purchase
POST /sapi/v1/staking/redeem
GET /sapi/v1/staking/position
GET /sapi/v1/staking/stakingRecord
POST /sapi/v1/staking/setAutoStaking
GET /sapi/v1/staking/personalLeftQuota
2024-01-15
- New Endpoints for Wallet:
GET /sapi/v1/spot/delist-schedule
: Query spot delist schedule
- Update Endpoints for Wallet:
GET /sapi/v1/asset/dribblet
:add parameteraccountType
POST /sapi/v1/asset/dust-btc
:add parameteraccountType
POST /sapi/v1/asset/dust
:add parameteraccountType
2024-01-09
According to the announcement, Binance Margin will remove the following SAPI interfaces at 4:00 on March 31, 2024 (UTC). Please switch to the corresponding alternative interfaces in time:
POST /sapi/v1/margin/transfer
will be removed, please replace withPOST /sapi/v1/asset/transfer
universal transferPOST /sapi/v1/margin/isolated/transfer
will be removed, please replace withPOST /sapi/v1/asset/transfer
universal transferPOST /sapi/v1/margin/loan
will be removed, please replace with the newPOST /sapi/v1/margin/borrow-repay
borrowing and repayment interfacePOST /sapi/v1/margin/repay
will be removed, please replace with the newPOST /sapi/v1/margin/borrow-repay
borrowing and repayment interfaceGET /sapi/v1/margin/isolated/transfer
will be removed, please replace it withGET /sapi/v1/margin/transfer
to get total margin transfer historyGET /sapi/v1/margin/asset
will be removed, please replace withGET /sapi/v1/margin/allAssets
GET /sapi/v1/margin/pair
will be removed, please replace withGET /sapi/v1/margin/allPairs
GET /sapi/v1/margin/isolated/pair
will be removed, please replace withGET /sapi/v1/margin/isolated/allPairs
GET /sapi/v1/margin/loan
will be removed, please replace withGET /sapi/v1/margin/borrow-repay
GET /sapi/v1/margin/repay
will be removed, please replace withGET /sapi/v1/margin/borrow-repay
GET /sapi/v1/margin/dribblet
will be removed, please replace withGET /sapi/v1/asset/dribblet
GET /sapi/v1/margin/dust
will be removed, please replace withPOST /sapi/v1/asset/dust-btc
POST /sapi/v1/margin/dust
will be removed, please replace withPOST /sapi/v1/asset/dust
New Endpoints for Margin:
POST /sapi/v1/margin/borrow-repay
: Margin account borrow/repayGET /sapi/v1/margin/borrow-repay
: Query borrow/repay records in Margin account
Update Endpoints fpr Margin:
GET /sapi/v1/margin/transfer
: add parameterisolatedSymbol
, add response bodyGET /sapi/v1/margin/allAssets
: add parameterasset
, add response bodyGET /sapi/v1/margin/allPairs
: add parametersymbol
GET /sapi/v1/margin/isolated/allPairs
: add parametersymbol
2023-12-22
Binance will disable the following Staking SAPI endpoints at 2024-03-31 04:00:
GET /sapi/v1/eth-staking/eth/history/wbethRewardsHistory
: add new endpoint to query WBETH income recordPOST /sapi/v2/eth-staking/eth/stake
: add new endpoint to stake ETH to get WBETH. Current v1 endpointPOST /sapi/v1/eth-staking/eth/stake
will be deprecated in the future, with the exact timing to be determined.GET /sapi/v2/eth-staking/account
: add new endpoint to query positions and 30-day earnings of staked ETH. Current v1 endpointGET /sapi/v1/eth-staking/account
will be deprecated in the future, with the exact timing to be determined.POST /sapi/v1/eth-staking/wbeth/unwrap
: delete this endpoint,POST /sapi/v1/eth-staking/eth/redeem
is able to achieve same functionalityPOST /sapi/v1/eth-staking/eth/redeem
: Add new parameterasset
, add new response fieldsethAmount
,conversionRatio
GET /sapi/v1/eth-staking/eth/history/stakingHistory
: add new response fieldsdistributeAsset
,distributeAmount
,conversionRatio
GET /sapi/v1/eth-staking/eth/history/redemptionHistory
add new response fieldsasset
,distributeAsset
,distributeAmount
,conversionRatio
POST /sapi/v1/eth-staking/wbeth/wrap
: add new response fieldswbethAmount
,exchangeRate
New Websocket for Margin Trading:
- New Base url
wss://margin-stream.binance.com
for two events: Liability update event and Margin call event
- New Base url
2023-12-08
Simple Binary Encoding (SBE) has been added to SPOT Testnet.
This will be added to the live exchange at a later date.
For more information on what SBE is, please refer to the FAQ
2023-12-04
Notice: The changes below are being rolled out gradually, and will take approximately a week to complete.
General Changes:
- Error message
Precision is over the maximum defined for this asset.
has been changed toParameter '%s' has too much precision.
- This error message is returned when a parameter has more precision than allowed:
e.g. if
base asset
precision is 6 andquantity=0.1234567
then this error message will appear. - This affects all requests with the following parameters:
quantity
quoteOrderQty
icebergQty
limitIcebergQty
stopIcebergQty
price
stopPrice
stopLimitPrice
- This error message is returned when a parameter has more precision than allowed:
e.g. if
- Requests for open OCO (
GET /api/v3/openOrderList
) now correctly return results in ascending order. - Requests for all OCO (
GET /api/v3/allOrderList
) now correctly return results in ascending order whenstartTime
orfromId
are specified. - Fixed a bug where order query (
GET /api/v3/order
)requests would incorrectly return-2026 ORDER_ARCHIVED
error for newly placed orders.
SPOT API
- New endpoint
GET /api/v3/account/commission
- New endpoint
GET /api/v3/ticker/tradingDay
GET /api/v3/avgPrice
response has a new fieldcloseTime
, indicating the last trade time.GET /api/v3/klines
and/api/v3/uiKlines
have a new optional parametertimeZone
.POST /api/v3/order/test
andPOST /api/v3/sor/order/test
have a new optional parametercomputeCommissionRates
.- Changes regarding invalid endpoints being sent:
- Previously, if you query an non-existing endpoint (e.g.
curl -X GET "https://api.binance.com/api/v3/exchangie
) you would get a HTTP 404 code with the response<html><body><h2>404 Not found</h2></body></html>
- From now on the HTML response will only appear if the Accept request header has
text/html
for this situation. The HTTP code will remain the same.
- Previously, if you query an non-existing endpoint (e.g.
WebSocket Streams
- New stream
<symbol>@avgPrice
id
now supports the same values as used forid
in the WebSocket API:- 64-bit signed integers (previously this was unsigned)
- Alphanumeric strings, max of 36 in length
null
- Fixed a bug where unsolicited pongs sent before the ping would cause disconnection.
User Data Streams
- When an event of type
executionReport
has an execution type (x
) ofTRADE_PREVENTION
, fieldsl
,L
andY
will now always be 0. New fieldspl
,pL
andpY
will describe the prevented execution quantity, prevented execution price, and prevented execution notional instead. These new fields show the values of what wouldl
,L
andY
have been if the taker order didn't have self-trade prevention enabled.
The following will take effect approximately a week after the release date:
- Symbol Permissions will only affect order placement, not cancellation.
permissions
still apply to Cancel-Replace orders (i.e. The cancellation won't be allowed if your account does have the permission to place an order using this request.)
2023-11-21
- New endpoint for Wallet:
GET /sapi/v1/capital/deposit/address/list
: Fetch deposit address list with network.
- Update endpoints for Margin
POST /sapi/v1/margin/order
:New enumerate valueAUTO_BORROW_REPAY
for the field ofsideEffectType
POST /sapi/v1/margin/order/oco
:New enumerate valueAUTO_BORROW_REPAY
for the field ofsideEffectType
GET /sapi/v1/margin/available-inventory
:New response field ofupdateTime
which indicates the acquisition time of lending inventory.
2023-11-17
- New endpoint for Margin to support cross margin Pro modeFAQ:
GET /sapi/v1/margin/leverageBracket
: query Liability coin leverage bracket in cross margin Pro mode
- Update endpoints for Margin:
POST /sapi/v1/margin/max-leverage
: fieldmaxLeverage
adds value 10 for Cross Margin ProGET /sapi/v1/margin/account
: add new response fieldaccountType
,MARGIN_2
for Cross Margin Pro
2023-11-02
- Changes to Wallet Endpoint:
GET /sapi/v1/account/apiRestrictions
: add new response fieldenablePortfolioMarginTrading
2023-10-19
Effective on 2023-10-19 00:00 UTC
The request weights of the following requests have been increased:
SPOT API | Condition | Previous Request Weight | New Request Weight |
---|---|---|---|
GET /api/v3/trades |
N/A | 2 | 10 |
GET /api/v3/depth |
Limit 1-100 | 2 | 5 |
Limit 101-500 | 10 | 25 | |
Limit 501-1000 | 20 | 50 | |
Limit 1001-5000 | 100 | 250 |
2023-10-16
- New endpoint for Margin:
GET /sapi/v1/margin/available-inventory
: Query margin available inventoryPOST /sapi/v1/margin/manual-liquidation
: Margin manual liquidation
2023-10-11
- New endpoint for VIP Loans:
GET /sapi/v1/loan/vip/request/interestRate
: Get Borrow Interest Rate
2023-10-03
- Order decrement feature went live at 06:15 UTC.
- For more information on this feature, please refer to our FAQ
2023-09-25
New endpoint for Futures:
GET /sapi/v1/futures/histDataLink
: query futures ticklevel orderbook historicak data download link
Delete Futures cross collateral endpoint(offline on 2022):
GET /sapi/v1/futures/loan/borrow/history
GET /sapi/v1/futures/loan/repay/history
GET /sapi/v2/futures/loan/wallet
GET /sapi/v1/futures/loan/adjustCollateral/history
GET /sapi/v1/futures/loan/liquidationHistory
GET /sapi/v1/futures/loan/interestHistory
2023-09-22
New endpoints for Wallet:
GET /sapi/v1/asset/wallet/balance
: query user wallet balanceGET /sapi/v1/asset/custody/transfer-history
: query user delegation history(For Master Account)
Changes to VIP loan Endpoint:
GET /sapi/v1/loan/vip/loanable/data
: add new response fields_flexibleDailyInterestRate
,_flexibleYearlyInterestRate
GET /sapi/v1/loan/vip/ongoing/orders
: add new response fieldsloanDate
,loanRate
,loanTerm
,expirationTime
Changes to Portfolio Margin Pro Endpoint:
POST /sapi/v1/portfolio/repay
: add paramaterfrom
2023-09-18
New endpoints for Auto-Invest:
GET /sapi/v1/lending/auto-invest/index/info
: query index detailsGET /sapi/v1/lending/auto-invest/index/user-summary
: query index linked plan position detailsPOST /sapi/v1/lending/auto-invest/one-off
: One Time transactionGET /sapi/v1/lending/auto-invest/one-off/status
: query one-time transaction statusPOST /sapi/v1/lending/auto-invest/redeem
: index linked plan redemptionGET /sapi/v1/lending/auto-invest/redeem/history
:query index Linked plan Redemption historyGET /sapi/v1/lending/auto-invest/rebalance/history
: query index linked plan rebalance details
Changes to Margin Endpoint
GET /sapi/v1/margin/isolated/transfer
:- Add request field
type
- Delete request field
transFrom
,transTo
- Add request field
2023-09-14
- New endpoint for Portfolio Margin Pro:
GET /sapi/v1/portfolio/margin-asset-leverage
: Get Portfolio Margin Asset Leverage
- The api key permission for the following endpoints changed from enable
Enable Spot & Margin Trading
to enablePermits Universal Transfer
POST /sapi/v1/portfolio/auto-collection
POST /sapi/v1/portfolio/asset-collection
POST /sapi/v1/portfolio/bnb-transfer
2023-09-04
- Rate limit adjustment for Wallet Endpoint:
GET /sapi/v1/capital/withdraw/history
: UID rate limit is adjusted to 18000, maxmium 10 requests per second. Please refer to the endpoint description for detail
2023-08-31
- New endpoint for Margin:
/sapi/v1/margin/capital-flow
: Get cross or isolated margin capital flow
2023-08-26
- Changes to Simple Earn endpoints:
GET /sapi/v1/simple-earn/flexible/history/subscriptionRecord
: new fields in response:sourceAccount
,amtFromSpot
,amtFromFunding
GET /sapi/v1/simple-earn/locked/history/subscriptionRecord
: new fields in response:sourceAccount
,amtFromSpot
,amtFromFunding
GET /sapi/v1/simple-earn/flexible/history/redemptionRecord
: new fields in responsedestAccount
POST /sapi/v1/simple-earn/flexible/subscribe
: new parametersourceAccount
POST /sapi/v1/simple-earn/locked/subscribe
: new parametersourceAccount
POST /sapi/v1/simple-earn/flexible/redeem
: new parameterdestAccount
- New endpoint for Crypto Loans:
POST /sapi/v1/loan/flexible/borrow
: flexible Loan borrowGET /sapi/v1/loan/flexible/ongoing/orders
: get flexible loan ongoing ordersGET /sapi/v1/loan/flexible/borrow/history
: Get flexible loan borrow historyPOST /sapi/v1/loan/flexible/repay
: flexible loan repayPOST /sapi/v1/loan/flexible/repay/history
: Get flexible loan repayment historyPOST /sapi/v1/loan/flexible/adjust/ltv
: adjust flexible Loan adjust LTVGET /sapi/v1/loan/flexible/ltv/adjustment/history
: Get Flexible loan LTV adjustment historyGET /sapi/v1/loan/flexible/loanable/data
:Get flexible loan assets dataGET /sapi/v1/loan/flexible/collateral/data
: Get flexible loan collateral assets data
2023-08-25
The following changes will be effective from 2023-08-25 at UTC 00:00.
- The
REQUEST_WEIGHT
rate limit for SPOT API has been adjusted to 6,000 every minute. - The
RAW_REQUESTS
for SPOT API has been adjusted to 61,000 every 5 minutes. - The weights to the following requests for the SPOT API have been adjusted.
Please refer to the table for more details:
Request | Previous Request Weight | New Request Weight |
---|---|---|
GET /api/v3/order |
2 | 4 |
GET /api/v3/orderList |
2 | 4 |
GET /api/v3/openOrders - With symbol |
3 | 6 |
GET /api/v3/openOrders - Without symbol |
40 | 80 |
GET /api/v3/openOrderList |
3 | 6 |
GET /api/v3/allOrders |
10 | 20 |
GET /api/v3/allOrderList |
10 | 20 |
GET /api/v3/myTrades |
10 | 20 |
GET /api/v3/myAllocations |
10 | 20 |
GET /api/v3/myPreventedMatches - Using preventedMatchId |
1 | 2 |
GET /api/v3/myPreventedMatches - Using orderId |
10 | 20 |
GET /api/v3/account |
10 | 20 |
GET /api/v3/rateLimit/order |
20 | 40 |
GET /api/v3/exchangeInfo |
10 | 20 |
GET /api/v3/depth - Limit 1-100 |
1 | 2 |
GET /api/v3/depth - Limit 101-500 |
5 | 10 |
GET /api/v3/depth - Limit 501-1000 |
10 | 20 |
GET /api/v3/depth - Limit 1001-5000 |
50 | 100 |
GET /api/v3/aggTrades |
1 | 2 |
GET /api/v3/trades |
1 | 2 |
GET /api/v3/historicalTrades |
5 | 10 |
GET /api/v3/klines |
1 | 2 |
GET /api/v3/uiKlines |
1 | 2 |
GET /api/v3/ticker/bookTicker - With symbol |
1 | 2 |
GET /api/v3/ticker/bookTicker - Without symbol or With symbols |
2 | 4 |
GET /api/v3/ticker/price - With symbol |
1 | 2 |
GET /api/v3/ticker/price - Without symbol or With symbols |
2 | 4 |
GET /api/v3/ticker/24hr - With symbol or With symbols using 1-20 symbols |
1 | 2 |
GET /api/v3/ticker/24hr - With symbols using 21-100 symbols |
20 | 40 |
GET /api/v3/ticker/24hr - Without symbol or symbols using 101 or more symbols |
40 | 80 |
GET /api/v3/avgPrice |
1 | 2 |
GET /api/v3/ticker |
2 | 4 |
GET /api/v3/ticker - Maximum weight for this request |
100 | 200 |
POST /api/v3/userDataStream |
1 | 2 |
PUT /api/v3/userDataStream |
1 | 2 |
DELETE /api/v3/userDataStream |
1 | 2 |
2023-08-18
- Update endpoints for VIP Loan:
POST /sapi/v1/loan/vip/borrow
: add fieldisFlexibleRate
to borrow using flexible rate loan
2023-08-08
Smart Order Routing (SOR) has been added to the APIs. For more information please refer to our FAQ. Please wait for future announcements on when the feature will be enabled.
SPOT API
- Changes to
GET /api/v3/exchangeInfo
:- New field in response:
sors
, describing SORs enabled on the exchange.
- New field in response:
- Changes to
GET /api/v3/myPreventedMatches
- New field
makerSymbol
will appear in the response for all prevented matches.
- New field
- New endpoints for order placement using SOR:
POST /api/v3/sor/order
POST /api/v3/sor/order/test
- New endpoint
GET /api/v3/myAllocations
USER DATA STREAM
- Changes to
executionReport
:- These fields are only relevant for orders placed using SOR:
- New field
b
formatchType
- New field
a
forallocId
- New field
k
forworkingFloor
- New field
- This field is only relevant for orders expiring due to STP:
- New field
Cs
forcounterSymbol
- New field
- These fields are only relevant for orders placed using SOR:
2023-08-02
- Effective from 21 Aug 2023, a 1% transaction fee will apply when you buy or create gift cards in Binance directly. The following endpoints are impacted:
POST /sapi/v1/giftcard/createCode
POST /sapi/v1/giftcard/buyCode
2023-07-20
- As per the announcement, effective from 20 July 2023, creating gift cards is limited only to entity accounts which have passed KYB verification. The following endpoints are impacted:
POST /sapi/v1/giftcard/createCode
POST /sapi/v1/giftcard/buyCode
- New endpoints for Porfolio Margin Pro:
POST /sapi/v1/portfolio/asset-collection
: Fund Collection by Asset
2023-07-18
- New API key type – Ed25519 – is now supported. (UI support will be released this week.)
- Ed25519 API keys are an alternative to RSA API keys, using asymmetric cryptography to authenticate your requests on the API.
- We recommend switching to Ed25519 for improved performance and security.
For more information, please refer to our supplemental document API Key Types.
- Documentation has been updated with how to sign a payload with Ed25519 keys.
2023-07-14
- New endpoints for Porfolio Margin Pro:
POST /sapi/v1/portfolio/repay-futures-switch
: Change Auto-repay-futures StatusGET /sapi/v1/portfolio/repay-futures-switch
: Get Auto-repay-futures StatusPOST /sapi/v1/portfolio/repay-futures-negative-balance
: Repay futures Negative Balance
- New endpoints for VIP Loan:
POST /sapi/v1/loan/vip/renew
: VIP Loan Renew
2023-07-11
Notice: The change below are being rolled out, and will take approximately a week to complete.
SPOT API
- Changes to error messages:
- Previously, when duplicate symbols were passed to requests that do not allow it, the error would be "Mandatory parameter symbols was not sent, was empty/null, or malformed."
- Now, the error message is "Symbol is present multiple times in the list", with a new error code
-1151
- This affects the following requests:
GET /api/v3/exchangeInfo
GET /api/v3/ticker/24hr
GET /api/v3/ticker/price
GET/api/v3/ticker/bookTicker
- Fixed a bug where some non-archived orders being queried would receive the error code that their order was archived.
- Changes to
GET /api/v3/account
:- New field
preventSor
will appear in the response. - New field
uid
that shows the User Id/Account will appear in the response.
- New field
- Changes to
GET /api/v3/historicalTrades
:- Changed security type from
MARKET_DATA
toNONE
. - This means that the
X-MBX-APIKEY
header is no longer necessary and is now ignored.
- Changed security type from
The following changes will take effect approximately a week from the release date::
- Fixed multiple bugs with orders that use
type=MARKET
andquoteOrderQty
, also known as “reverse market orders”:- Reverse market orders are no longer partially filled, or filled for zero or negative quantity under extreme market conditions.
MARKET_LOT_SIZE
filter now correctly rejects reverse market orders that go over the symbol'smaxQty
.
- Fixed a bug where OCO orders using
trailingDelta
could have an incorrecttrailingTime
value after either leg of the OCO is touched. - New field
transactTime
will appear in order cancellation responses. This affects the following requests:DELETE /api/v3/order
POST /api/v3/order/cancelReplace
DELETE /api/v3/openOrders
DELETE /api/v3/orderList
2023-07-07
- New endpoints for Margin:
POST /sapi/v1/margin/max-leverage
: Adjust cross margin max leverage
2023-06-29
- Added multiple new endpoints related to ETH Staking in Staking.
- New endpoints for Margin:
GET /sapi/v1/margin/dust
: Get Assets That Can Be Converted Into BNBPOST /sapi/v1/margin/dust
: Convert dust assets to BNB.
- New endpoints for VIP Loan(effective on 2023-06-30):
POST /sapi/v1/loan/vip/borrow
: Borrow VIP loanGET /sapi/v1/loan/vip/loanable/data
: Get interest rate and borrow limit of loanable assets.GET /sapi/v1/loan/vip/collateral/data
: Get collateral asset dataGET /sapi/v1/loan/vip/request/data
: Query application status.
2023-06-22
- New endpoints for Sub-Account:
POST /sapi/v1/sub-account/eoptions/enable
: enable Options for Sub-accountGET /sapi/v1/managed-subaccount/query-trans-log
: Query Managed Sub Account Transfer Log (For Trading Team Sub Account)
- Update endpoints for Margin:
POST /sapi/v1/margin/order
: add fieldsautoRepayAtCancel
andselfTradePreventionMode
POST /sapi/v1/margin/order/oco
: add fieldselfTradePreventionMode
- New endpoints for Simple Earn.
- Delete endpoint for Lending:
GET /sapi/v1/lending/daily/product/list
GET /sapi/v1/lending/daily/userLeftQuota
POST /sapi/v1/lending/daily/purchase
GET /sapi/v1/lending/daily/userRedemptionQuota
POST /sapi/v1/lending/daily/redeem
GET /sapi/v1/lending/daily/token/position
GET /sapi/v1/lending/union/account
GET /sapi/v1/lending/union/purchaseRecord
GET /sapi/v1/lending/union/redemptionRecord
GET /sapi/v1/lending/union/interestHistory
2023-06-20
- New endpoints for Auto-Investment:
GET /sapi/v1/lending/auto-invest/target-asset/list
: query target asset listGET /sapi/v1/lending/auto-invest/target-asset/roi/list
: query ROI return list for target assetGET /sapi/v1/lending/auto-invest/all/asset
: query all source assets and target assetsGET /sapi/v1/lending/auto-invest/source-asset/list
: query source asset to be used for investmentPOST /sapi/v1/lending/auto-invest/plan/add
: create an investment planPOST/sapi/v1/lending/auto-invest/plan/edit
: adjust the details of the planPOST /sapi/v1/lending/auto-invest/plan/edit-status
: change plan statusGET /sapi/v1/lending/auto-invest/plan/list
: query plan listsGET /sapi/v1/lending/auto-invest/plan/id
: Get holding details of the planGET /sapi/v1/lending/auto-invest/history/list
: query subscription transaction history of a plan
- Update endpoints for Margin:
GET /sapi/v1/margin/delist-schedule
: get tokens or symbols delist schedule for cross margin and isolated margin
2023-06-09
Below changes are applicable to the Portfolio Margin Pro Program and the new Portfolio Margin Program: these will be taken into effect on 2023-06-22: Transfers in and out of Portfolio Margin Account can only be done through Cross Margin Wallets. For
POST /sapi/v1/asset/transfer
, only below parameters can be supported for the Portfolio Margin Pro Program and the new Portfolio Margin Program:MAIN_PORTFOLIO_MARGIN
andPORTFOLIO_MARGIN_MAIN
- Please be aware that transfer in and out from UM or CM wallets to non-PM wallets (such as spot wallet and option wallet) are not supported. For POST /sapi/v1/asset/transfer, below parameters can no longer be supported for the Portfolio Margin Pro Program and the new Portfolio Margin Program:
- MAIN_UMFUTURE
- MAIN_CMFUTURE
- UMFUTURE_MAIN
- UMFUTURE_MARGIN
- CMFUTURE_MARGIN
- MARGIN_UMFUTURE
- MARGIN_CMFUTURE
- FUNDING_UMFUTURE
- UMFUTURE_FUNDING
- FUNDING_CMFUTURE
- CMFUTURE_FUNDING
- UMFUTURE_OPTION
- OPTION_UMFUTURE
POST /sapi/v1/sub-account/futures/internalTransfer
will no longer be supportedPOST /sapi/v1/sub-account/futures/transfer
will no longer be supportedPOST /sapi/v1/futures/transfer
will no longer be supportedPOST /sapi/v1/sub-account/universalTransfer
will no longer be supported for below:- SPOT transfer to USDT_FUTURE, COIN_FUTURE (regardless of master or sub)
- USDT_FUTURE, COIN_FUTURE transfer to SPOT (regardless of master or sub)
- Please be aware that transfer in and out from UM or CM wallets to non-PM wallets (such as spot wallet and option wallet) are not supported. For POST /sapi/v1/asset/transfer, below parameters can no longer be supported for the Portfolio Margin Pro Program and the new Portfolio Margin Program:
New endpoints for Portfolio Margin Pro(Effective on 06/09):
POST /sapi/v1/portfolio/auto-collection
: all transfers (excluding UM Account’s BNB) from Futures Account to Margin accountPOST /sapi/v1/portfolio/bnb-transfer
: BNB transfer can be between Margin Account and UM Account
2023-06-06
- A new endpoint is now available for redundancy: https://api-gcp.binance.com/
- This is using the GCP (Google Cloud Platform) CDN and may have slower performance compared to
api1
-api4
endpoints.
- This is using the GCP (Google Cloud Platform) CDN and may have slower performance compared to
2023-06-01
- New WEBSOCKET for Bwap:
- New Base url
wss://api.binance.com/sapi/wss
for BSwap streamsearn_swapprice_<poolid>
andearn_swapprice_all
- New Base url
2023-05-30
- Update endpoints for Pay:
GET /sapi/v1/pay/transactions
: add more content in response fieldfundsDetail
2023-05-26
Notice: The change below are being rolled out, and will take approximately a week to complete.
- The following base endpoints may give better performance but have less stability than https://api.binance.com:
- https://api1.binance.com
- https://api2.binance.com
- https://api3.binance.com
- https://api4.binance.com
2023-05-24
- The previous market data URLs have been deprecated. Please update your code immediately to prevent interruption of our services.
- API Market data from
data.binance.com
can now be accessed fromdata-api.binance.vision
. - Websocket Market Data from
data-stream.binance.com
can now be accessed fromdata-stream.binance.vision
.
- API Market data from
GET /sapi/v1/portfolio/interest-rate
has be deprecated, users can query the Portfolio Margin Pro Negative Balance Interest Rate by usingGET /sapi/v1/margin/interestRateHistory
.
2023-05-18
- New endpoints for Wallet:
POST /sapi/v1/capital/deposit/credit-apply
: apply deposit credit for expired address
2023-05-09
- New endpoints for Portfolio Margin:
GET /sapi/v1/portfolio/asset-index-price
: query portfolio margin asset index price
- Update endpoints for Wallet:
POST /sapi/v1/asset/transfer
: add enumMAIN_PORTFOLIO_MARGIN
andPORTFOLIO_MARGIN_MAIN
2023-04-20
- New endpoints for Sub-Account:
GET /sapi/v1/managed-subaccount/deposit/address
: get managed sub-account deposit address
- Update endpoints for VIP Loans:
GET /sapi/v1/loan/vip/ongoing/orders
: add fieldstotalCollateralValueAfterHaircut
andlockedCollateralValue
2023-04-18
- New endpoints for Spot Algo:
POST /sapi/v1/algo/spot/newOrderTwap
to support new orderDELETE /sapi/v1/algo/spot/order
to support cancel Algo orderGET /sapi/v1/algo/spot/openOrders
to support query Algo open ordersGET /sapi/v1/algo/spot/historicalOrders
to support query Algo historical ordersGET /sapi/v1/algo/spot/subOrders
to support query Algo sub orders for a specified algoId
2023-03-23
- Update endpoints for Sub-Account:
GET /sapi/v1/managed-subaccount/queryTransLogForInvestor
: Add response fieldtranId
GET /sapi/v1/managed-subaccount/queryTransLogForTradeParent
: Add response fieldtranId
- New endpoints for Sub-Account:
GET /sapi/v1/managed-subaccount/info
: query investor's managed sub-account listGET /sapi/v1/sub-account/transaction-statistics
: Query sub-account transaction tatistics
2023-03-13
Notice: All changes are being rolled out gradually to all our servers, and may take a week to complete.
GENERAL CHANGES
- The error messages for certain issues have been improved for easier troubleshooting.
Situation | Old Error Message | New Error Message |
---|---|---|
An account cannot place or cancel an order, due to trading ability disabled. | This action is disabled on this account. | This account may not place or cancel orders. |
When the permissions configured on the symbol do not match the permissions on the account. | This symbol is not permitted for this account. | |
When the account tries to place an order on a symbol it has no permissions for. | This symbol is restricted for this account. | |
Placing an order when symbol is not TRADING. | Unsupported order combination. | This order type is not possible in this trading phase. |
Placing an order with timeinForce=IOC or FOK on a trading phase that does not support it. | Limit orders require GTC for this phase. |
- Fixed error message for querying archived orders:
- Previously, If an archived order (i.e. order with status
CANCELED
orEXPIRED
whereexecutedQty
== 0 that occurred more than 90 days in the past.) is queried, the error message would be:{"code": -2013,"msg": "Order does not exist."}
- Now, the error message is:
{"code": -2026,"msg": "Order was canceled or expired with no executed qty over 90 days ago and has been archived."}
- Previously, If an archived order (i.e. order with status
- Behavior for API requests with
startTime
andendTime
:- Previously some requests failed if the
startTime
==endTime
. - Now, all API requests that accept
startTime
andendTime
allow the parameters to be equal. This applies to the following requests:- Rest API
GET /api/v3/aggTrades
GET /api/v3/klines
GET /api/v3/allOrderList
GET /api/v3/allOrders
GET /api/v3/myTrades
- Rest API
- Previously some requests failed if the
The following changes will take effect approximately a week from the release date, but the rest of the documentation has been updated to reflect the future changes:
- Changes to Filter Evaluation:
- Previous behavior:
LOT_SIZE
andMARKET_LOT_SIZE
required that (quantity
-minQty
) %stepSize
== 0. - New behavior: This has now been changed to (
quantity
%stepSize
) == 0.
- Previous behavior:
- Bug fix with reverse
MARKET
orders (i.e.,MARKET
usingquoteOrderQty
):- Previous behavior: Reverse market orders would always have the status
FILLED
even if the order did not fully fill due to low liquidity. - New behavior: If the reverse market order did not fully fill due to low liquidity the order status will be
EXPIRED
, andFILLED
only if the order was completely filled.
- Previous behavior: Reverse market orders would always have the status
SPOT API
- Changes to
DELETE /api/v3/order
andPOST /api/v3/order/cancelReplace
:- A new optional parameter
cancelRestrictions
that determines whether the cancel will succeed if the order status isNEW
orPARTIALLY_FILLED
. - If the order cancellation fails due to
cancelRestrictions
, the error will be:{"code": -2011,"msg": "Order was not canceled due to cancel restrictions."}
- A new optional parameter
2023-02-27
- New endpoints for Margin:
/sapi/v1/margin/next-hourly-interest-rate
: Get user the next hourly estimate interest
- New endpoints for Porfolio Margin:
GET /sapi/v1/portfolio/interest-history
: get user's portfolio margin interest historyGET /sapi/v1/portfolio/interest-rate
: get portfolio margin interest rate
2023-02-21
- Adjusted endpoints for Crypto Loan:
POST /sapi/v1/loan/borrow
: paramaterloanTerm
is restricted to 7 or 30
2023-02-17
The Websocket Stream now only allows 300 connections requests every 5 minutes.
This limit is per IP address.
Please be careful when trying to open multiple connections or reconnecting to the Websocket API.
2023-02-13
- New endpoints for Sub-Account:
GET /sapi/v4/sub-account/assets
: Fetch sub-account assets
2023-02-02
- New endpoints for Margin:
GET /sapi/v1/margin/exchange-small-liability
: Query the coins which can be small liability exchangePOST /sapi/v1/margin/exchange-small-liability
: Cross Margin Small Liability ExchangeGET /sapi/v1/margin/exchange-small-liability-history
: Get Small liability Exchange History
- Update endpoints for Wallet:
- Universal Transfer
POST /sapi/v1/asset/transfer
support option transfer
- Universal Transfer
2023-01-26
As per the announcement, Self Trade Prevention will be enabled at 2023-01-26 08:00 UTC.
Please refer to GET /api/v3/exchangeInfo
from the Rest API or exchangeInfo
from the Websocket API on the default and allowed modes.
2023-01-23
New API cluster has been added. Note that all endpoints are functionally equal, but may vary in performance.
- https://api4.binance.com
2023-01-19
ACTUAL RELEASE DATE TBD
SPOT API
New Feature: Self-Trade Prevention (aka STP) will be added to the system at a later date. This will prevent orders from matching with orders from the same account, or accounts under the same tradeGroupId
.
Please refer to GET /api/v3/exchangeInfo
from the SPOT API or exchangeInfo
from the Websocket API on the status.
"defaultSelfTradePreventionMode": "NONE", //If selfTradePreventionMode not provided, this will be the value passed to the engine
"allowedSelfTradePreventionModes": [ //What the allowed modes of selfTradePrevention are
"NONE",
"EXPIRE_TAKER",
"EXPIRE_BOTH",
"EXPIRE_MAKER"
]
- New order status:
EXPIRED_IN_MATCH
- This means that the order expired due to STP being triggered. - New endpoint:
GET /api/v3/myPreventedMatches
- This queries the orders that expired due to STP being triggered.
- New optional parameter
selfTradePreventionMode
has been added to the following endpoints:POST /api/v3/order
POST /api/v3/order/oco
POST /api/v3/order/cancelReplace
- New responses that will appear for all order placement endpoints if there was a prevented match (i.e. if an order could have matched with an order of the same account, or the accounts are in the same
tradeGroupId
):tradeGroupId
- This will only appear if account is configured to atradeGroupId
and if there was a prevented match.preventedQuantity
- Only appears if there was a prevented match.- An array
preventedMatches
with the following fields:preventedMatchId
makerOrderId
price
takerPreventedQuantity
- This will only appear ifselfTradePreventionMode
set isEXPIRE_TAKER
orEXPIRE_BOTH
.makerPreventedQuantity
- This will only appear ifselfTradePreventionMode
set isEXPIRE_MAKER
orEXPIRE_BOTH
.
- New fields
preventedMatchId
andpreventedQuantity
that can appear in the order query endpoints if the order had expired due to an STP trigger:GET /api/v3/order
GET /api/v3/openOrders
GET /api/v3/allOrders
USER DATA STREAM
- New execution Type:
TRADE_PREVENTION
- New fields for
executionReport
(These fields will only appear if the order has expired due to STP trigger)u
-tradeGroupId
v
-preventedMatchId
U
-counterOrderId
A
-preventedQuantity
B
-lastPreventedQuantity
2023-01-13
- The following endpoints will be discontinued on January 13, 2023 6:00 AM UTC:
POST /sapi/v1/sub-account/subAccountApi/ipRestriction
to support master account enable and disable IP restriction for a sub-account API KeyPOST /sapi/v1/sub-account/subAccountApi/ipRestriction/ipList
to support master account add IP list for a sub-account API Key
- New endpoints for Sub-Account:
GET /sapi/v1/managed-subaccount/fetch-future-asset
: Investor can use this api to query managed sub account futures asset detailsGET /sapi/v1/managed-subaccount/marginAsset
: Investor can use this api to query managed sub account margin asset details
- New endpoin for Margin:
GET /sapi/v1/margin/crossMarginCollateralRatio
: Get cross margin collateral ratio
2023-01-05
- New endpoints for Sub-Account:
GET /sapi/v1/managed-subaccount/queryTransLogForInvestor
: Investor can use this api to query managed sub account transfer logGET /sapi/v1/managed-subaccount/queryTransLogForTradeParent
: Trading team can use this api to query managed sub account transfer log
2022-12-26
- New endpoints for wallet:
GET /sapi/v1/capital/contract/convertible-coins
: Get a user's auto-conversion settings in deposit/withdrawalPOST /sapi/v1/capital/contract/convertible-coins
: User can use it to turn on or turn off the BUSD auto-conversion from/to a specific stable coin.
2022-12-15
- New RSA signature
- Documentation has been updated to show how to sign a request using an RSA key.
- For security reasons, we recommend to use RSA keys instead of HMAC keys when generating an API key.
- We accept
PKCS#8
(BEGIN PUBLIC KEY). - More details on how to upload your RSA public key will be added at a later date.
2022-12-13
REST API
Some error messages on error code -1003
have changed:
- Previous error message:
Too much request weight used; current limit is %s request weight per %s %s. Please use the websocket for live updates to avoid polling the API.
has been updated to:
Too much request weight used; current limit is %s request weight per %s. Please use WebSocket Streams for live updates to avoid polling the API.
- Previous error message
Way too much request weight used; IP banned until %s. Please use the websocket for live updates to avoid bans.
has been updated to:
Way too much request weight used; IP banned until %s. Please use WebSocket Streams for live updates to avoid bans.
2022-12-05
Notice: These changes are being rolled out gradually to all our servers, and will take approximately a week to complete.
WEBSOCKET
!bookTicker
will be removed by December 7, 2022. Please use the Individual Book Ticker Streams instead. (<symbol>@bookTicker).- Multiple <symbol>@bookTicker streams can be subscribed to over one connection. (E.g.
wss://stream.binance.com:9443/stream?streams=btcusdt@bookTicker/bnbbtc@bookTicker
)
- Multiple <symbol>@bookTicker streams can be subscribed to over one connection. (E.g.
SPOT API
- New error code
-1135
- This error code will occur if a parameter requiring a JSON object is invalid.
- New error code
-1108
- This error will occur if a value to a parameter being sent was too large, potentially causing overflow.
- This error code can occur in the following endpoints:
POST /api/v3/order
POST /api/v3/order/cancelReplace
POST /api/v3/order/oco
- Changes to
GET /api/v3/aggTrades
- Previous behavior:
startTime
andendTime
had to be used in combination and could only be an hour apart. - New behavior:
startTime
andendTime
can be used individually and the 1 hour limit has been removed.- When using
startTime
only, this will return trades from that time, up to thelimit
provided. - When using
endTime
only, this will return trades starting from theendTime
including all trades before that time, up to the limit provided. - If
limit
not provided, regardless of used in combination or sent individually, the endpoint will use the default limit.
- When using
- Previous behavior:
Changes to
GET /api/v3/myTrades
- Fixed a bug where
symbol
+orderId
combination would return all trades even if the number of trades went beyond the500
default limit. Previous behavior: The API would send specific error messages depending on the combination of parameters sent. E.g:
{ "code": -1106, "msg": "Parameter X was sent when not required." }
New behavior: If the combinations of optional parameters to the endpoint were not supported, then the endpoint will respond with the generic error:
{ "code": -1128, "msg": "Combination of optional parameters invalid." }
Added a new combination of supported parameters:
symbol
+orderId
+fromId
.The following combinations of parameters were previously supported but no longer accepted, as these combinations were only taking
fromId
into consideration, ignoringstartTime
andendTime
:symbol
+fromId
+startTime
symbol
+fromId
+endTime
symbol
+fromId
+startTime
+endTime
Thus, these are the supported combinations of parameters:
symbol
symbol
+orderId
symbol
+startTime
symbol
+endTime
symbol
+fromId
symbol
+startTime
+endTime
symbol
+orderId
+fromId
- Fixed a bug where
Note: These new fields will appear approximately a week from the release date.
- Changes to
GET /api/v3/exchangeInfo
- New fields
defaultSelfTradePreventionMode
andallowedSelfTradePreventionModes
- New fields
- Changes to the Order Placement Endpoints/Order Query/Order Cancellation Endpoints:
- New field
selfTradePreventionMode
will appear in the response. - Affects the following endpoints:
POST /api/v3/order
POST /api/v3/order/oco
POST /api/v3/order/cancelReplace
GET /api/v3/order
DELETE /api/v3/order
DELETE /api/v3/orderList
- New field
- Changes to
GET /api/v3/account
- New field
requireSelfTradePrevention
will appear in the response.
- New field
- New field
workingTime
, indicating when the order started working on the order book, will appear in the following endpoints:POST /api/v3/order
GET /api/v3/order
POST /api/v3/order/cancelReplace
POST /api/v3/order/oco
GET /api/v3/order
GET /api/v3/openOrders
GET /api/v3/allOrders
- Field
trailingTime
, indicating the time when the trailing order is active and tracking price changes, will appear for the following order types (TAKE_PROFIT
,TAKE_PROFIT_LIMIT
,STOP_LOSS
,STOP_LOSS_LIMIT
iftrailingDelta
parameter was provided) for the following endpoints:POST /api/v3/order
GET /api/v3/order
GET /api/v3/openOrders
GET /api/v3/allOrders
POST /api/v3/order/cancelReplace
DELETE /api/v3/order
- Field
commissionRates
will appear in theGET /api/v3/acccount
response
USER DATA STREAM
- eventType
executionReport
has new fieldsV
-selfTradePreventionMode
D
-trailing_time
(Appears if the trailing stop order is active)W
-workingTime
(Appears ifisWorking
=true
)
2022-12-02
- Added a new market data base URL
https://data.binance.com
. - Added a new WebSocket URL
wss://data-stream.binance.com
.
2022-11-29
- New endpoint for VIP Loan:
GET /sapi/v1/loan/vip/collateral/account
: Check Locked Value of VIP Collateral Account
2022-11-22
- New endpoints for Convert:
GET /sapi/v1/convert/exchangeInfo
: Query for all convertible token pairs and the tokens’ respective upper/lower limitsGET /sapi/v1/convert/assetInfo
: Query for supported asset’s precision informationPOST /sapi/v1/convert/getQuote
: Request a quote for the requested token pairsPOST /sapi/v1/convert/acceptQuote
: Accept the offered quote by quote ID.GET /sapi/v1/convert/orderStatus
: Query order status by order ID.
2022-11-18
- New endpoint for Wallet:
GET /sapi/v1/asset/ledger-transfer/cloud-mining/queryByPage
: The query of Cloud-Mining payment and refund history
- New endpoints for Sub-account:
POST /sapi/v2/sub-account/subAccountApi/ipRestriction
: To support master account update IP Restriction for Sub-Account API key
2022-11-14
- New endpoints for VIP Loan:
GET /sapi/v1/loan/vip/ongoing/orders
: Get VIP Loan Ongoing OrdersPOST /sapi/v1/loan/vip/repay
: VIP Loan RepayGET /sapi/v1/loan/vip/repay/history
: Get VIP Loan Repayment History
2022-11-02
- Update endpoints for Wallet:
POST /sapi/v1/capital/withdraw/apply
: Weight changed to Weight(UID): 600
2022-11-01
- New endpoints for Crypto Loan:
GET /sapi/v1/loan/loanable/data
: Get interest rate and borrow limit of loanable assets. The borrow limit is shown in USD value.GET /sapi/v1/loan/collateral/data
: Get LTV information and collateral limit of collateral assets. The collateral limit is shown in USD value.GET /sapi/v1/loan/repay/collateral/rate
: Get the the rate of collateral coin / loan coin when using collateral repay, the rate will be valid within 8 second.POST /sapi/v1/loan/customize/margin_call
: Customize margin call for ongoing orders only.
2022-10-28
- Update endpoints for Wallet:
POST /sapi/v1/asset/convert-transfer
: New parameteraccountType
POST /sapi/v1/asset/convert-transfer/queryByPage
: request method is changed toGET
, new parameterclientTranId
2022-10-15
- New endpoints for Binance Code:
POST /sapi/v1/giftcard/buyCode
: For buying a fixed-value Binance Code.GET /sapi/v1/giftcard/buyCode/token-limit
: To verify which tokens are available for you to purchase fixed-value gift cards as mentioned in section 2 and its’ limitation.
2022-09-30
- Delete endpoints for Futures Cross Collateral:
POST /sapi/v1/futures/loan/borrow
POST /sapi/v1/futures/loan/repay
GET /sapi/v1/futures/loan/configs
GET /sapi/v2/futures/loan/configs
GET /sapi/v1/futures/loan/calcAdjustLevel
GET /sapi/v2/futures/loan/calcAdjustLevel
GET /sapi/v1/futures/loan/calcMaxAdjustAmount
GET /sapi/v2/futures/loan/calcMaxAdjustAmount
POST /sapi/v1/futures/loan/adjustCollateral
POST /sapi/v2/futures/loan/adjustCollateral
GET /sapi/v1/futures/loan/collateralRepayLimit
GET /sapi/v1/futures/loan/collateralRepay
POST /sapi/v1/futures/loan/collateralRepay
GET /sapi/v1/futures/loan/collateralRepayResult
2022-09-30
Scheduled changes to the removal of !bookTicker
around November 2022.
- The All Book Tickers stream (
!bookTicker
) is set to be removed in November 2022 - More details of the actual removal date will be announced at a later time.
- Please use the Individual Book Ticker Streams instead. (
<symbol>@bookTicker
). - Multiple
<symbol>@bookTicker
streams can be subscribed to over one connection.- Example: wss://stream.binance.com:9443/stream?streams=btcusdt@bookTicker/bnbbtc@bookTicker
2022-09-29
- New endpoints for Wallet:
POST /sapi/v1/asset/convert-transfer
: Convert transfer, convert between BUSD and stablecoins.POST /sapi/v1/asset/convert-transfer/queryByPage
: Query convert transfer
2022-09-22
- Update endpoint for Sub-Account:
POST /sapi/v1/sub-account/subAccountApi/ipRestriction
: Add new paramthirdParty
POST /sapi/v1/sub-account/subAccountApi/ipRestriction/ipList
: Add new paramthirdPartyName
DELETE /sapi/v1/sub-account/subAccountApi/ipRestriction/ipList
: Add new paramthirdPartyName
- Add Rate Limit for following endpoints:
GET /sapi/v1/bswap/liquidity
: 3/1s per account and per poolGET /sapi/v1/bswap/quote
: 3/1s per account and per poolPOST /sapi/v1/lending/daily/purchase
: 1/3s per accountPOST /sapi/v1/lending/customizedFixed/purchase
: 1/3s per accountPOST /sapi/v1/staking/purchase
: 1/3s per account
2022-09-16
- New endpoint for Margin:
GET /sapi/v1/margin/tradeCoeff
: Get personal margin level information
2022-09-15
- New endpoints for Crypto Loan
POST /sapi/v1/loan/borrow
: Borrow - Crypto Loan BorrowGET /sapi/v1/loan/borrow/history
: Borrow - Get Loan Borrow HistoryGET/sapi/v1/loan/ongoing/orders
: Borrow - Get Loan Ongoing OrdersPOST/sapi/v1/loan/repay
: Repay - Crypto Loan RepayGET/sapi/v1/loan/repay/history
: Repay - Get Loan Repayment HistoryPOST/sapi/v1/loan/adjust/ltv
: Adjust LTV - Crypto Loan Adjust LTVGET/sapi/v1/loan/ltv/adjustment/history
: Adjust LTV - Get Loan LTV Adjustment History
2022-09-15
Note that these are rolling changes, so it may take a few days for it to rollout to all our servers.
- Changes to
GET /api/v3/exchangeInfo
- New optional parameter
permissions
added to display all symbols with the permissions matching the parameter provided. (eg.SPOT
,MARGIN
) - If not provided, the default value will be
["SPOT","MARGIN"]
.- This means the request
GET /api/v3/exchangeInfo
without any parameters will show all symbols that can be used forSPOT
,MARGIN
trading. - To search for symbols that can be traded on other permissions (e.g.
TRD_GRP_004
, etc), then this needs to be searched for explicitly. (e.g.permissions
=TRD_GRP_004
)
- This means the request
- Cannot be combined with
symbol
orsymbols
- New optional parameter
2022-09-12
- Update endpoint for Sub-account:
GET /sapi/v1/sub-account/subAccountApi/ipRestriction
: To support master account query Third party IP list name for a sub account API key
2022-09-05
- Delete endpoint for Futures:
GET /sapi/v1/futures/loan/wallet
2022-08-23
SPOT API
Note that these are rolling changes, so it may take a few days for it to rollout to all our servers.
- Changes to
GET /api/v3/ticker
andGET /api/v3/ticker/24hr
- New optional parameter
type
added - Supported values for parameter
type
areFULL
andMINI
FULL
is the default value and the response that is currently being returned from the endpointMINI
omits the following fields from the response:priceChangePercent
,weightedAvgPrice
,bidPrice
,bidQty
,askPrice
,askQty
, andlastQty
- New optional parameter
- New error code
-1008
- This is sent whenever the servers are overloaded with requests.
- This error code only appears for the SPOT API.
- New field
brokered
has been added toGET /api/v3/account
- New endpoint:
GET /api/v3/uiKlines
- New kline interval:
1s
2022-08-18
- Update endpoint for Convert:
GET /sapi/v1/convert/tradeFlow
: Update weight from Weight(IP) 3000 to Weight(UID) 3000.
2022-08-08
SPOT API
- Changes to
POST /api/v3/order
andPOST /api/v3/order/cancelReplace
- New optional field
strategyId
is a parameter used to identify an order as part of a strategy. - New optional field
strategyType
is a parameter used to identify what strategy was running. (E.g. If all the orders are part of spot grid strategy, it can be set tostrategyType=1000000
) - Note:
strategyType
cannot be less than1000000
.
- New optional field
- Changes to
POST /api/v3/order/oco
- New optional fields
limitStrategyId
,limitStrategyType
.stopStrategyId
,stopStrategyType
- These are the strategy metadata parameters for both legs of the OCO orders.
limitStrategyType
andstopStrategyType
both cannot be less than1000000
.
- New optional fields
- Changes to
GET /api/v3/order
,GET /api/v3/openOrders
, andGET /api/v3/allOrders
- New fields
strategyId
andstrategyType
will appear in the response JSON for orders that had these fields populated upon order placement.
- New fields
- Changes to
DELETE /api/v3/order
andDELETE /api/v3/openOrders
- New fields
strategyId
andstrategyType
will appear in the response JSON for cancelled orders that had these fields populated upon order placement.
- New fields
USER DATA STREAM
- New fields to eventType
executionReport
j
forstrategyId
J
forstrategyType
- Note that these fields only appear if these were populated upon order placement.
2022-08-05
- Update endpoint for Convert:
GET /sapi/v1/convert/tradeFlow
: Update weight from Weight(IP) 100 to Weight(IP) 3000.
2022-07-21
- New endpoint for Portfolio Margin:
GET /sapi/v1/portfolio/pmLoan
Query Portfolio Margin Bankruptcy Loan RecordPOST /sapi/v1/portfolio/repay
Portfolio Margin Bankruptcy Loan Repay
2022-07-18
- New endpoint for Portfolio Margin:
GET /sapi/v1/portfolio/collateralRate
to get Portfolio Margin Collateral Rate.
2022-07-01
- New endpoint for Wallet:
POST /sapi/v3/asset/getUserAsset
to get user assets.
- New endpoint for Margin:
GET /sapi/v1/margin/dribblet
to query the historical information of user's margin account small-value asset conversion BNB.
- Update endpoint for Convert:
GET /sapi/v1/convert/tradeFlow
: Update weight from 3000 to 100.
- Update endpoint for Margin:
GET /sapi/v1/margin/repay
: Add response field rawAsset.
2022-06-20
SPOT API: Changes to GET /api/v3/ticker
- Weight has been reduced from 5 to 2 per symbol, regardless of
windowSize
. - The max number of symbols that can be processed in a request is 100.
- If the number of
symbols
sent is more than 100, the error will be as follows:
- If the number of
{
"code": -1101,
"msg": "Too many values sent for parameter 'symbols', maximum allowed up to 100."
}
- The max Weight(IP) for this endpoint will cap at 100.
- I.e. If the request has more than 50 symbols, the Weight will still be 100, regardless of
windowSize
.
- I.e. If the request has more than 50 symbols, the Weight will still be 100, regardless of
2022-06-15
Note: The update is being rolled out over the next few days, so these changes may not be visible right away.
GET /api/v3/ticker
added- Rolling window price change statistics based on
windowSize
provided. - Contrary to
GET /api/v3/ticker/24hr
the list of symbols cannot be omitted. - If
windowSize
not specified, the value will default to1d
. - Response is similar to
GET /api/v3/ticker/24hr
, minus the following fields:prevClosePrice
,lastQty
,bidPrice
,bidQty
,askPrice
,askQty
- Rolling window price change statistics based on
POST /api/v3/order/cancelReplace
added- Cancels an existing order and places a new order on the same symbol.
- The filters are evaluated before the cancel order is placed.
- e.g. If the
MAX_NUM_ORDERS
filter is 10, and the total number of open orders on the account is also 10, when usingPOST /api/v3/order/cancelReplace
both the cancel order placement and new order will fail because of the filter.
- e.g. If the
- The change is being rolled out in the next few days, thus this feature will be enabled once the upgrade is completed.
GET /api/v3/exchangeInfo
returns new fieldcancelReplaceAllowed
insymbols
list.- New filter
NOTIONAL
has been added.- Defines the allowed notional value (
price * quantity
) based on a configuredminNotional
andmaxNotional
- Defines the allowed notional value (
- New exchange filter
EXCHANGE_MAX_NUM_ICEBERG_ORDERS
has been added.- Defines the limit of open iceberg orders on an account
WEBSOCKETS
- New symbol ticker streams with 1h and 4h windows:
- Individual symbol ticker streams
<symbol>@ticker_<window-size>
- All market ticker streams
!ticker_<window-size>@arr
- Individual symbol ticker streams
2022-06-02
- Update endpoint for Subaccount:
GET /sapi/v1/sub-account/sub/transfer/history
: fromEmail and toEmail can be master email.
2022-05-31
- Update endpoint for Fiat:
GET /sapi/v1/fiat/orders
: Weight changes from UID(3000) to UID(90000)
- Update endpoint for Pay:
GET /sapi/v1/pay/transactions
: Param names changed: startTimestamp -> startTime; endTimestamp -> endTime.
2022-05-26
- Update endpoint for Fiat:
GET /sapi/v1/fiat/orders
: Weight changes from IP(1) to UID(3000)
- Update info for the following margin account endpoints: The max interval between
startTime
andendTime
is 30 days.:GET /sapi/v1/margin/transfer
GET /sapi/v1/margin/loan
GET /sapi/v1/margin/repay
GET /sapi/v1/margin/isolated/transfer
GET /sapi/v1/margin/interestHistory
2022-05-23
- Changes to Order Book Depth Levels
- Quantities in the Depth levels were returning negative values in situations where they were exceeding the max value, resulting in an overflow.
- Going forward depth levels will not overflow, but will be capped at the max value based on the precision of the base asset. This means that the depth level is at max value or more.
- E.g. If the precision is 8, then the max value for quantity will be at 92,233,720,368.54775807.
- When the fix has been applied, a change in the order book at the affected price level is required for the changes to be visible.
What does this affect?
- SPOT API
GET /api/v3/depth
- Websocket Streams
<symbol>@depth
<symbol>@depth@100ms
<symbol>@depth<levels>
<symbol>@depth<levels>@100ms
- SPOT API
Updates to
MAX_POSITION
- If an order's
quantity
can cause the position to overflow, this will now fail theMAX_POSITION
filter.
- If an order's
2022-05-19
- Update endpoint for Mining:
GET /sapi/v1/mining/pub/algoList
andGET /sapi/v1/mining/pub/coinList
: Need no paramter.
- Add error codes (21xxx) for Portfolio Margin Account: -21001, -21002, -21003
2022-05-17
SPOT API
- Changes to
GET api/v3/aggTrades
- When providing
startTime
andendTime
, the oldest items are returned.
- When providing
- Changed error messaging on
GET /api/v3/myTrades
where parametersymbol
is not provided:
{
"code": -1102,
"msg": "Mandatory parameter 'symbol' was not sent, was empty/null, or malformed."
}
- The following endpoints now support multi-symbol querying using the parameter
symbols
.GET /api/v3/ticker/24hr
GET /api/v3/ticker/price
GET /api/v3/ticker/bookTicker
- In the above, the request weight will depend on the number of symbols provided in
symbols
.
Please refer to the table below:
Endpoint | Number of Symbols | Weight |
---|---|---|
GET /api/v3/ticker/price |
Any | 2 |
GET /api/v3/ticker/bookTicker |
Any | 2 |
GET /api/v3/ticker/24hr |
1-20 | 1 |
GET /api/v3/ticker/24hr |
21-100 | 20 |
GET /api/v3/ticker/24hr |
101 or more | 40 |
2022-05-05
- New endpoint for Binance Code:
GET /sapi/v1/giftcard/cryptography/rsa-public-key
to fetch RSA public key.
- Update endpoint for Binance Code:
POST /sapi/v1/giftcard/redeemCode
: new optional parameterexternalUid
. Each external unique ID represents a unique user on the partner platform. The function helps you to identify the redemption behavior of different users.
2022-04-28
- New endpoints for Staking:
GET /sapi/v1/staking/productList
to get Staking product listPOST /sapi/v1/staking/purchase
to stake productPOST /sapi/v1/staking/redeem
to redeem productGET /sapi/v1/staking/position
to get Staking product holding positionGET /sapi/v1/staking/stakingRecord
to inquiry Staking history recordsPOST /sapi/v1/staking/setAutoStaking
to set Auto Staking functionGET /sapi/v1/staking/personalLeftQuota
to inquiry Staking left quota
2022-04-27
- New endpoint for Futures Algo:
POST /sapi/v1/algo/futures/newOrderTwap
to support Twap new order
FAQ: Time-Weighted Average Price(Twap) Introduction
2022-04-26
GET /sapi/v1/margin/rateLimit/order
added- The endpoint will display the user's current margin order count usage for all intervals.
2022-04-20
- New endpoint for Portfolio Margin:
GET /sapi/v1/portfolio/account
to support query portfolio margin account info
Only Portfolio Margin Account is accessible to this endpoint. To enroll, kindly refer to: How to Enroll into the Binance Portfolio Margin Program
2022-04-13
- New endpoints for Futures Algo:
POST /sapi/v1/algo/futures/newOrderVp
to support VP new orderDELETE /sapi/v1/algo/futures/order
to support cancel Algo orderGET /sapi/v1/algo/futures/openOrders
to support query Algo open ordersGET /sapi/v1/algo/futures/historicalOrders
to support query Algo historical ordersGET /sapi/v1/algo/futures/subOrders
to support query Algo sub orders for a specified algoId
FAQ: Volume Participation(VP) Introduction
2022-04-13
Information on Trailing Stops
SPOT API
- Trailing Stops have been enabled.
- This is a type of algo order where the activation is based on a percentage of a price change in the market using the new parameter
trailingDelta
. - This can only used with any of the following order types:
STOP_LOSS
,STOP_LOSS_LIMIT
,TAKE_PROFIT
,TAKE_PROFIT_LIMIT
. - The
trailingDelta
parameter will be done in Basis Points or BIPS.- For example: a STOP_LOSS SELL order with a
trailingDelta
of 100 will trigger after a price decrease of 1%. (100 / 10,000 => 0.01 => 1%)
- For example: a STOP_LOSS SELL order with a
- When used in combination with OCO Orders, the
trailingDelta
will determine when the contingent leg of the OCO will trigger. - When
trailingDelta
is used in combination withstopPrice
, once thestopPrice
condition is met, the trailing stop starts tracking the price change from thestopPrice
based on thetrailingDelta
provided. - When no
stopPrice
is sent, the trailing stop starts tracking the price changes from the last price based on thetrailingDelta
provided.
- This is a type of algo order where the activation is based on a percentage of a price change in the market using the new parameter
- Changes to POST
/api/v3/order
- New optional field
trailingDelta
- New optional field
- Changes to POST
/api/v3/order/test
- New optional field
trailingDelta
- New optional field
- Changes to POST
/api/v3/order/oco
- New optional field
trailingDelta
- New optional field
- A new filter
TRAILING_DELTA
has been added.- This filter is defined by the minimum and maximum values for the
trailingDelta
value.
- This filter is defined by the minimum and maximum values for the
USER DATA STREAM
- New field in
executionReport
- "d" for
trailingDelta
- "d" for
2022-04-12
Note: The changes are being rolled out during the next few days, so these will not appear right away.
- Error message changed on
GET api/v3/allOrders
wheresymbol
is not provided:
{ "code": -1102, "msg": "Mandatory parameter 'symbol' was not sent, was empty/null, or malformed." }
- Fixed a typo with an error message when an account has disabled permissions (e.g. to withdraw, to trade, etc)
"This action is disabled on this account."
- During a market data audit, we detected some issues with the Spot aggregate trade data.
- Missing aggregate trades were recovered.
- Duplicated records were marked invalid with the following values:
- p = '0' // price
- q = '0' // qty
- f = -1 // first_trade_id
- l = -1 // last_trade_id
2022-3-29
The following updates will take effect on March 31, 2022 08:00 AM UTC
- Update endpoint for Sub-account:
GET /sapi/v1/sub-account/universalTransfer
The query time period must be less then 30 days; If startTime
and endTime
not sent, return records of the last 30 days by default
2022-03-25
- Update endpoint for Sub-Account:
- New endpoint
GET /sapi/v1/managed-subaccount/accountSnapshot
to support investor master account query asset snapshot of managed sub-account
- New endpoint
2022-03-08
- Update endpoint for Sub-Account:
- New transfer types
MARGIN
,ISOLATED_MARGIN
and parametersymbol
added inPOST /sapi/v1/sub-account/universalTransfer
to support transfer to sub-account cross margin account and isolated margin account
- New transfer types
2022-02-28
- New field
allowTrailingStop
has been added toGET /api/v3/exchangeInfo
2022-02-22
SPOT API
(price-minPrice) % tickSize == 0
rule inPRICE_FILTER
has been changed toprice % tickSize == 0
.- A new filter
PERCENT_PRICE_BY_SIDE
has been added. - Changes to GET
api/v3/depth
- The
limit
value can be outside of the previous values (i.e. 5, 10, 20, 50, 100, 500, 1000,5000) and will return the correct limit. (i.e. if limit=3 then the response will be the top 3 bids and asks) - The limit still cannot exceed 5000. If the limit provided is greater than 5000, then the response will be truncated to 5000.
- Due to the changes, these are the updated request weights based on the limit value provided:
- The
Limit | Request Weight |
---|---|
1-100 | 1 |
101-500 | 5 |
501-1000 | 10 |
1001-5000 | 50 |
- Changes to GET
api/v3/aggTrades
- When providing
startTime
andendTime
, the oldest items are returned.
- When providing
2022-2-18
- Update endpoint for Sub-Account:
- New fields
isManagedSubAccount
andisAssetManagementSubAccount
added inGET /sapi/v1/sub-account/list
to support query whether the sub-account is a managed sub-account or a asset management sub-account
- New fields
2022-2-17
The following updates will take effect on February 24, 2022 08:00 AM UTC
- Update endpoint for Wallet:
GET /sapi/v1/accountSnapshot
The time limit of this endpoint is shortened to only support querying the data of the latest month
2022-2-09
- New endpoint for Wallet:
POST /sapi/v1/asset/dust-btc
to get assets that can be converted into BNB
2022-1-25
- From January 28, 2022 4:00 AM UTC, You need to open
Enable Spot & Margin Trading
permission for the API key which requests these endpoints as following:POST /sapi/v1/asset/dust
Dust transferPOST /sapi/v1/lending/daily/purchase
Purchase Savings flexible productPOST /sapi/v1/lending/daily/redeem
Redeem Savings flexible productPOST /sapi/v1/lending/customizedFixed/purchase
Purchase Savings Fixed/Activity projectPOST /sapi/v1/lending/positionChanged
Change Savings Fixed/Activity position to Daily positionPOST /sapi/v1/bswap/liquidityAdd
Bswap add liquidityPOST /sapi/v1/bswap/liquidityRemove
Bswap remove liquidityPOST /sapi/v1/bswap/swap
Bswap swapPOST /sapi/v1/bswap/claimRewards
Bswap claim rewards
2022-1-21
- New endpoints for Binance Code:
POST /sapi/v1/giftcard/createCode
to create a Binance Code.POST /sapi/v1/giftcard/redeemCode
to redeem a Binance Code.GET /sapi/v1/giftcard/verify
to verify a Binance Code.
2022-1-4
New endpoint for Mining:
GET /sapi/v1/mining/payment/uid
to get Mining account earning.
New endpoints for BSwap:
GET /sapi/v1/bswap/unclaimedRewards
to get unclaimed rewards record.POST /sapi/v1/bswap/claimRewards
to claim swap rewards or liquidity rewards.GET /sapi/v1/bswap/claimedHistory
to get history of claimed rewards.
2021-12-30
Update endpoint for Margin:
- Removed out
limit
fromGET /sapi/v1/margin/interestRateHistory
; The max interval between startTime and endTime is 30 days.
- Removed out
Update endpoint for Wallet:
- As the Mining account is merged into Funding account, transfer types MAIN_MINING, MINING_MAIN, MINING_UMFUTURE, MARGIN_MINING, and MINING_MARGIN will be discontinued in Universal Transfer endpoint
POST /sapi/v1/asset/transfer
on January 05, 2022 08:00 AM UTC
- As the Mining account is merged into Funding account, transfer types MAIN_MINING, MINING_MAIN, MINING_UMFUTURE, MARGIN_MINING, and MINING_MARGIN will be discontinued in Universal Transfer endpoint
2021-12-29
- Removed out dated "Symbol Type" enum; added "Permissions" enum.
2021-12-24
- Update endpoints for Sub-Account:
- New parameter
clientTranId
added inPOST /sapi/v1/sub-account/universalTransfer
andGET /sapi/v1/sub-account/universalTransfer
to support custom transfer id
- New parameter
2021-12-03
New endpoints for Margin:
GET /sapi/v1/margin/crossMarginData
to get cross margin fee data collectionGET /sapi/v1/margin/isolatedMarginData
to get isolated margin fee data collectionGET /sapi/v1/margin/isolatedMarginTier
to get isolated margin tier data collection
New endpoints for NFT:
GET /sapi/v1/nft/history/transactions
to get NFT transaction historyGET /sapi/v1/nft/history/deposit
to get NFT deposit historyGET /sapi/v1/nft/history/withdraw
to get NFT withdraw historyGET /sapi/v1/nft/user/getAsset
to get NFT asset
2021-11-30
New endpoint for Convert:
GET /sapi/v1/convert/tradeFlow
to support user query convert trade history records
New endpoint for Rebate:
GET /sapi/v1/rebate/taxQuery
to support user query spot rebate history records
2021-11-19
New endpoint for Pay:
GET /sapi/v1/pay/transactions
to support user query Pay trade history
Update endpoint for Wallet:
- New field
info
added inGET /sapi/v1/capital/withdraw/history
to show the reason for withdrawal failure
- New field
2021-11-18
The following updates will take effect on November 25, 2021 08:00 AM UTC
- Update endpoint for Wallet:
GET /sapi/v1/accountSnapshot
The query time range of both endpoints are shortened to support data query within the last 6 months only, where startTime does not support selecting a timestamp beyond 6 months. If you do not specify startTime and endTime, the data of the last 7 days will be returned by default.
2021-11-17
- The following endpoints will be discontinued on November 17, 2021 13:00 PM UTC:
POST /sapi/v1/account/apiRestrictions/ipRestriction
to support user enable and disable IP restriction for an API KeyPOST /sapi/v1/account/apiRestrictions/ipRestriction/ipList
to support user add IP list for an API KeyGET /sapi/v1/account/apiRestrictions/ipRestriction
to support user query IP restriction for an API KeyDELETE /sapi/v1/account/apiRestrictions/ipRestriction/ipList
to support user delete IP list for an API Key
2021-11-16
- New endpoints for Sub-Account:
POST /sapi/v1/sub-account/subAccountApi/ipRestriction
to support master account enable and disable IP restriction for a sub-account API KeyPOST /sapi/v1/sub-account/subAccountApi/ipRestriction/ipList
to support master account add IP list for a sub-account API KeyGET /sapi/v1/sub-account/subAccountApi/ipRestriction
to support master account query IP restriction for a sub-account API KeyDELETE /sapi/v1/sub-account/subAccountApi/ipRestriction/ipList
to support master account delete IP list for a sub-account API Key
2021-11-09
- New endpoints for Wallet:
POST /sapi/v1/account/apiRestrictions/ipRestriction
to support user enable and disable IP restriction for an API KeyPOST /sapi/v1/account/apiRestrictions/ipRestriction/ipList
to support user add IP list for an API KeyGET /sapi/v1/account/apiRestrictions/ipRestriction
to support user query IP restriction for an API KeyDELETE /sapi/v1/account/apiRestrictions/ipRestriction/ipList
to support user delete IP list for an API Key
2021-11-08
- New endpoint for Crypto Loans:
- New endpoint
GET /sapi/v1/loan/income
to support user query crypto loans income history
- New endpoint
2021-11-05
- Update endpoint for Wallet:
- New parameter
walletType
added inPOST /sapi/v1/capital/withdraw/apply
to support user choose wallet typespot wallet
andfunding wallet
when withdraw crypto.
- New parameter
2021-11-04
The following updates will take effect on November 11, 2021 08:00 AM UTC
- Update endpoints for Wallet and Futures:
GET /sapi/v1/asset/transfer
GET /sapi/v1/futures/transfer
The query time range of both endpoints are shortened to support data query within the last 6 months only, where startTime does not support selecting a timestamp beyond 6 months. If you do not specify startTime and endTime, the data of the last 7 days will be returned by default.
2021-11-01
GET /api/v3/rateLimit/order
added- The endpoint will display the user's current order count usage for all intervals.
- This endpoint will have a request weight of 20.
2021-10-22
- Update endpoint for Wallet:
- New transfer types
MAIN_FUNDING
,FUNDING_MAIN
,FUNDING_UMFUTURE
,UMFUTURE_FUNDING
,MARGIN_FUNDING
,FUNDING_MARGIN
,FUNDING_CMFUTURE
andCMFUTURE_FUNDING
added in Universal Transfer endpointPOST /sapi/v1/asset/transfer
andGET /sapi/v1/asset/transfer
to support transfer assets among funding account and other accounts - As the C2C account, Binance Payment, Binance Card and other business account are merged into a Funding account, transfer types
MAIN_C2C
,C2C_MAIN
,C2C_UMFUTURE
,C2C_MINING
,UMFUTURE_C2C
,MINING_C2C
,MARGIN_C2C
,C2C_MARGIN
,MAIN_PAY
andPAY_MAIN
will be discontinued in Universal Transfer endpointPOST /sapi/v1/asset/transfer
andGET /sapi/v1/asset/transfer
on November 04, 2021 08:00 AM UTC
- New transfer types
2021-10-14
- Update the time range of the response data for the following margin account endpoints,
startTime
andendTime
time span will not exceed 30 days, without time parameter sent the system will return the last 7 days of data by default, while thearchived
parameter istrue
, the system will return the last 7 days of data 6 months ago by default:GET /sapi/v1/margin/transfer
GET /sapi/v1/margin/loan
GET /sapi/v1/margin/repay
GET /sapi/v1/margin/isolated/transfer
GET /sapi/v1/margin/interestHistory
2021-09-18
- New endpoints for BSwap:
GET /sapi/v1/bswap/poolConfigure
to get pool configureGET /sapi/v1/bswap/addLiquidityPreview
to get add liquidity previewGET /sapi/v1/bswap/removeLiquidityPreview
to get remove liquidity preview
2021-09-17
- Add
/api/*
and/sapi/*
limit introduction in General Info
2021-09-08
Add endpoints for enabled isolated margin account limit:
DELETE /sapi/v1/margin/isolated/account
to disable isolated margin account for a specific symbolPOST /sapi/v1/margin/isolated/account
to enable isolated margin account for a specific symbolGET /sapi/v1/margin/isolated/accountLimit
to query enabled isolated margin account limit
New field "enabled" in response of
GET /sapi/v1/margin/isolated/account
to check if the isolated margin account is enabled
2021-09-03
- Update endpoint for Wallet:
- New fields
sameAddress
,depositDust
andspecialWithdrawTips
added inGET /sapi/v1/capital/config/getall
sameAddress
means if the coin needs to provide memo to withdrawdepositDust
means minimum creditable amountspecialWithdrawTips
means special tips for withdraw - New field
confirmNo
added inGET /sapi/v1/capital/withdraw/history
to support query confirm times for withdraw history
- New fields
2021-08-27
- Update endpoint for Wallet:
- New parameter
withdrawOrderId
added inGET /sapi/v1/capital/withdraw/history
to support user query withdraw history by withdrawOrderId - New field
unlockConfirm
added inGET /sapi/v1/capital/deposit/hisrec
to support query network confirm times for unlocking
- New parameter
2021-08-23
- New endpoints for Margin Account OCO:
POST /sapi/v1/margin/order/oco
DELETE /sapi/v1/margin/orderList
GET /sapi/v1/margin/orderList
GET /sapi/v1/margin/allOrderList
GET /sapi/v1/margin/openOrderList
Same usage as spot account OCO
2021-08-20
- Update endpoint for Wallet:
- New parameters
fromSymbol
,toSymbol
and new transfer typesISOLATEDMARGIN_MARGIN
,MARGIN_ISOLATEDMARGIN
andISOLATEDMARGIN_ISOLATEDMARGIN
added inPOST /sapi/v1/asset/transfer
andGET /sapi/v1/asset/transfer
to support user transfer assets between Margin(cross) account and Margin(isolated) account
- New parameters
2021-08-12
- GET
api/v3/myTrades
has a new optional fieldorderId
2021-08-05
- New endpoint for C2C:
GET /sapi/v1/c2c/orderMatch/listUserOrderHistory
to query user C2C trade history
2021-08-05
- Update endpoints for Savings:
GET /sapi/v1/lending/union/purchaseRecord
GET /sapi/v1/lending/union/redemptionRecord
GET /sapi/v1/lending/union/interestHistory
The time between startTime
and endTime
cannot be longer than 30 days. If startTime
and endTime
are both not sent, then the last 30 days' data will be returned
2021-07-29
- Update endpoint for Sub-Account:
GET /sapi/v1/sub-account/transfer/subUserHistory
ifstartTime
andendTime
are not sent, the recent 30-day data will be returned by default
2021-07-27
- New endpoint for Fiat:
GET /sapi/v1/fiat/orders
to query user fiat deposit and withdraw historyGET /sapi/v1/fiat/payments
to query user fiat payments history
2021-07-16
- New endpoint for Wallet:
GET /sapi/v1/account/apiRestrictions
to query user API Key permission
2021-07-09
- New endpoint for Wallet:
POST /sapi/v1/asset/get-funding-asset
to query funding wallet, includes Binance Pay, Binance Card, Binance Gift Card, Stock Token
2021-06-24
- Update endpoints for Wallet:
GET /sapi/v1/capital/withdraw/history
added default value 1000, max value 1000 for the parameterlimit
GET /sapi/v1/capital/deposit/hisrec
added default value 1000, max value 1000 for the parameterlimit
2021-06-17
- Update endpoint for Savings:
GET /sapi/v1/lending/daily/product/list
to include new parameterscurrent
andsize
2021-06-15
- New endpoints for Sub-Account:
POST /sapi/v1/managed-subaccount/deposit
to deposit assets into the managed sub-account (only for investor master account)GET /sapi/v1/managed-subaccount/asset
to query managed sub-account asset details (only for investor master account)POST /sapi/v1/managed-subaccount/withdraw
to withdrawal assets from the managed sub-account (only for investor master account)
2021-06-04
On August 01, 2021 02:00 AM UTC the WAPI endpoints will be discontinued:
GET /wapi/v3/systemStatus.html
POST /wapi/v3/withdraw.html
GET /wapi/v3/depositHistory.html
GET /wapi/v3/withdrawHistory.html
GET /wapi/v3/depositAddress.html
GET /wapi/v3/accountStatus.html
GET /wapi/v3/apiTradingStatus.html
GET /wapi/v3/userAssetDribbletLog.html
GET /wapi/v3/assetDetail.html
GET /wapi/v3/tradeFee.html
GET /wapi/v3/sub-account/list.html
GET /wapi/v3/sub-account/transfer/history.html
POST /wapi/v3/sub-account/transfer.html
GET /wapi/v3/sub-account/assets.html
The WAPI endpoints have been removed from Binance API Documentation.To ensure your trading strategies are not affected, all API users are encouraged to upgrade trading bots to SAPI endpoints as soon as possible.
2021-05-26
- Update endpoint for Wallet:
- New transfer types
MAIN_PAY
,PAY_MAIN
added in Universal Transfer endpointPOST /sapi/v1/asset/transfer
andGET /sapi/v1/asset/transfer
to support trasnfer assets between spot account and pay account
- New transfer types
2021-05-12
- Added
Data Source
in the documentation to explain where each endpoint is retrieving its data - Added field
Data Source
to each Spot API endpoint in the documentation - GET
api/v3/exchangeInfo
now supports single or multi-symbol query
2021-04-28
On May 15, 2021 08:00 UTC the SAPI Create Margin Account endpoint will be discontinued:
POST /sapi/v1/margin/isolated/create
Isolated Margin account creation and trade preparation can be completed directly through Isolated Margin funds transfer POST /sapi/v1/margin/isolated/transfer
2021-04-26
On April 28, 2021 00:00 UTC the weights to the following endpoints will be adjusted:
GET /api/v3/order
weight increased to 2GET /api/v3/openOrders
weight increased to 3GET /api/v3/allOrders
weight increased to 10GET /api/v3/orderList
weight increased to 2GET /api/v3/openOrderList
weight increased to 3GET /api/v3/account
weight increased to 10GET /api/v3/myTrades
weight increased to 10GET /api/v3/exchangeInfo
weight increased to 10
2021-04-08
- Update endpoint for Sub-Account:
GET /sapi/v1/sub-account/futures/accountSummary
andGET /sapi/v2/sub-account/futures/accountSummary
the unit of fieldasset
changed to USD valued summary of sub-account assets
2021-04-02
- New endpoints for Wallet:
GET /sapi/v1/system/status
to query system statusGET /sapi/v1/account/status
to query account statusGET /sapi/v1/account/apiTradingStatus
to query account API trading statusGET /sapi/v1/asset/dribblet
to query dust logGET /sapi/v1/asset/assetDetail
to query asset detailGET /sapi/v1/asset/tradeFee
to query trade fee
- New endpoint for Sub-Account:
GET /sapi/v3/sub-account/assets
to query sub-account assets
2021-04-01
- Update endpoint for Sub-Account:
GET /sapi/v1/sub-account/transfer/subUserHistory
new fieldsfromAccountType
andtoAccountType
added in response
2021-03-31
- Update endpoint for Sub-Account:
GET /wapi/v3/sub-account/transfer/history.html
added new parametersfromEmail
andtoEmail
, the original parameteremail
is equal tofromEmail
by default
2021-03-08
- New endpoint for Sub-Account:
POST /sapi/v1/sub-account/virtualSubAccount
to support create a virtual sub-accountGET /sapi/v1/sub-account/list
to support query sub-account list
2021-03-05
- New endpoints for Margin:
-
GET /sapi/v1/margin/interestRateHistory
to support margin interest rate history query
-
2021-02-08
- New endpoints for Futures:
-
GET /sapi/v2/futures/loan/wallet
to support BUSD loan query -
GET /sapi/v2/futures/loan/configs
to support BUSD loan query -
GET /sapi/v2/futures/loan/calcAdjustLevel
to support BUSD loan -
GET /sapi/v2/futures/loan/calcMaxAdjustAmount
to support adjustment of BUSD loan -
POST /sapi/v2/futures/loan/adjustCollateral
to support adjustment of BUSD loan
-
- Update endpoints for Futures
-
GET /sapi/v1/futures/loan/adjustCollateral/history
new parameter and fields in responseloanCoin
for BUSD loan -
GET /sapi/v1/futures/loan/liquidationHistory
new parameter and fields in responseloanCoin
for BUSD loan
-
2021-02-04
- New transfer types
MARGIN_MINING
,MINING_MARGIN
,MARGIN_C2C
,C2C_MARGIN
,MARGIN_CMFUTURE
,CMFUTURE_MARGIN
added in Universal Transfer endpointPOST /sapi/v1/asset/transfer
andGET /sapi/v1/asset/transfer
.
2021-01-15
- New endpoint
DELETE /sapi/v1/margin/openOrders
for Margin Trade- This will allow a user to cancel all open orders on a single symbol for margin account.
- This endpoint will cancel all open orders including OCO orders for margin account.
2021-01-10
- New parameter
pageSize
for Mining endpointGET /sapi/v1/mining/payment/list
New fields in response to Mining endpoint
GET /sapi/v1/mining/payment/list
:- "type" for income type
- "hashTransfer" for resale Hashrate
- "transferAmount" for transferred Income
New Mining endpoints:
GET /sapi/v1/mining/payment/other
GET /sapi/v1/mining/hash-transfer/config/details
GET /sapi/v1/mining/hash-transfer/config/details/list
GET /sapi/v1/mining/hash-transfer/profit/details
POST /sapi/v1/mining/hash-transfer/config
POST /sapi/v1/mining/hash-transfer/config/cancel
2021-01-01
USER DATA STREAM
outboundAccountInfo
has been removed.
2020-12-30
- New endpoint for Wallet:
POST /sapi/v1/asset/transfer
to support user universal transfer among Spot, Margin, Futures, C2C, MINING accounts.GET /sapi/v1/asset/transfer
to get user universal transfer history.
2020-12-22
- New endpoint for Sub-Account:
GET /sapi/v1/sub-account/sub/transfer/history
to get spot asset transfer history.
2020-12-11
- Update endpoints for Futures Cross-Collateral:
GET /sapi/v1/futures/loan/wallet
new fields in responseinterestFreeLimit
for total interest free limit,interestFreeLimitUsed
for interest free limit used.GET /sapi/v1/futures/loan/interestHistory
new fields in responseinterestFreeLimitUsed
for interest free limit used.
2020-12-02
- New endpoints for Sub-Account:
GET /sapi/v2/sub-account/futures/account
to get detail on sub-account's USDT margined futures account and COIN margined futures account.GET /sapi/v2/sub-account/futures/accountSummary
to get summary of sub-account's USDT margined futures account and COIN margined futures account.GET /sapi/v2/sub-account/futures/positionRisk
to get position risk of sub-account's USDT margined futures account and COIN margined futures account.
2020-12-01
- Update Margin Trade Endpoint:
POST /sapi/v1/margin/order
new parameterquoteOrderQty
allow a user to specify the totalquoteOrderQty
spent or received in theMARKET
order.
2020-11-27
New API clusters have been added in order to improve performance.
Users can access any of the following API clusters, in addition to api.binance.com
If there are any performance issues with accessing api.binance.com
please try any of the following instead:
- https://api1.binance.com/api/v3/*
- https://api2.binance.com/api/v3/*
- https://api3.binance.com/api/v3/*
2020-11-16
- Updated endpoints for Margin, new parameter
archived
to query data from 6 months ago:GET /sapi/v1/margin/loan
GET /sapi/v1/margin/repay
GET /sapi/v1/margin/interestHistory
2020-11-13
- New endpoints for Sub-Account:
POST /sapi/v1/sub-account/universalTransfer
to transfer spot and futures asset between master account and sub accounts.GET /sapi/v1/sub-account/universalTransfer
to search transfer records.
2020-11-10
- New endpoint to toggle BNB Burn:
POST /sapi/v1/bnbBurn
to toggle BNB Burn on spot trade and margin interest.GET /sapi/v1/bnbBurn
to get BNB Burn status.
2020-11-09
- New field
tranId
is available from endpoints:GET /sapi/v1/sub-account/futures/internalTransfer
GET /sapi/v1/sub-account/transfer/subUserHistory
2020-11-03
Update endpoints for Futures Cross-Collateral:
GET /sapi/v1/futures/loan/repay/history
new fields in responserepayType
(NORMAL
for normal repayment,COLLATERAL
for collateral repayment),price
(collateral repayment rate),repayCollateral
(collateral amount for collateral repayment).GET /sapi/v1/futures/loan/wallet
new fields in responsetotalInterest
(total interest for cross-collateral),principalForInterest
(cross-collateral principal for interest),interest
(cross-collateral interest).GET /sapi/v1/futures/loan/configs
new fields in responseinterestRate
(interest rate for cross-collateral),interestGracePeriod
(interest grace period for cross-collateral).
New endpoints for Futures Cross-Collateral:
GET /sapi/v1/futures/loan/collateralRepayLimit
to check the maximum and minimum limit when repay with collateral.GET /sapi/v1/futures/loan/collateralRepay
to get quote for collateral repayment.POST /sapi/v1/futures/loan/collateralRepay
to repay with collateral.GET /sapi/v1/futures/loan/collateralRepayResult
to check collateral repayment result.GET /sapi/v1/futures/loan/interestHistory
to get cross-collateral interest history.
2020-10-14
- Update endpoints for Futures Cross-Collateral:
POST /sapi/v1/futures/loan/borrow
andGET /sapi/v1/futures/loan/borrow/history
new fieldborrowId
in response for ID of Cross-Collateral borrow operation.POST /sapi/v1/futures/loan/repay
andGET /sapi/v1/futures/loan/repay/history
new fieldrepayId
in response for ID of Cross-Collateral repay operation.
2020-10-10
- New
type
added in the endpointPOST /sapi/v1/sub-account/futures/transfer
to support transfer asset from subaccount's spot account to its COIN-margined futures account and transfer asset from subaccount's COIN-margined futures account to its spot account.
2020-09-30
- Update endpoints for Margin Account:
GET /sapi/v1/margin/maxBorrowable
new fieldborrowLimit
in response for account borrow limit.
2020-09-28
- New endpoints for Binance Savings:
POST /sapi/v1/lending/positionChanged
to change fixed/activity position to daily position.
- New parameter
ACTIVITY
replaceREGULAR
in the following Binance Savings endpoints:GET /sapi/v1/lending/project/list
POST /sapi/v1/lending/customizedFixed/purchase
GET /sapi/v1/lending/project/position/list
GET /sapi/v1/lending/union/purchaseRecord
GET /sapi/v1/lending/union/interestHistory
2020-09-23
- New SAPI endpoints for BSwap:
GET /sapi/v1/bswap/pools
to list all swap pools.GET /sapi/v1/bswap/liquidity
to get liquidity information of a pool.POST /sapi/v1/bswap/liquidityAdd
to add liquidity.POST /sapi/v1/bswap/liquidityRemove
to remove liquidity.GET /sapi/v1/bswap/liquidityOps
to get liquidity operation record.GET /sapi/v1/bswap/quote
to request quotes.POST /sapi/v1/bswap/swap
to swap.GET /sapi/v1/bswap/swap
to get swap history.
2020-09-09
USER DATA STREAM
outboundAccountInfo
has been deprecated.outboundAccountInfo
will be removed in the future. (Exact date unknown) Please useoutboundAccountPosition
instead.outboundAccountInfo
will now only show the balance of non-zero assets and assets that have been reduced to 0.
2020-09-03
- New endpoint
POST /sapi/v1/sub-account/futures/internalTransfer
to transfer futures asset between master account and subaccount. - New endpoint
GET /sapi/v1/sub-account/futures/internalTransfer
to get futures transfer history of subaccount.
2020-09-01
- New parameter
masterAccountTotalAsset
added in the endpointGET /sapi/v1/sub-account/spotSummary
to get BTC valued asset summary of master account.
2020-08-27
- New endpoint
GET /sapi/v1/sub-account/spotSummary
to get BTC valued asset summary of subaccout.
2020-08-26
- New parameter
symbols
added in the endpointGET /sapi/v1/margin/isolated/account
.
2020-07-28
ISOLATED MARGIN
New parameters "isIsolated" and "symbol" added for isolated margin in the following endpoints:
POST /sapi/v1/margin/loan
POST /sapi/v1/margin/repay
New parameter "isIsolated" and new response field "isIsolated" added for isolated margin in the following endpoints:
POST /sapi/v1/margin/order
DELETE /sapi/v1/margin/order
GET /sapi/v1/margin/order
GET /sapi/v1/margin/openOrders
GET /sapi/v1/margin/allOrders
GET /sapi/v1/margin/myTrades
New parameter "isolatedSymbol" and new response field "isolatedSymbol" added for isolated margin in the following endpoints:
GET /sapi/v1/margin/loan
GET /sapi/v1/margin/repay
GET /sapi/v1/margin/interestHistory
New parameter "isolatedSymbol" and new response field "isIsolated" added for isolated margin in the following endpoint
GET /sapi/v1/margin/forceLiquidationRec
New parameter "isolatedSymbol" added for isolated margin in the following endpoints:
GET /sapi/v1/margin/maxBorrowable
GET /sapi/v1/margin/maxTransferable
New endpoints for isolated margin:
POST /sapi/v1/margin/isolated/create
POST /sapi/v1/margin/isolated/transfer
GET /sapi/v1/margin/isolated/transfer
GET /sapi/v1/margin/isolated/account
GET /sapi/v1/margin/isolated/pair
GET /sapi/v1/margin/isolated/allPairs
New endpoints for listenKey management of isolated margin account:
POST /sapi/v1/userDataStream/isolated
PUT /sapi/v1/userDataStream/isolated
DELETE /sapi/v1/userDataStream/isolated
2020-07-20
- The max value of parameter "limit" in
GET /sapi/v1/margin/allOrders
has been changed as 500.
2020-07-17
- There is now a request limit specifically for the sapi/v1/margin/allOrders endpoint at 60 raw requests per minute for a single IP address.
2020-07-13
- New SAPI Endpoints for futures Cross-Collateral:
POST /sapi/v1/futures/loan/borrow
GET /sapi/v1/futures/loan/borrow/history
POST /sapi/v1/futures/loan/repay
GET /sapi/v1/futures/loan/repay/history
GET /sapi/v1/futures/loan/wallet
GET /sapi/v1/futures/loan/configs
GET /sapi/v1/futures/loan/calcAdjustLevel
GET /sapi/v1/futures/loan/calcMaxAdjustAmount
POST /sapi/v1/futures/loan/adjustCollateral
GET /sapi/v1/futures/loan/adjustCollateral/history
GET /sapi/v1/futures/loan/liquidationHistory
2020-06-28
- SAPI Endpoints for futures:
POST /sapi/v1/futures/transfer
GET /sapi/v1/futures/transfer
2020-05-06
- New endpoints for Mining:
GET /sapi/v1/mining/pub/algoList
GET /sapi/v1/mining/pub/coinList
GET /sapi/v1/mining/worker/detail
GET /sapi/v1/mining/worker/list
GET /sapi/v1/mining/payment/list
GET /sapi/v1/mining/statistics/user/status
GET /sapi/v1/mining/statistics/user/list
2020-05-01
- From 2020-05-01 UTC 00:00, all symbols will have a limit of 200 open orders using the MAX_NUM_ORDERS filter.
- No existing orders will be removed or canceled.
- Accounts that have 200 or more open orders on a symbol will not be able to place new orders on that symbol until the open order count is below 200.
- OCO orders count as 2 open orders before the
LIMIT
order is touched or theSTOP_LOSS
(orSTOP_LOSS_LIMIT
) order is triggered; once this happens the other order is canceled and will no longer count as an open order.
2020-04-25
SPOT API
- New field
permissions
- Defines the trading permissions that are allowed on accounts and symbols.
permissions
is an enum array; values:SPOT
MARGIN
permissions
will replaceisSpotTradingAllowed
andisMarginTradingAllowed
onGET api/v3/exchangeInfo
in future API versions (v4+).- For an account to trade on a symbol, the account and symbol must share at least 1 permission in common.
- Updates to GET
api/v3/exchangeInfo
- New field
permissions
added. - New field
quoteAssetPrecision
added; a duplicate of thequotePrecision
field.quotePrecision
will be removed in future API versions (v4+).
- New field
- Updates to GET
api/v3/account
- New field
permissions
added.
- New field
- New endpoint DELETE
api/v3/openOrders
- This will allow a user to cancel all open orders on a single symbol.
- This endpoint will cancel all open orders including OCO orders.
- Orders can be canceled via the API on symbols in the
BREAK
orHALT
status.
USER DATA STREAM
OutboundAccountInfo
has new fieldP
which shows the trading permissions of the account.
2020-04-23
WEB SOCKET STREAM
- WebSocket connections have a limit of 5 incoming messages per second. A message is considered:
- A PING frame
- A PONG frame
- A JSON control message (e.g. subscribe, unsubscribe)
- A connection that goes beyond the limit will be disconnected; IPs that are repeatedly disconnected may be banned.
- A single connection can listen to a maximum of 1024 streams.
2020-04-16
New fields in response to endpoint
GET /sapi/v1/lending/daily/token/position
:todayPurchasedAmount
for user's purchased amount today
New lending endpoints for customized fixed projects:
GET /sapi/v1/lending/project/list
POST /sapi/v1/lending/customizedFixed/purchase
GET /sapi/v1/lending/project/position/list
2020-04-02
- New fields in response to endpoint
GET /sapi/v1/capital/config/getall
:minConfirm
for min number for balance confirmationunLockConfirm
for confirmation number for balance unlock
2020-03-24
MAX_POSITION
filter added.- This filter defines the allowed maximum position an account can have on the base asset of a symbol. An account's position defined as the sum of the account's:
- free balance of the base asset
- locked balance of the base asset
- sum of the qty of all open BUY orders
BUY
orders will be rejected if the account's position is greater than the maximum position allowed.
- This filter defines the allowed maximum position an account can have on the base asset of a symbol. An account's position defined as the sum of the account's:
2020-03-13
- New parameter
transactionFeeFlag
is available in endpoint:POST /sapi/v1/capital/withdraw/apply
andPOST /wapi/v3/withdraw.html
2020-02-05
- New sub account endpoints:
POST /sapi/v1/sub-account/futures/transfer
to transfer between futures and spot accout of sub-account.POST /sapi/v1/sub-account/margin/transfer
to transfer between margin and spot accout of sub-account.POST /sapi/v1/sub-account/transfer/subToSub
to transfer to another account by sub-account.POST /sapi/v1/sub-account/transfer/subToMaster
to transfer to same master by sub-account.GET /sapi/v1/sub-account/transfer/subUserHistory
to get transfer history of sub-account.
2020-01-15
New parameter
withdrawOrderId
for client customized withdraw id for endpointPOST /wapi/v3/withdraw.html
.New field
withdrawOrderId
in response toGET /wapi/v3/withdrawHistory.html
2019-12-25
New endpoints for Binance Savings:
GET /sapi/v1/lending/daily/product/list
GET /sapi/v1/lending/daily/userLeftQuota
POST /sapi/v1/lending/daily/purchase
GET /sapi/v1/lending/daily/userRedemptionQuota
POST /sapi/v1/lending/daily/redeem
GET /sapi/v1/lending/daily/token/position
GET /sapi/v1/lending/union/account
GET /sapi/v1/lending/union/purchaseRecord
GET /sapi/v1/lending/union/redemptionRecord
GET /sapi/v1/lending/union/interestHistory
Added time interval limit in
GET /sapi/v1/capital/withdraw/history
,
GET /wapi/v3/withdrawHistory.html
,
GET /sapi/v1/capital/deposit/hisrec
and
GET /wapi/v3/depositHistory.html
:- The default
startTime
is 90 days from current time, and the defaultendTime
is current time. - Please notice the default
startTime
andendTime
to make sure that time interval is within 0-90 days. - If both
startTime
andendTime
are sent, time betweenstartTime
andendTime
must be less than 90 days.
- The default
2019-12-18
- New endpoint to get daily snapshot of account:
GET /sapi/v1/accountSnapshot
2019-11-30
Added parameter
sideEffectType
inPOST /sapi/v1/margin/order (HMAC SHA256)
with enums:NO_SIDE_EFFECT
for normal trade order;MARGIN_BUY
for margin trade order;AUTO_REPAY
for making auto repayment after order filled.
New field
marginBuyBorrowAmount
andmarginBuyBorrowAsset
inFULL
response toPOST /sapi/v1/margin/order (HMAC SHA256)
2019-11-28
- New SAPI endpont to disable fast withdraw switch:
POST /sapi/v1/account/disableFastWithdrawSwitch (HMAC SHA256)
- New SAPI endpont to enable fast withdraw switch:
POST /sapi/v1/account/enableFastWithdrawSwitch (HMAC SHA256)
2019-11-22
- Quote Order Qty Market orders have been enabled on all symbols.
- Quote Order Qty
MARKET
orders allow a user to specify the totalquoteOrderQty
spent or received in theMARKET
order. - Quote Order Qty
MARKET
orders will not breakLOT_SIZE
filter rules; the order will execute a quantity that will have the notional value as close as possible toquoteOrderQty
. - Using
BNBBTC
as an example:- On the
BUY
side, the order will buy as many BNB asquoteOrderQty
BTC can. - On the
SELL
side, the order will sell as much BNB as needed to receivequoteOrderQty
BTC.
- On the
- Quote Order Qty
2019-11-19
GET /sapi/v1/sub-account/margin/account
has new field:marginTradeCoeffVo
which containsforceLiquidationBar
for liquidation margin ratiomarginCallBar
for margin call margin rationormalBar
for initial margin ratio
2019-11-13
Rest API
- api/v3/exchangeInfo has new fields:
quoteOrderQtyMarketAllowed
baseCommissionPrecision
quoteCommissionPrecision
MARKET
orders have a new optional field:quoteOrderQty
used to specify the quote quantity to BUY or SELL. This cannot be used in combination withquantity
.- The exact timing that
quoteOrderQty
MARKET orders will be enabled is TBD. There will be a separate announcement and further details at that time.
- The exact timing that
- All order query endpoints will return a new field
origQuoteOrderQty
in the JSON payload. (e.g. GET api/v3/allOrders)
{
"code": -1128,
"msg": "Combination of optional parameters invalid. Recommendation: 'stopLimitTimeInForce' should also be sent."
}
Updated error messages for -1128
- Sending an
OCO
with astopLimitPrice
but without astopLimitTimeInForce
will return the error:
- Sending an
Updated error messages for -1003 to specify the limit is referring to the request weight, not to the number of requests.
Deprecation of v1 endpoints:
By end of Q1 2020, the following endpoints will be removed from the API. The documentation has been updated to use the v3 versions of these endpoints.
- GET api/v1/depth
- GET api/v1/historicalTrades
- GET api/v1/aggTrades
- GET api/v1/klines
- GET api/v1/ticker/24hr
- GET api/v1/ticker/price
- GET api/v1/exchangeInfo
- POST api/v1/userDataStream
- PUT api/v1/userDataStream
- GET api/v1/ping
- GET api/v1/time
- GET api/v1/ticker/bookTicker
These endpoints however, will NOT be migrated to v3. Please use the following endpoints instead moving forward.
Old V1 Endpoints | New V3 Endpoints |
---|---|
GET api/v1/ticker/allPrices | GET api/v3/ticker/price |
GET api/v1/ticker/allBookTickers | GET api/v3/ticker/bookTicker |
USER DATA STREAM
Changes to
executionReport
event- If the C field is empty, it will now properly return
null
, instead of"null"
. - New field Q which represents the
quoteOrderQty
.
- If the C field is empty, it will now properly return
balanceUpdate
event type added- This event occurs when funds are deposited or withdrawn from your account.
WEB SOCKET STREAM
- WSS now supports live subscribing/unsubscribing to streams.
2019-11-08
- New sapi for subaccount management on margin and futures:
GET /sapi/v1/sub-account/status (HMAC SHA256)
POST /sapi/v1/sub-account/margin/enable (HMAC SHA256)
GET /sapi/v1/sub-account/margin/account (HMAC SHA256)
GET /sapi/v1/sub-account/margin/accountSummary (HMAC SHA256)
POST /sapi/v1/sub-account/futures/enable (HMAC SHA256)
GET /sapi/v1/sub-account/futures/account (HMAC SHA256)
GET /sapi/v1/sub-account/futures/accountSummary (HMAC SHA256)
GET /sapi/v1/sub-account/futures/positionRisk (HMAC SHA256)
2019-11-04
- New sapi endpoints for subaccount wallet.
GET /sapi/v1/capital/deposit/subAddress (HMAC SHA256))
: fetch subaccount deposit address.GET /sapi/v1/capital/deposit/subHisrec (HMAC SHA256))
: fetch subaccount deposit history.
2019-10-29
- New sapi endpoints for wallet.
POST /sapi/v1/capital/withdraw/apply (HMAC SHA256)
: withdraw.Get /sapi/v1/capital/withdraw/history (HMAC SHA256)
: fetch withdraw history with network.
2019-10-14
- New sapi endpoints for wallet.
GET /sapi/v1/capital/config/getall (HMAC SHA256)
: get all coins' information for user.GET /sapi/v1/capital/deposit/hisrec (HMAC SHA256)
: fetch deposit history with network.GET /sapi/v1/capital/deposit/address (HMAC SHA256)
: fetch deposit address with network.
2019-10-11
- Added parameter
network
inPOST /wapi/v3/withdraw.html
so that asset can be withdrawed with specific network.
2019-09-09
- New WebSocket streams for bookTickers added:
<symbol>@bookTicker
and!bookTicker
.
2019-09-03
- Faster order book data with 100ms updates:
<symbol>@depth@100ms
and<symbol>@depth#@100ms
- Added "Update Speed:" to
Websocket Market Streams
- Removed deprecated v1 endpoints as per previous announcement:
- GET api/v1/order
- GET api/v1/openOrders
- POST api/v1/order
- DELETE api/v1/order
- GET api/v1/allOrders
- GET api/v1/account
- GET api/v1/myTrades
2019-08-16
GET api/v1/depth
limit
of 10000 has been temporarily removedIn Q4 2017, the following endpoints were deprecated and removed from the API documentation. They have been permanently removed from the API as of this version. We apologize for the omission from the original changelog:
- GET api/v1/order
- GET api/v1/openOrders
- POST api/v1/order
- DELETE api/v1/order
- GET api/v1/allOrders
- GET api/v1/account
- GET api/v1/myTrades
Streams, endpoints, parameters, payloads, etc. described in the documents in this repository are considered official and supported. The use of any other streams, endpoints, parameters, or payloads, etc. is not supported; use them at your own risk and with no guarantees.
2019-09-15
Rest API
New order type: OCO ("One Cancels the Other")
- An OCO has 2 orders: (also known as legs in financial terms)
STOP_LOSS
orSTOP_LOSS_LIMIT
legLIMIT_MAKER
leg
- Price Restrictions:
SELL Orders
: Limit Price > Last Price > Stop PriceBUY Orders
: Limit Price < Last Price < Stop Price- As stated, the prices must "straddle" the last traded price on the symbol. EX: If the last price is 10:
- A SELL OCO must have the limit price greater than 10, and the stop price less than 10.
- A BUY OCO must have a limit price less than 10, and the stop price greater than 10.
- Quantity Restrictions:
- Both legs must have the same quantity.
ICEBERG
quantities however, do not have to be the same.
- Execution Order:
- If the
LIMIT_MAKER
is touched, the limit maker leg will be executed first BEFORE canceling the Stop Loss Leg. - if the Market Price moves such that the
STOP_LOSS
orSTOP_LOSS_LIMIT
will trigger, the Limit Maker leg will be cancelled BEFORE executing theSTOP_LOSS
Leg.
- If the
- Cancelling an OCO
- Cancelling either order leg will cancel the entire OCO.
- The entire OCO can be canceled via the
orderListId
or thelistClientOrderId
.
- New Enums for OCO:
ListStatusType
RESPONSE
- used when ListStatus is responding to a failed action. (either order list placement or cancellation)EXEC_STARTED
- used when an order list has been placed or there is an update to a list's status.ALL_DONE
- used when an order list has finished executing and is no longer active.
ListOrderStatus
EXECUTING
- used when an order list has been placed or there is an update to a list's status.ALL_DONE
- used when an order list has finished executing and is no longer active.REJECT
- used when ListStatus is responding to a failed action. (either order list placement or cancellation)
ContingencyType
OCO
- specifies the type of order list.
- New Endpoints:
- POST api/v3/order/oco
- DELETE api/v3/orderList
- GET api/v3/orderList
- An OCO has 2 orders: (also known as legs in financial terms)
recvWindow
cannot exceed 60000.New
intervalLetter
values for headers:- SECOND => S
- MINUTE => M
- HOUR => H
- DAY => D
New Headers
X-MBX-USED-WEIGHT-(intervalNum)(intervalLetter)
will give your current used request weight for the (intervalNum)(intervalLetter) rate limiter. For example, if there is a one minute request rate weight limiter set, you will get aX-MBX-USED-WEIGHT-1M
header in the response. The legacy headerX-MBX-USED-WEIGHT
will still be returned and will represent the current used weight for the one minute request rate weight limit.New Header
X-MBX-ORDER-COUNT-(intervalNum)(intervalLetter)
that is updated on any valid order placement and tracks your current order count for the interval; rejected/unsuccessful orders are not guaranteed to haveX-MBX-ORDER-COUNT-**
headers in the response.- Eg.
X-MBX-ORDER-COUNT-1S
for "orders per 1 second" andX-MBX-ORDER-COUNT-1D
for orders per "one day"
- Eg.
GET api/v1/depth now supports
limit
5000 and 10000; weights are 50 and 100 respectively.GET api/v1/exchangeInfo has a new parameter
ocoAllowed
.
USER DATA STREAM
executionReport
event now contains "g" which has theorderListId
; it will be set to -1 for non-OCO orders.- New Event Type
listStatus
;listStatus
is sent on an update to any OCO order. - New Event Type
outboundAccountPosition
;outboundAccountPosition
is sent any time an account's balance changes and contains the assets that could have changed by the event that generated the balance change (a deposit, withdrawal, trade, order placement, or cancelation).
NEW ERRORS
- -1131 BAD_RECV_WINDOW
recvWindow
must be less than 60000
- -1099 Not found, authenticated, or authorized
- This replaces error code -1999
NEW -2011 ERRORS
- OCO_BAD_ORDER_PARAMS
- A parameter for one of the orders is incorrect.
- OCO_BAD_PRICES
- The relationship of the prices for the orders is not correct.
- UNSUPPORTED_ORD_OCO
- OCO orders are not supported for this symbol.
2019-03-12
Rest API
- X-MBX-USED-WEIGHT header added to Rest API responses.
- Retry-After header added to Rest API 418 and 429 responses.
- When canceling the Rest API can now return
errorCode
-1013 OR -2011 if the symbol'sstatus
isn'tTRADING
. api/v1/depth
no longer has the ignored and empty[]
.api/v3/myTrades
now returnsquoteQty
; the price * qty of for the trade.
Websocket streams
<symbol>@depth
and<symbol>@depthX
streams no longer have the ignored and empty[]
.
System improvements
- Matching Engine stability/reliability improvements.
- Rest API performance improvements.
2018-11-13
Rest API
- Can now cancel orders through the Rest API during a trading ban.
- New filters:
PERCENT_PRICE
,MARKET_LOT_SIZE
,MAX_NUM_ICEBERG_ORDERS
. - Added
RAW_REQUESTS
rate limit. Limits based on the number of requests over X minutes regardless of weight. - /api/v3/ticker/price increased to weight of 2 for a no symbol query.
- /api/v3/ticker/bookTicker increased weight of 2 for a no symbol query.
- DELETE /api/v3/order will now return an execution report of the final state of the order.
MIN_NOTIONAL
filter has two new parameters:applyToMarket
(whether or not the filter is applied to MARKET orders) andavgPriceMins
(the number of minutes over which the price averaged for the notional estimation).intervalNum
added to /api/v1/exchangeInfo limits.intervalNum
describes the amount of the interval. For example:intervalNum
5, withinterval
minute, means "every 5 minutes".
Explanation for the average price calculation:
(qty * price) of all trades / sum of qty of all trades over previous 5 minutes.
If there is no trade in the last 5 minutes, it takes the first trade that happened outside of the 5min window. For example if the last trade was 20 minutes ago, that trade's price is the 5 min average.
If there is no trade on the symbol, there is no average price and market orders cannot be placed. On a new symbol with
applyToMarket
enabled on theMIN_NOTIONAL
filter, market orders cannot be placed until there is at least 1 trade.The current average price can be checked here:
https://api.binance.com/api/v3/avgPrice?symbol=<symbol>
For example: https://api.binance.com/api/v3/avgPrice?symbol=BNBUSDT
User data stream
Last quote asset transacted quantity
(as variableY
) added to execution reports. Represents thelastPrice
*lastQty
(L
*l
).
2018-07-18
Rest API
- New filter:
ICEBERG_PARTS
-
POST api/v3/order
new defaults fornewOrderRespType
.ACK
,RESULT
, orFULL
;MARKET
andLIMIT
order types default toFULL
, all other orders default toACK
. - POST api/v3/order
RESULT
andFULL
responses now havecummulativeQuoteQty
- GET api/v3/openOrders with no symbol weight reduced to 40.
- GET api/v3/ticker/24hr with no symbol weight reduced to 40.
- Max amount of trades from GET /api/v1/trades increased to 1000.
- Max amount of trades from GET /api/v1/historicalTrades increased to 1000.
- Max amount of aggregate trades from GET /api/v1/aggTrades increased to 1000.
- Max amount of aggregate trades from GET /api/v1/klines increased to 1000.
- Rest API Order lookups now return
updateTime
which represents the last time the order was updated;time
is the order creation time. - Order lookup endpoints will now return
cummulativeQuoteQty
. IfcummulativeQuoteQty
is < 0, it means the data isn't available for this order at this time. -
REQUESTS
rate limit type changed toREQUEST_WEIGHT
. This limit was always logically request weight and the previous name for it caused confusion.
User data stream
-
cummulativeQuoteQty
field added to order responses and execution reports (as variableZ
). Represents the cummulative amount of thequote
that has been spent (with aBUY
order) or received (with aSELL
order). Historical orders will have a value < 0 in this field indicating the data is not available at this time.cummulativeQuoteQty
divided bycummulativeQty
will give the average price for an order. -
O
(order creation time) added to execution reports
2018-01-23
- GET /api/v1/historicalTrades weight decreased to 5
- GET /api/v1/aggTrades weight decreased to 1
- GET /api/v1/klines weight decreased to 1
- GET /api/v1/ticker/24hr all symbols weight decreased to number of trading symbols / 2
- GET /api/v3/allOrders weight decreased to 5
- GET /api/v3/myTrades weight decreased to 5
- GET /api/v3/account weight decreased to 5
- GET /api/v1/depth limit=500 weight decreased to 5
- GET /api/v1/depth limit=1000 weight decreased to 10
- -1003 error message updated to direct users to websockets
2018-01-20
- GET /api/v1/ticker/24hr single symbol weight decreased to 1
- GET /api/v3/openOrders all symbols weight decreased to number of trading symbols / 2
- GET /api/v3/allOrders weight decreased to 15
- GET /api/v3/myTrades weight decreased to 15
- GET /api/v3/order weight decreased to 1
- myTrades will now return both sides of a self-trade/wash-trade
2018-01-14
- GET /api/v1/aggTrades weight changed to 2
- GET /api/v1/klines weight changed to 2
- GET /api/v3/order weight changed to 2
- GET /api/v3/allOrders weight changed to 20
- GET /api/v3/account weight changed to 20
- GET /api/v3/myTrades weight changed to 20
- GET /api/v3/historicalTrades weight changed to 20
Introduction
API Key Setup
- Some endpoints will require an API Key. Please refer to this page regarding API key creation.
- Once API key is created, it is recommended to set IP restrictions on the key for security reasons.
- Never share your API key/secret key to ANYONE.
API Key Restrictions
- After creating the API key, the default restrictions is
Enable Reading
. - To enable withdrawals via the API, the API key restriction needs to be modified through the Binance UI.
Enabling Accounts
Spot Account
A SPOT
account is provided by default upon creation of a Binance Account.
Margin Account
To enable a MARGIN
account for Margin Trading, please refer to the Margin Trading Guide
Spot Testnet
Users can use the SPOT Testnet to practice SPOT
trading.
Currently, this is only available via the API.
Please refer to the SPOT Testnet page for more information and how to set up the Testnet API key.
API Library
Connectors
The following are lightweight libraries that work as connectors to the Binance public API, written in different languages:
- Python https://github.com/binance/binance-connector-python
- Node.js https://github.com/binance/binance-connector-node
- Ruby https://github.com/binance/binance-connector-ruby
- DotNET C# https://github.com/binance/binance-connector-dotnet
- Java https://github.com/binance/binance-connector-java
- Rust https://github.com/binance/binance-spot-connector-rust
- PHP https://github.com/binance/binance-connector-php
- Go https://github.com/binance/binance-connector-go
- Typescript https://github.com/binance/binance-connector-typescript
Postman Collections
Postman collections are available, and they are recommended for new users seeking a quick and easy start with the API.
https://github.com/binance/binance-api-postman
Swagger
A YAML file with OpenAPI specification for the RESTful API is available, along with a Swagger UI page for reference.
https://github.com/binance/binance-api-swagger
Contact Us
- Binance API Telegram Group
- For any questions in sudden drop in performance with the API and/or Websockets.
- For any general questions about the API not covered in the documentation.
- Binance Developers
- For any questions on your code implementation with the API and/or Websockets.
- Binance Customer Support
- For cases such as missing funds, help with 2FA, etc.
General Info
General API Information
- The following base endpoints are available:
- https://api.binance.com
- https://api-gcp.binance.com
- https://api1.binance.com
- https://api2.binance.com
- https://api3.binance.com
- https://api4.binance.com
- The last 4 endpoints in the point above (
api1
-api4
) might give better performance but have less stability. Please use whichever works best for your setup. - All endpoints return either a JSON object or array.
- Data is returned in ascending order. Oldest first, newest last.
- All time and timestamp related fields are in milliseconds.
- The base endpoint https://data-api.binance.vision can be used to access the following API endpoints that have
NONE
as security type:
HTTP Return Codes
- HTTP
4XX
return codes are used for malformed requests; the issue is on the sender's side. - HTTP
403
return code is used when the WAF Limit (Web Application Firewall) has been violated. - HTTP
409
return code is used when a cancelReplace order partially succeeds. (e.g. if the cancellation of the order fails but the new order placement succeeds.) - HTTP
429
return code is used when breaking a request rate limit. - HTTP
418
return code is used when an IP has been auto-banned for continuing to send requests after receiving429
codes. - HTTP
5XX
return codes are used for internal errors; the issue is on Binance's side. It is important to NOT treat this as a failure operation; the execution status is UNKNOWN and could have been a success.
Error Codes and Messages
- If there is an error, the API will return an error with a message of the reason.
The error payload on API and SAPI is as follows:
{
"code": -1121,
"msg": "Invalid symbol."
}
- Specific error codes and messages defined in Error Codes.
General Information on Endpoints
- For
GET
endpoints, parameters must be sent as aquery string
. - For
POST
,PUT
, andDELETE
endpoints, the parameters may be sent as aquery string
or in therequest body
with content typeapplication/x-www-form-urlencoded
. You may mix parameters between both thequery string
andrequest body
if you wish to do so. - Parameters may be sent in any order.
- If a parameter sent in both the
query string
andrequest body
, thequery string
parameter will be used.
LIMITS
General Info on Limits
- The following
intervalLetter
values for headers:- SECOND => S
- MINUTE => M
- HOUR => H
- DAY => D
intervalNum
describes the amount of the interval. For example,intervalNum
5 withintervalLetter
M means "Every 5 minutes".- The
/api/v3/exchangeInfo
rateLimits
array contains objects related to the exchange'sRAW_REQUESTS
,REQUEST_WEIGHT
, andORDERS
rate limits. These are further defined in theENUM definitions
section underRate limiters (rateLimitType)
. - A 429 will be returned when either request rate limit or order rate limit is violated.
IP Limits
- Every request will contain
X-MBX-USED-WEIGHT-(intervalNum)(intervalLetter)
in the response headers which has the current used weight for the IP for all request rate limiters defined. - Each route has a
weight
which determines for the number of requests each endpoint counts for. Heavier endpoints and endpoints that do operations on multiple symbols will have a heavierweight
. - When a 429 is received, it's your obligation as an API to back off and not spam the API.
- Repeatedly violating rate limits and/or failing to back off after receiving 429s will result in an automated IP ban (HTTP status 418).
- IP bans are tracked and scale in duration for repeat offenders, from 2 minutes to 3 days.
- A
Retry-After
header is sent with a 418 or 429 responses and will give the number of seconds required to wait, in the case of a 429, to prevent a ban, or, in the case of a 418, until the ban is over. - The limits on the API are based on the IPs, not the API keys.
Unfilled Order Count
- Every successful order response will contain a
X-MBX-ORDER-COUNT-(intervalNum)(intervalLetter)
header indicating how many orders you have placed for that interval.
To monitor this, refer toGET api/v3/rateLimit/order
. - Rejected/unsuccessful orders are not guaranteed to have
X-MBX-ORDER-COUNT-**
headers in the response. - If you have exceeded this, you will receive a 429 error without the
Retry-After
header. - Please note that if your orders are consistently filled by trades, you can continuously place orders on the API. For more information, please see Spot Unfilled Order Count Rules.
- The number of unfilled orders is tracked for each account.
Websocket Limits
- WebSocket connections have a limit of 5 incoming messages per second. A message is considered:
- A PING frame
- A PONG frame
- A JSON controlled message (e.g. subscribe, unsubscribe)
- A connection that goes beyond the limit will be disconnected; IPs that are repeatedly disconnected may be banned.
- A single connection can listen to a maximum of 1024 streams.
- There is a limit of 300 connections per attempt every 5 minutes per IP.
/api/ and /sapi/ Limit Introduction
The /api/*
and /sapi/*
endpoints adopt either of two access limiting rules, IP limits or UID (account) limits.
Endpoints related to
/api/*
:- According to the two modes of IP and UID (account) limit, each are independent.
- Endpoints share the 6,000 per minute limit based on IP.
- Responses contain the header
X-MBX-USED-WEIGHT-(intervalNum)(intervalLetter)
, defining the weight used by the current IP. - Successful order responses contain the header
X-MBX-ORDER-COUNT-(intervalNum)(intervalLetter)
, defining the order limit used by the UID.
Endpoints related to
/sapi/*
:- Endpoints are marked according to IP or UID limit and their corresponding weight value.
- Each endpoint with IP limits has an independent 12000 per minute limit, or per second limit if specified explicitly
- Each endpoint with UID limits has an independent 180000 per minute limit, or per second limit if specified explicitly
- Responses from endpoints with IP limits contain the header
X-SAPI-USED-IP-WEIGHT-1M
orX-SAPI-USED-IP-WEIGHT-1S
, defining the weight used by the current IP. - Responses from endpoints with UID limits contain the header
X-SAPI-USED-UID-WEIGHT-1M
orX-SAPI-USED-UID-WEIGHT-1S
, defining the weight used by the current UID.
Data Sources
- The API system is asynchronous, so some delay in the response is normal and expected.
- Each endpoint has a data source indicating where the data is being retrieved, and thus which endpoints have the most up-to-date response.
These are the three sources, ordered by which is has the most up-to-date response to the one with potential delays in updates.
- Matching Engine - the data is from the matching Engine
- Memory - the data is from a server's local or external memory
- Database - the data is taken directly from a database
Endpoint security type
- Each endpoint has a security type that determines how you will
interact with it. This is stated next to the NAME of the endpoint.
- If no security type is stated, assume the security type is NONE.
- API-keys are passed into the REST API via the
X-MBX-APIKEY
header. - API-keys and secret-keys are case sensitive.
- API-keys can be configured to only access certain types of secure endpoints. For example, one API-key could be used for TRADE only, while another API-key can access everything except for TRADE routes.
- By default, API-keys can access all secure routes.
Security Type | Description |
---|---|
NONE | Endpoint can be accessed freely. |
TRADE | Endpoint requires sending a valid API-Key and signature. |
MARGIN | Endpoint requires sending a valid API-Key and signature. |
USER_DATA | Endpoint requires sending a valid API-Key and signature. |
USER_STREAM | Endpoint requires sending a valid API-Key. |
MARKET_DATA | Endpoint requires sending a valid API-Key. |
TRADE
,MARGIN
andUSER_DATA
endpoints areSIGNED
endpoints.
SIGNED (TRADE, USER_DATA, AND MARGIN) Endpoint security
SIGNED
endpoints require an additional parameter,signature
, to be sent in thequery string
orrequest body
.- The
signature
is not case sensitive. - Please consult the examples on how to compute the signature, depending on which API key you are using. (e.g. HMAC, RSA, Ed25519)
Timing security
- A
SIGNED
endpoint also requires a parameter,timestamp
, to be sent which should be the millisecond timestamp of when the request was created and sent. - An additional parameter,
recvWindow
, may be sent to specify the number of milliseconds aftertimestamp
the request is valid for. IfrecvWindow
is not sent, it defaults to 5000.
The logic is as follows:
if (timestamp < (serverTime + 1000) && (serverTime - timestamp) <= recvWindow)
{
// process request
}
else
{
// reject request
}
Serious trading is about timing. Networks can be unstable and unreliable,
which can lead to requests taking varying amounts of time to reach the
servers. With recvWindow
, you can specify that the request must be
processed within a certain number of milliseconds or be rejected by the
server.
SIGNED Endpoint Examples for POST /api/v3/order - HMAC Keys
Here is a step-by-step example of how to send a vaild signed payload from the
Linux command line using echo
, openssl
, and curl
.
Key | Value |
---|---|
apiKey | vmPUZE6mv9SD5VNHk4HlWFsOr6aKE2zvsw0MuIgwCIPy6utIco14y7Ju91duEh8A |
secretKey | NhqPtmdSJYdKjVHjA7PZj4Mge3R5YNiP1e3UZjInClVN65XAbvqqM6A7H5fATj0j |
Parameter | Value |
---|---|
symbol | LTCBTC |
side | BUY |
type | LIMIT |
timeInForce | GTC |
quantity | 1 |
price | 0.1 |
recvWindow | 5000 |
timestamp | 1499827319559 |
Example 1: As a request body
Example 1
HMAC SHA256 signature:
$ echo -n "symbol=LTCBTC&side=BUY&type=LIMIT&timeInForce=GTC&quantity=1&price=0.1&recvWindow=5000×tamp=1499827319559" | openssl dgst -sha256 -hmac "NhqPtmdSJYdKjVHjA7PZj4Mge3R5YNiP1e3UZjInClVN65XAbvqqM6A7H5fATj0j"
(stdin)= c8db56825ae71d6d79447849e617115f4a920fa2acdcab2b053c4b2838bd6b71
curl command:
(HMAC SHA256)
$ curl -H "X-MBX-APIKEY: vmPUZE6mv9SD5VNHk4HlWFsOr6aKE2zvsw0MuIgwCIPy6utIco14y7Ju91duEh8A" -X POST 'https://api.binance.com/api/v3/order' -d 'symbol=LTCBTC&side=BUY&type=LIMIT&timeInForce=GTC&quantity=1&price=0.1&recvWindow=5000×tamp=1499827319559&signature=c8db56825ae71d6d79447849e617115f4a920fa2acdcab2b053c4b2838bd6b71'
- requestBody:
symbol=LTCBTC
&side=BUY
&type=LIMIT
&timeInForce=GTC
&quantity=1
&price=0.1
&recvWindow=5000
×tamp=1499827319559
Example 2: As a query string
Example 2
HMAC SHA256 signature:
$ echo -n "symbol=LTCBTC&side=BUY&type=LIMIT&timeInForce=GTC&quantity=1&price=0.1&recvWindow=5000×tamp=1499827319559" | openssl dgst -sha256 -hmac "NhqPtmdSJYdKjVHjA7PZj4Mge3R5YNiP1e3UZjInClVN65XAbvqqM6A7H5fATj0j"
(stdin)= c8db56825ae71d6d79447849e617115f4a920fa2acdcab2b053c4b2838bd6b71
curl command:
(HMAC SHA256)
$ curl -H "X-MBX-APIKEY: vmPUZE6mv9SD5VNHk4HlWFsOr6aKE2zvsw0MuIgwCIPy6utIco14y7Ju91duEh8A" -X POST 'https://api.binance.com/api/v3/order?symbol=LTCBTC&side=BUY&type=LIMIT&timeInForce=GTC&quantity=1&price=0.1&recvWindow=5000×tamp=1499827319559&signature=c8db56825ae71d6d79447849e617115f4a920fa2acdcab2b053c4b2838bd6b71'
- queryString:
symbol=LTCBTC
&side=BUY
&type=LIMIT
&timeInForce=GTC
&quantity=1
&price=0.1
&recvWindow=5000
×tamp=1499827319559
Example 3: Mixed query string and request body
Example 3
HMAC SHA256 signature:
$ echo -n "symbol=LTCBTC&side=BUY&type=LIMIT&timeInForce=GTCquantity=1&price=0.1&recvWindow=5000×tamp=1499827319559" | openssl dgst -sha256 -hmac "NhqPtmdSJYdKjVHjA7PZj4Mge3R5YNiP1e3UZjInClVN65XAbvqqM6A7H5fATj0j"
(stdin)= 0fd168b8ddb4876a0358a8d14d0c9f3da0e9b20c5d52b2a00fcf7d1c602f9a77
curl command:
(HMAC SHA256)
$ curl -H "X-MBX-APIKEY: vmPUZE6mv9SD5VNHk4HlWFsOr6aKE2zvsw0MuIgwCIPy6utIco14y7Ju91duEh8A" -X POST 'https://api.binance.com/api/v3/order?symbol=LTCBTC&side=BUY&type=LIMIT&timeInForce=GTC' -d 'quantity=1&price=0.1&recvWindow=5000×tamp=1499827319559&signature=0fd168b8ddb4876a0358a8d14d0c9f3da0e9b20c5d52b2a00fcf7d1c602f9a77'
- queryString:
symbol=LTCBTC&side=BUY&type=LIMIT&timeInForce=GTC
- requestBody:
quantity=1&price=0.1&recvWindow=5000×tamp=1499827319559
Note that the signature is different in example 3. There is no & between "GTC" and "quantity=1".
SIGNED Endpoint Example for POST /api/v3/order - RSA Keys
- This will be a step by step process how to create the signature payload to send a valid signed payload.
- We support
PKCS#8
currently. - To get your API key, you need to upload your RSA Public Key to your account and a corresponding API key will be provided for you.
For this example, the private key will be referenced as test-prv-key.pem
Key | Value |
---|---|
apiKey | CAvIjXy3F44yW6Pou5k8Dy1swsYDWJZLeoK2r8G4cFDnE9nosRppc2eKc1T8TRTQ |
Parameter | Value |
---|---|
symbol | BTCUSDT |
side | SELL |
type | LIMIT |
timeInForce | GTC |
quantity | 1 |
price | 0.2 |
recvWindow | 5000 |
timestamp | 1668481559918 |
Signature payload (with the listed parameters):
symbol=BTCUSDT&side=SELL&type=LIMIT&timeInForce=GTC&quantity=1&price=0.2×tamp=1668481559918&recvWindow=5000
Step 1: Construct the payload
Arrange the list of parameters into a string. Separate each parameter with a &
.
Step 2: Compute the signature:
2.1 - Encode signature payload as ASCII data.
Step 2.2
$ echo -n 'symbol=BTCUSDT&side=SELL&type=LIMIT&timeInForce=GTC&quantity=1&price=0.2×tamp=1668481559918&recvWindow=5000' | openssl dgst -sha256 -sign ./test-prv-key.pem
2.2 - Sign payload using RSASSA-PKCS1-v1_5 algorithm with SHA-256 hash function.
Step 2.3
$ echo -n 'symbol=BTCUSDT&side=SELL&type=LIMIT&timeInForce=GTC&quantity=1&price=0.2×tamp=1668481559918&recvWindow=5000' | openssl dgst -sha256 -sign ./test-prv-key.pem | openssl enc -base64 -A
HZ8HOjiJ1s/igS9JA+n7+7Ti/ihtkRF5BIWcPIEluJP6tlbFM/Bf44LfZka/iemtahZAZzcO9TnI5uaXh3++lrqtNonCwp6/245UFWkiW1elpgtVAmJPbogcAv6rSlokztAfWk296ZJXzRDYAtzGH0gq7CgSJKfH+XxaCmR0WcvlKjNQnp12/eKXJYO4tDap8UCBLuyxDnR7oJKLHQHJLP0r0EAVOOSIbrFang/1WOq+Jaq4Efc4XpnTgnwlBbWTmhWDR1pvS9iVEzcSYLHT/fNnMRxFc7u+j3qI//5yuGuu14KR0MuQKKCSpViieD+fIti46sxPTsjSemoUKp0oXA==
2.3 - Encode output as base64 string.
Step 2.4
HZ8HOjiJ1s%2FigS9JA%2Bn7%2B7Ti%2FihtkRF5BIWcPIEluJP6tlbFM%2FBf44LfZka%2FiemtahZAZzcO9TnI5uaXh3%2B%2BlrqtNonCwp6%2F245UFWkiW1elpgtVAmJPbogcAv6rSlokztAfWk296ZJXzRDYAtzGH0gq7CgSJKfH%2BXxaCmR0WcvlKjNQnp12%2FeKXJYO4tDap8UCBLuyxDnR7oJKLHQHJLP0r0EAVOOSIbrFang%2F1WOq%2BJaq4Efc4XpnTgnwlBbWTmhWDR1pvS9iVEzcSYLHT%2FfNnMRxFc7u%2Bj3qI%2F%2F5yuGuu14KR0MuQKKCSpViieD%2BfIti46sxPTsjSemoUKp0oXA%3D%3D
2.4 - Since the signature may contain /
and =
, this could cause issues with sending the request. So the signature has to be URL encoded.
Step 2.5
curl -H "X-MBX-APIKEY: CAvIjXy3F44yW6Pou5k8Dy1swsYDWJZLeoK2r8G4cFDnE9nosRppc2eKc1T8TRTQ" -X POST 'https://api.binance.com/api/v3/order?symbol=BTCUSDT&side=SELL&type=LIMIT&timeInForce=GTC&quantity=1&price=0.2×tamp=1668481559918recvWindow=5000&signature=HZ8HOjiJ1s%2FigS9JA%2Bn7%2B7Ti%2FihtkRF5BIWcPIEluJP6tlbFM%2FBf44LfZka%2FiemtahZAZzcO9TnI5uaXh3%2B%2BlrqtNonCwp6%2F245UFWkiW1elpgtVAmJPbogcAv6rSlokztAfWk296ZJXzRDYAtzGH0gq7CgSJKfH%2BXxaCmR0WcvlKjNQnp12%2FeKXJYO4tDap8UCBLuyxDnR7oJKLHQHJLP0r0EAVOOSIbrFang%2F1WOq%2BJaq4Efc4XpnTgnwlBbWTmhWDR1pvS9iVEzcSYLHT%2FfNnMRxFc7u%2Bj3qI%2F%2F5yuGuu14KR0MuQKKCSpViieD%2BfIti46sxPTsjSemoUKp0oXA%3D%3D'
2.5 - curl command
Bash script
#!/usr/bin/env bash
# Set up authentication:
API_KEY="put your own API Key here"
PRIVATE_KEY_PATH="test-prv-key.pem"
# Set up the request:
API_METHOD="POST"
API_CALL="api/v3/order"
API_PARAMS="symbol=BTCUSDT&side=SELL&type=LIMIT&timeInForce=GTC&quantity=1&price=0.2"
# Sign the request:
timestamp=$(date +%s000)
api_params_with_timestamp="$API_PARAMS×tamp=$timestamp"
signature=$(echo -n "$api_params_with_timestamp" \
| openssl dgst -sha256 -sign "$PRIVATE_KEY_PATH" \
| openssl enc -base64 -A)
# Send the request:
curl -H "X-MBX-APIKEY: $API_KEY" -X "$API_METHOD" \
"https://api.binance.com/$API_CALL?$api_params_with_timestamp" \
--data-urlencode "signature=$signature"
A sample Bash script containing similar steps is available in the right side.
SIGNED Endpoint Examples for POST /api/v3/order - Ed25519 Keys
Parameter | Value |
---|---|
symbol | BTCUSDT |
side | SELL |
type | LIMIT |
timeInForce | GTC |
quantity | 1 |
price | 0.2 |
timestamp | 1668481559918 |
Python script
#!/usr/bin/env python3
import base64
import requests
import time
from cryptography.hazmat.primitives.serialization import load_pem_private_key
# Set up authentication
API_KEY='put your own API Key here'
PRIVATE_KEY_PATH='test-prv-key.pem'
# Load the private key.
# In this example the key is expected to be stored without encryption,
# but we recommend using a strong password for improved security.
with open(PRIVATE_KEY_PATH, 'rb') as f:
private_key = load_pem_private_key(data=f.read(),
password=None)
# Set up the request parameters
params = {
'symbol': 'BTCUSDT',
'side': 'SELL',
'type': 'LIMIT',
'timeInForce': 'GTC',
'quantity': '1.0000000',
'price': '0.20',
}
# Timestamp the request
timestamp = int(time.time() * 1000) # UNIX timestamp in milliseconds
params['timestamp'] = timestamp
# Sign the request
payload = '&'.join([f'{param}={value}' for param, value in params.items()])
signature = base64.b64encode(private_key.sign(payload.encode('ASCII')))
params['signature'] = signature
# Send the request
headers = {
'X-MBX-APIKEY': API_KEY,
}
response = requests.post(
'https://api.binance.com/api/v3/order',
headers=headers,
data=params,
)
print(response.json())
A sample code in Python to show how to sign the payload with an Ed25519 key is available on the right side.
Public API Definitions
Terminology
These terms will be used throughout the documentation, so it is recommended especially for new users to read to help their understanding of the API.
base asset
refers to the asset that is thequantity
of a symbol. For the symbol BTCUSDT, BTC would be thebase asset.
quote asset
refers to the asset that is theprice
of a symbol. For the symbol BTCUSDT, USDT would be thequote asset
.
ENUM definitions
Symbol status (status):
PRE_TRADING
TRADING
POST_TRADING
END_OF_DAY
HALT
AUCTION_MATCH
BREAK
Account and Symbol Permissions (permissions):
SPOT
MARGIN
TRD_GRP_002
TRD_GRP_003
TRD_GRP_004
TRD_GRP_005
TRD_GRP_006
TRD_GRP_007
TRD_GRP_008
TRD_GRP_009
TRD_GRP_010
TRD_GRP_011
TRD_GRP_012
TRD_GRP_013
TRD_GRP_014
TRD_GRP_015
TRD_GRP_016
TRD_GRP_017
TRD_GRP_018
TRD_GRP_019
TRD_GRP_020
TRD_GRP_021
TRD_GRP_022
TRD_GRP_023
TRD_GRP_024
TRD_GRP_025
Order status (status):
Status | Description |
---|---|
NEW |
The order has been accepted by the engine. |
PARTIALLY_FILLED |
A part of the order has been filled. |
FILLED |
The order has been completed. |
CANCELED |
The order has been canceled by the user. |
PENDING_CANCEL |
Currently unused |
REJECTED |
The order was not accepted by the engine and not processed. |
EXPIRED |
The order was canceled according to the order type's rules (e.g. LIMIT FOK orders with no fill, LIMIT IOC or MARKET orders that partially fill) or by the exchange, (e.g. orders canceled during liquidation, orders canceled during maintenance) |
EXPIRED_IN_MATCH |
The order was canceled by the exchange due to STP trigger. (e.g. an order with EXPIRE_TAKER will match with existing orders on the book with the same account or same tradeGroupId ) |
Order list Status (listStatusType):
Status | Description |
---|---|
RESPONSE |
This is used when the ListStatus is responding to a failed action. (E.g. order list placement or cancellation) |
EXEC_STARTED |
The order list has been placed or there is an update to the order list status. |
ALL_DONE |
The order list has finished executing and thus no longer active. |
Order list Order Status (listOrderStatus):
Status | Description |
---|---|
EXECUTING |
Either an order list has been placed or there is an update to the status of the list. |
ALL_DONE |
An order list has completed execution and thus no longer active. |
REJECT |
The List Status is responding to a failed action either during order placement or order canceled.) |
ContingencyType
OCO
OTO
AllocationType
SOR
WorkingFloor
EXCHANGE
SOR
Order types (orderTypes, type):
LIMIT
MARKET
STOP_LOSS
STOP_LOSS_LIMIT
TAKE_PROFIT
TAKE_PROFIT_LIMIT
LIMIT_MAKER
Order Response Type (newOrderRespType):
ACK
RESULT
FULL
Order side (side):
BUY
SELL
Time in force (timeInForce):
This sets how long an order will be active before expiration.
Status | Description |
---|---|
GTC |
Good Til Canceled An order will be on the book unless the order is canceled. |
IOC |
Immediate Or Cancel An order will try to fill the order as much as it can before the order expires. |
FOK |
Fill or Kill An order will expire if the full order cannot be filled upon execution. |
Kline/Candlestick chart intervals:
s-> seconds; m -> minutes; h -> hours; d -> days; w -> weeks; M -> months
- 1s
- 1m
- 3m
- 5m
- 15m
- 30m
- 1h
- 2h
- 4h
- 6h
- 8h
- 12h
- 1d
- 3d
- 1w
- 1M
Rate limiters (rateLimitType)
REQUEST_WEIGHT
{
"rateLimitType": "REQUEST_WEIGHT",
"interval": "MINUTE",
"intervalNum": 1,
"limit": 6000
}
ORDERS
{
"rateLimitType": "ORDERS",
"interval": "SECOND",
"intervalNum": 10,
"limit": 100
},
{
"rateLimitType": "ORDERS",
"interval": "DAY",
"intervalNum": 1,
"limit": 200000
}
RAW_REQUESTS
{
"rateLimitType": "RAW_REQUESTS",
"interval": "MINUTE",
"intervalNum": 5,
"limit": 5000
}
REQUEST_WEIGHT
ORDERS
RAW_REQUESTS
Rate limit intervals (interval)
- SECOND
- MINUTE
- DAY
STP Modes
NONE
EXPIRE_MAKER
EXPIRE_TAKER
EXPIRE_BOTH
Filters
Filters define trading rules on a symbol or an exchange.
Filters come in two forms: symbol filters
and exchange filters
.
Symbol Filters
PRICE_FILTER
ExchangeInfo format:
{
"filterType": "PRICE_FILTER",
"minPrice": "0.00000100",
"maxPrice": "100000.00000000",
"tickSize": "0.00000100"
}
The PRICE_FILTER
defines the price
rules for a symbol. There are 3 parts:
minPrice
defines the minimumprice
/stopPrice
allowed; disabled onminPrice
== 0.maxPrice
defines the maximumprice
/stopPrice
allowed; disabled onmaxPrice
== 0.tickSize
defines the intervals that aprice
/stopPrice
can be increased/decreased by; disabled ontickSize
== 0.
Any of the above variables can be set to 0, which disables that rule in the price filter
. In order to pass the price filter
, the following must be true for price
/stopPrice
of the enabled rules:
price
>=minPrice
price
<=maxPrice
price
%tickSize
== 0
PERCENT_PRICE
ExchangeInfo format:
{
"filterType": "PERCENT_PRICE",
"multiplierUp": "1.3000",
"multiplierDown": "0.7000",
"avgPriceMins": 5
}
The PERCENT_PRICE
filter defines the valid range for the price based on the average of the previous trades.
avgPriceMins
is the number of minutes the average price is calculated over. 0 means the last price is used.
In order to pass the percent price
, the following must be true for price
:
price
<=weightedAveragePrice
*multiplierUp
price
>=weightedAveragePrice
*multiplierDown
PERCENT_PRICE_BY_SIDE
ExchangeInfo format:
{
"filterType": "PERCENT_PRICE_BY_SIDE",
"bidMultiplierUp": "1.2",
"bidMultiplierDown": "0.2",
"askMultiplierUp": "5",
"askMultiplierDown": "0.8",
"avgPriceMins": 1
}
The PERCENT_PRICE_BY_SIDE
filter defines the valid range for the price based on the average of the previous trades.
avgPriceMins
is the number of minutes the average price is calculated over. 0 means the last price is used.
There is a different range depending on whether the order is placed on the BUY
side or the SELL
side.
Buy orders will succeed on this filter if:
Order price
<=weightedAveragePrice
*bidMultiplierUp
Order price
>=weightedAveragePrice
*bidMultiplierDown
Sell orders will succeed on this filter if:
Order Price
<=weightedAveragePrice
*askMultiplierUp
Order Price
>=weightedAveragePrice
*askMultiplierDown
LOT_SIZE
ExchangeInfo format:
{
"filterType": "LOT_SIZE",
"minQty": "0.00100000",
"maxQty": "100000.00000000",
"stepSize": "0.00100000"
}
The LOT_SIZE
filter defines the quantity
(aka "lots" in auction terms) rules for a symbol. There are 3 parts:
minQty
defines the minimumquantity
/icebergQty
allowed.maxQty
defines the maximumquantity
/icebergQty
allowed.stepSize
defines the intervals that aquantity
/icebergQty
can be increased/decreased by.
In order to pass the lot size
, the following must be true for quantity
/icebergQty
:
quantity
>=minQty
quantity
<=maxQty
quantity
%stepSize
== 0
MIN_NOTIONAL
ExchangeInfo format:
{
"filterType": "MIN_NOTIONAL",
"minNotional": "0.00100000",
"applyToMarket": true,
"avgPriceMins": 5
}
The MIN_NOTIONAL
filter defines the minimum notional value allowed for an order on a symbol.
An order's notional value is the price
* quantity
.
If the order is an Algo order (e.g. STOP_LOSS_LIMIT
), then the notional value of the stopPrice
* quantity
will also be evaluated.
If the order is an Iceberg Order, then the notional value of the price
* icebergQty
will also be evaluated.
applyToMarket
determines whether or not the MIN_NOTIONAL
filter will also be applied to MARKET
orders.
Since MARKET
orders have no price, the average price is used over the last avgPriceMins
minutes.
avgPriceMins
is the number of minutes the average price is calculated over. 0 means the last price is used.
NOTIONAL
ExchangeInfo format:
{
"filterType": "NOTIONAL",
"minNotional": "10.00000000",
"applyMinToMarket": false,
"maxNotional": "10000.00000000",
"applyMaxToMarket": false,
"avgPriceMins": 5
}
The NOTIONAL
filter defines the acceptable notional range allowed for an order on a symbol.
applyMinToMarket
determines whether the minNotional
will be applied to MARKET
orders.
applyMaxToMarket
determines whether the maxNotional
will be applied to MARKET
orders.
In order to pass this filter, the notional (price * quantity
) has to pass the following conditions:
price * quantity
<=maxNotional
price * quantity
>=minNotional
For MARKET
orders, the average price used over the last avgPriceMins
minutes will be used for calculation.
If the avgPriceMins
is 0, then the last price will be used.
ICEBERG_PARTS
ExchangeInfo format:
{
"filterType": "ICEBERG_PARTS",
"limit": 10
}
The ICEBERG_PARTS
filter defines the maximum parts an iceberg order can have. The number of ICEBERG_PARTS
is defined as CEIL(qty / icebergQty)
.
MARKET_LOT_SIZE
ExchangeInfo format:
{
"filterType": "MARKET_LOT_SIZE",
"minQty": "0.00100000",
"maxQty": "100000.00000000",
"stepSize": "0.00100000"
}
The MARKET_LOT_SIZE
filter defines the quantity
(aka "lots" in auction terms) rules for MARKET
orders on a symbol. There are 3 parts:
minQty
defines the minimumquantity
allowed.maxQty
defines the maximumquantity
allowed.stepSize
defines the intervals that aquantity
can be increased/decreased by.
In order to pass the market lot size
, the following must be true for quantity
:
quantity
>=minQty
quantity
<=maxQty
quantity
%stepSize
== 0
MAX_NUM_ORDERS
ExchangeInfo format:
{
"filterType": "MAX_NUM_ORDERS",
"maxNumOrders": 25
}
The MAX_NUM_ORDERS
filter defines the maximum number of orders an account is allowed to have open on a symbol.
Note that both "algo" orders and normal orders are counted for this filter.
MAX_NUM_ALGO_ORDERS
ExchangeInfo format:
{
"filterType": "MAX_NUM_ALGO_ORDERS",
"maxNumAlgoOrders": 5
}
The MAX_NUM_ALGO_ORDERS
filter defines the maximum number of "algo" orders an account is allowed to have open on a symbol.
"Algo" orders are STOP_LOSS
, STOP_LOSS_LIMIT
, TAKE_PROFIT
, and TAKE_PROFIT_LIMIT
orders.
MAX_NUM_ICEBERG_ORDERS
The MAX_NUM_ICEBERG_ORDERS
filter defines the maximum number of ICEBERG
orders an account is allowed to have open on a symbol.
An ICEBERG
order is any order where the icebergQty
is > 0.
ExchangeInfo format:
{
"filterType": "MAX_NUM_ICEBERG_ORDERS",
"maxNumIcebergOrders": 5
}
MAX_POSITION
The MAX_POSITION
filter defines the allowed maximum position an account can have on the base asset of a symbol.
An account's position defined as the sum of the account's:
- free balance of the base asset
- locked balance of the base asset
- sum of the qty of all open BUY orders
BUY
orders will be rejected if the account's position is greater than the maximum position allowed.
If an order's quantity
can cause the position to overflow, this will also fail the MAX_POSITION
filter.
ExchangeInfo format:
{
"filterType":"MAX_POSITION",
"maxPosition":"10.00000000"
}
TRAILING_DELTA
ExchangeInfo format:
{
"filterType": "TRAILING_DELTA",
"minTrailingAboveDelta": 10,
"maxTrailingAboveDelta": 2000,
"minTrailingBelowDelta": 10,
"maxTrailingBelowDelta": 2000
}
The TRAILING_DELTA
filter defines the minimum and maximum value for the parameter trailingDelta
.
In order for a trailing stop order to pass this filter, the following must be true:
For STOP_LOSS BUY
, STOP_LOSS_LIMIT_BUY
,TAKE_PROFIT SELL
and TAKE_PROFIT_LIMIT SELL
orders:
trailingDelta
>=minTrailingAboveDelta
trailingDelta
<=maxTrailingAboveDelta
For STOP_LOSS SELL
, STOP_LOSS_LIMIT SELL
, TAKE_PROFIT BUY
, and TAKE_PROFIT_LIMIT BUY
orders:
trailingDelta
>=minTrailingBelowDelta
trailingDelta
<=maxTrailingBelowDelta
Exchange Filters
EXCHANGE_MAX_NUM_ORDERS
ExchangeInfo format:
{
"filterType": "EXCHANGE_MAX_NUM_ORDERS",
"maxNumOrders": 1000
}
The EXCHANGE_MAX_NUM_ORDERS
filter defines the maximum number of orders an account is allowed to have open on the exchange.
Note that both "algo" orders and normal orders are counted for this filter.
EXCHANGE_MAX_NUM_ALGO_ORDERS
ExchangeInfo format:
{
"filterType": "EXCHANGE_MAX_NUM_ALGO_ORDERS",
"maxNumAlgoOrders": 200
}
The EXCHANGE_MAX_NUM_ALGO_ORDERS
filter defines the maximum number of "algo" orders an account is allowed to have open on the exchange.
"Algo" orders are STOP_LOSS
, STOP_LOSS_LIMIT
, TAKE_PROFIT
, and TAKE_PROFIT_LIMIT
orders.
EXCHANGE_MAX_NUM_ICEBERG_ORDERS
The EXCHANGE_MAX_NUM_ICEBERG_ORDERS
filter defines the maximum number of iceberg orders an account is allowed to have open on the exchange.
ExchangeInfo format:
{
"filterType": "EXCHANGE_MAX_NUM_ICEBERG_ORDERS",
"maxNumIcebergOrders": 10000
}
Wallet Endpoints
System Status (System)
Response
{
"status": 0, // 0: normal,1:system maintenance
"msg": "normal" // "normal", "system_maintenance"
}
GET /sapi/v1/system/status
Fetch system status.
Weight(IP): 1
All Coins' Information (USER_DATA)
Get information of coins (available for deposit and withdraw) for user.
Response:
[
{
"coin": "BTC",
"depositAllEnable": true,
"free": "0.08074558",
"freeze": "0.00000000",
"ipoable": "0.00000000",
"ipoing": "0.00000000",
"isLegalMoney": false,
"locked": "0.00000000",
"name": "Bitcoin",
"networkList": [
{
"addressRegex": "^(bnb1)[0-9a-z]{38}$",
"coin": "BTC",
"depositDesc": "Wallet Maintenance, Deposit Suspended", // shown only when "depositEnable" is false.
"depositEnable": false,
"isDefault": false,
"memoRegex": "^[0-9A-Za-z\\-_]{1,120}$",
"minConfirm": 1, // min number for balance confirmation
"name": "BEP2",
"network": "BNB",
"specialTips": "Both a MEMO and an Address are required to successfully deposit your BEP2-BTCB tokens to Binance.",
"unLockConfirm": 0, // confirmation number for balance unlock
"withdrawDesc": "Wallet Maintenance, Withdrawal Suspended", // shown only when "withdrawEnable" is false.
"withdrawEnable": false,
"withdrawFee": "0.00000220",
"withdrawIntegerMultiple": "0.00000001",
"withdrawMax": "9999999999.99999999",
"withdrawMin": "0.00000440",
"sameAddress": true, // If the coin needs to provide memo to withdraw
"estimatedArrivalTime": 25,
"busy": false,
"contractAddressUrl": "https://bscscan.com/token/",
"contractAddress": "0x7130d2a12b9bcbfae4f2634d864a1ee1ce3ead9c"
},
{
"addressRegex": "^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$|^(bc1)[0-9A-Za-z]{39,59}$",
"coin": "BTC",
"depositEnable": true,
"isDefault": true,
"memoRegex": "",
"minConfirm": 1,
"name": "BTC",
"network": "BTC",
"specialTips": "",
"unLockConfirm": 2,
"withdrawEnable": true,
"withdrawFee": "0.00050000",
"withdrawIntegerMultiple": "0.00000001",
"withdrawMax": "750",
"withdrawMin": "0.00100000",
"sameAddress": false,
"estimatedArrivalTime": 25,
"busy": false,
"contractAddressUrl": "",
"contractAddress": ""
}
],
"storage": "0.00000000",
"trading": true,
"withdrawAllEnable": true,
"withdrawing": "0.00000000"
}
]
GET /sapi/v1/capital/config/getall
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Daily Account Snapshot (USER_DATA)
Response:
{
"code":200, // 200 for success; others are error codes
"msg":"", // error message
"snapshotVos":[
{
"data":{
"balances":[
{
"asset":"BTC",
"free":"0.09905021",
"locked":"0.00000000"
},
{
"asset":"USDT",
"free":"1.89109409",
"locked":"0.00000000"
}
],
"totalAssetOfBtc":"0.09942700"
},
"type":"spot",
"updateTime":1576281599000
}
]
}
OR
{
"code":200, // 200 for success; others are error codes
"msg":"", // error message
"snapshotVos":[
{
"data":{
"marginLevel":"2748.02909813",
"totalAssetOfBtc":"0.00274803",
"totalLiabilityOfBtc":"0.00000100",
"totalNetAssetOfBtc":"0.00274750",
"userAssets":[
{
"asset":"XRP",
"borrowed":"0.00000000",
"free":"1.00000000",
"interest":"0.00000000",
"locked":"0.00000000",
"netAsset":"1.00000000"
}
]
},
"type":"margin",
"updateTime":1576281599000
}
]
}
OR
{
"code":200, // 200 for success; others are error codes
"msg":"", // error message
"snapshotVos":[
{
"data":{
"assets":[
{
"asset":"USDT",
"marginBalance":"118.99782335", // Not real-time data, can ignore
"walletBalance":"120.23811389"
}
],
"position":[
{
"entryPrice":"7130.41000000",
"markPrice":"7257.66239673",
"positionAmt":"0.01000000",
"symbol":"BTCUSDT",
"unRealizedProfit":"1.24029054" // Only show the value at the time of opening the position
}
]
},
"type":"futures",
"updateTime":1576281599000
}
]
}
GET /sapi/v1/accountSnapshot
Weight(IP): 2400
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
type | STRING | YES | "SPOT", "MARGIN", "FUTURES" |
startTime | LONG | NO | |
endTime | LONG | NO | |
limit | INT | NO | min 7, max 30, default 7 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- The query time period must be less then 30 days
- Support query within the last one month only
- If startTimeand endTime not sent, return records of the last 7 days by default
Disable Fast Withdraw Switch (USER_DATA)
Response:
{}
POST /sapi/v1/account/disableFastWithdrawSwitch
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Caution:
This request will disable fastwithdraw switch under your account.
You need to enable "trade" option for the api key which requests this endpoint.
Enable Fast Withdraw Switch (USER_DATA)
Response:
{}
POST /sapi/v1/account/enableFastWithdrawSwitch
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- This request will enable fastwithdraw switch under your account.
You need to enable "trade" option for the api key which requests this endpoint. - When Fast Withdraw Switch is on, transferring funds to a Binance account will be done instantly. There is no on-chain transaction, no transaction ID and no withdrawal fee.
Withdraw(USER_DATA)
Response:
{
"id":"7213fea8e94b4a5593d507237e5a555b"
}
POST /sapi/v1/capital/withdraw/apply
Submit a withdraw request.
Weight(UID): 600
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
coin | STRING | YES | |
withdrawOrderId | STRING | NO | client id for withdraw |
network | STRING | NO | |
address | STRING | YES | |
addressTag | STRING | NO | Secondary address identifier for coins like XRP,XMR etc. |
amount | DECIMAL | YES | |
transactionFeeFlag | BOOLEAN | NO | 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 . |
name | STRING | NO | Description of the address. The upper limit of the address book is 200. Exceeding the limit will cause withdrawal failure. Space in name should be encoded into %20 . |
walletType | INTEGER | NO | 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 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- If
network
not send, return with default network of the coin. - You can get
network
andisDefault
innetworkList
of a coin in the response ofGet /sapi/v1/capital/config/getall
.
Deposit History (supporting network) (USER_DATA)
Response:
[
{
"id": "769800519366885376",
"amount": "0.001",
"coin": "BNB",
"network": "BNB",
"status": 0,
"address": "bnb136ns6lfw4zs5hg4n85vdthaad7hq5m4gtkgf23",
"addressTag": "101764890",
"txId": "98A3EA560C6B3336D348B6C83F0F95ECE4F1F5919E94BD006E5BF3BF264FACFC",
"insertTime": 1661493146000,
"transferType": 0,
"confirmTimes": "1/1",
"unlockConfirm": 0,
"walletType": 0
},
{
"id": "769754833590042625",
"amount":"0.50000000",
"coin":"IOTA",
"network":"IOTA",
"status":1,
"address":"SIZ9VLMHWATXKV99LH99CIGFJFUMLEHGWVZVNNZXRJJVWBPHYWPPBOSDORZ9EQSHCZAMPVAPGFYQAUUV9DROOXJLNW",
"addressTag":"",
"txId":"ESBFVQUTPIWQNJSPXFNHNYHSQNTGKRVKPRABQWTAXCDWOAKDKYWPTVG9BGXNVNKTLEJGESAVXIKIZ9999",
"insertTime":1599620082000,
"transferType":0,
"confirmTimes": "1/1",
"unlockConfirm": 0,
"walletType": 0
}
]
GET /sapi/v1/capital/deposit/hisrec
Fetch deposit history.
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
includeSource | Boolean | NO | default false , if true source address for the transaction will be returned |
coin | STRING | NO | |
status | INT | NO | 0(0:pending,6: credited but cannot withdraw, 7=Wrong Deposit,8=Waiting User confirm, 1:success) |
startTime | LONG | NO | Default: 90 days from current timestamp |
endTime | LONG | NO | Default: present timestamp |
offset | INT | NO | Default:0 |
limit | INT | NO | Default:1000, Max:1000 |
recvWindow | LONG | NO | |
timestamp | LONG | YES | |
txId | STRING | NO |
- Please notice the default
startTime
andendTime
to make sure that time interval is within 0-90 days. - If both
startTime
andendTime
are sent, time betweenstartTime
andendTime
must be less than 90 days. - Please note that the source address returned may not be accurate due to network-specific characteristics. If multiple source addresses found, only the first address will be returned
Withdraw History (supporting network) (USER_DATA)
Response:
[
{
"id": "b6ae22b3aa844210a7041aee7589627c", // Withdrawal id in Binance
"amount": "8.91000000", // withdrawal amount
"transactionFee": "0.004", // transaction fee
"coin": "USDT",
"status": 6,
"address": "0x94df8b352de7f46f64b01d3666bf6e936e44ce60",
"txId": "0xb5ef8c13b968a406cc62a93a8bd80f9e9a906ef1b3fcf20a2e48573c17659268" // withdrawal transaction id
"applyTime": "2019-10-12 11:12:02", // UTC time
"network": "ETH",
"transferType": 0 // 1 for internal transfer, 0 for external transfer
"withdrawOrderId": "WITHDRAWtest123", // // will not be returned if there's no withdrawOrderId for this withdraw.
"info": "The address is not valid. Please confirm with the recipient", // reason for withdrawal failure
"confirmNo":3, // confirm times for withdraw
"walletType": 1, //1: Funding Wallet 0:Spot Wallet
"txKey": "",
"completeTime": "2023-03-23 16:52:41" // complete UTC time when user's asset is deduct from withdrawing, only if status = 6(success)
},
{
"id": "156ec387f49b41df8724fa744fa82719",
"amount": "0.00150000",
"transactionFee": "0.004",
"coin": "BTC",
"status": 6,
"address": "1FZdVHtiBqMrWdjPyRPULCUceZPJ2WLCsB",
"txId": "60fd9007ebfddc753455f95fafa808c4302c836e4d1eebc5a132c36c1d8ac354"
"applyTime": "2019-09-24 12:43:45",
"network": "BTC",
"transferType": 0,
"info": "",
"confirmNo": 2,
"walletType": 1,
"txKey": "",
"completeTime": "2023-03-23 16:52:41"
}
]
GET /sapi/v1/capital/withdraw/history
Fetch withdraw history.
Weight(UID): 18000
Request Limit: 10 requests per second
- This endpoint specifically uses per second UID rate limit, user's total second level UID rate limit is 180000/second. Response from the endpoint contains header key X-SAPI-USED-UID-WEIGHT-1S, which defines weight used by the current UID.
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
coin | STRING | NO | |
withdrawOrderId | STRING | NO | |
status | INT | NO | 0(0:Email Sent,1:Cancelled 2:Awaiting Approval 3:Rejected 4:Processing 5:Failure 6:Completed) |
offset | INT | NO | |
limit | INT | NO | Default: 1000, Max: 1000 |
startTime | LONG | NO | Default: 90 days from current timestamp |
endTime | LONG | NO | Default: present timestamp |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
network
may not be in the response for old withdraw.- Please notice the default
startTime
andendTime
to make sure that time interval is within 0-90 days. - If both
startTime
andendTime
are sent, time betweenstartTime
andendTime
must be less than 90 days. - If
withdrawOrderId
is sent, time betweenstartTime
andendTime
must be less than 7 days. - If
withdrawOrderId
is sent,startTime
andendTime
are not sent, will return last 7 days records by default.
Deposit Address (supporting network) (USER_DATA)
Response:
{
"address": "1HPn8Rx2y6nNSfagQBKy27GB99Vbzg89wv",
"coin": "BTC",
"tag": "",
"url": "https://btc.com/1HPn8Rx2y6nNSfagQBKy27GB99Vbzg89wv"
}
GET /sapi/v1/capital/deposit/address
Fetch deposit address with network.
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
coin | STRING | YES | |
network | STRING | NO | |
amount | DECIMAL | NO | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- If
network
is not send, return with default network of the coin. - You can get
network
andisDefault
innetworkList
in the response ofGet /sapi/v1/capital/config/getall (HMAC SHA256)
. amount
needs to be sent if using LIGHTNING network
Account Status (USER_DATA)
Response:
{
"data": "Normal"
}
GET /sapi/v1/account/status
Fetch account status detail.
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Account API Trading Status (USER_DATA)
Response:
{
"data": { // API trading status detail
"isLocked": false, // API trading function is locked or not
"plannedRecoverTime": 0, // If API trading function is locked, this is the planned recover time
"triggerCondition": {
"GCR": 150, // Number of GTC orders
"IFER": 150, // Number of FOK/IOC orders
"UFR": 300 // Number of orders
},
"updateTime": 1547630471725
}
}
GET /sapi/v1/account/apiTradingStatus
Fetch account api trading status detail.
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
DustLog(USER_DATA)
Response
{
"total": 8, //Total counts of exchange
"userAssetDribblets": [
{
"operateTime": 1615985535000,
"totalTransferedAmount": "0.00132256", // Total transfered BNB amount for this exchange.
"totalServiceChargeAmount": "0.00002699", //Total service charge amount for this exchange.
"transId": 45178372831,
"userAssetDribbletDetails": [ //Details of this exchange.
{
"transId": 4359321,
"serviceChargeAmount": "0.000009",
"amount": "0.0009",
"operateTime": 1615985535000,
"transferedAmount": "0.000441",
"fromAsset": "USDT"
},
{
"transId": 4359321,
"serviceChargeAmount": "0.00001799",
"amount": "0.0009",
"operateTime": 1615985535000,
"transferedAmount": "0.00088156",
"fromAsset": "ETH"
}
]
},
{
"operateTime":1616203180000,
"totalTransferedAmount": "0.00058795",
"totalServiceChargeAmount": "0.000012",
"transId": 4357015,
"userAssetDribbletDetails": [
{
"transId": 4357015,
"serviceChargeAmount": "0.00001",
"amount": "0.001",
"operateTime": 1616203180000,
"transferedAmount": "0.00049",
"fromAsset": "USDT"
},
{
"transId": 4357015,
"serviceChargeAmount": "0.000002",
"amount": "0.0001",
"operateTime": 1616203180000,
"transferedAmount": "0.00009795",
"fromAsset": "ETH"
}
]
}
]
}
}
GET /sapi/v1/asset/dribblet
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
accountType | STRING | NO | SPOT or MARGIN ,default SPOT |
startTime | LONG | NO | |
endTime | LONG | NO | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- Only return last 100 records
- Only return records after 2020/12/01
Get Assets That Can Be Converted Into BNB (USER_DATA)
Response
{
"details": [
{
"asset": "ADA",
"assetFullName": "ADA",
"amountFree": "6.21", //Convertible amount
"toBTC": "0.00016848", //BTC amount
"toBNB": "0.01777302", //BNB amount(Not deducted commission fee)
"toBNBOffExchange": "0.01741756", //BNB amount(Deducted commission fee)
"exchange": "0.00035546" //Commission fee
}
],
"totalTransferBtc": "0.00016848",
"totalTransferBNB": "0.01777302",
"dribbletPercentage": "0.02" //Commission fee
}
POST /sapi/v1/asset/dust-btc
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
accountType | STRING | NO | SPOT or MARGIN ,default SPOT |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Dust Transfer (USER_DATA)
Response:
{
"totalServiceCharge":"0.02102542",
"totalTransfered":"1.05127099",
"transferResult":[
{
"amount":"0.03000000",
"fromAsset":"ETH",
"operateTime":1563368549307,
"serviceChargeAmount":"0.00500000",
"tranId":2970932918,
"transferedAmount":"0.25000000"
},
{
"amount":"0.09000000",
"fromAsset":"LTC",
"operateTime":1563368549404,
"serviceChargeAmount":"0.01548000",
"tranId":2970932918,
"transferedAmount":"0.77400000"
},
{
"amount":"248.61878453",
"fromAsset":"TRX",
"operateTime":1563368549489,
"serviceChargeAmount":"0.00054542",
"tranId":2970932918,
"transferedAmount":"0.02727099"
}
]
}
POST /sapi/v1/asset/dust
Convert dust assets to BNB.
Weight(UID): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | ARRAY | YES | The asset being converted. For example: asset=BTC,USDT |
accountType | STRING | NO | SPOT or MARGIN ,default SPOT |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to open
Enable Spot & Margin Trading
permission for the API Key which requests this endpoint.
Asset Dividend Record (USER_DATA)
Response:
{
"rows":[
{
"id":1637366104,
"amount":"10.00000000",
"asset":"BHFT",
"divTime":1563189166000,
"enInfo":"BHFT distribution",
"tranId":2968885920
},
{
"id":1631750237,
"amount":"10.00000000",
"asset":"BHFT",
"divTime":1563189165000,
"enInfo":"BHFT distribution",
"tranId":2968885920
}
],
"total":2
}
GET /sapi/v1/asset/assetDividend
Query asset dividend record.
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | NO | |
startTime | LONG | NO | |
endTime | LONG | NO | |
limit | INT | NO | Default 20, max 500 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- There cannot be more than 180 days between parameter
startTime
andendTime
.
Asset Detail (USER_DATA)
Response:
{
"CTR": {
"minWithdrawAmount": "70.00000000", //min withdraw amount
"depositStatus": false,//deposit status (false if ALL of networks' are false)
"withdrawFee": 35, // withdraw fee
"withdrawStatus": true, //withdraw status (false if ALL of networks' are false)
"depositTip": "Delisted, Deposit Suspended" //reason
},
"SKY": {
"minWithdrawAmount": "0.02000000",
"depositStatus": true,
"withdrawFee": 0.01,
"withdrawStatus": true
}
}
GET /sapi/v1/asset/assetDetail
Fetch details of assets supported on Binance.
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | NO | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- Please get network and other deposit or withdraw details from
GET /sapi/v1/capital/config/getall
.
Trade Fee (USER_DATA)
Response:
[
{
"symbol": "ADABNB",
"makerCommission": "0.001",
"takerCommission": "0.001"
},
{
"symbol": "BNBBTC",
"makerCommission": "0.001",
"takerCommission": "0.001"
}
]
GET /sapi/v1/asset/tradeFee
Fetch trade fee
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | NO | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
User Universal Transfer (USER_DATA)
Response:
{
"tranId":13526853623
}
POST /sapi/v1/asset/transfer
You need to enable Permits Universal Transfer
option for the API Key which requests this endpoint.
Weight(UID): 900
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
type | ENUM | YES | |
asset | STRING | YES | |
amount | DECIMAL | YES | |
fromSymbol | STRING | NO | |
toSymbol | STRING | NO | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
-
fromSymbol
must be sent when type are ISOLATEDMARGIN_MARGIN and ISOLATEDMARGIN_ISOLATEDMARGIN toSymbol
must be sent when type are MARGIN_ISOLATEDMARGIN and ISOLATEDMARGIN_ISOLATEDMARGINENUM of transfer types:
- MAIN_UMFUTURE Spot account transfer to USDⓈ-M Futures account
- MAIN_CMFUTURE Spot account transfer to COIN-M Futures account
- MAIN_MARGIN Spot account transfer to Margin(cross)account
- UMFUTURE_MAIN USDⓈ-M Futures account transfer to Spot account
- UMFUTURE_MARGIN USDⓈ-M Futures account transfer to Margin(cross)account
- CMFUTURE_MAIN COIN-M Futures account transfer to Spot account
- CMFUTURE_MARGIN COIN-M Futures account transfer to Margin(cross) account
- MARGIN_MAIN Margin(cross)account transfer to Spot account
- MARGIN_UMFUTURE Margin(cross)account transfer to USDⓈ-M Futures
- MARGIN_CMFUTURE Margin(cross)account transfer to COIN-M Futures
- ISOLATEDMARGIN_MARGIN Isolated margin account transfer to Margin(cross) account
- MARGIN_ISOLATEDMARGIN Margin(cross) account transfer to Isolated margin account
- ISOLATEDMARGIN_ISOLATEDMARGIN Isolated margin account transfer to Isolated margin account
- MAIN_FUNDING Spot account transfer to Funding account
- FUNDING_MAIN Funding account transfer to Spot account
- FUNDING_UMFUTURE Funding account transfer to UMFUTURE account
- UMFUTURE_FUNDING UMFUTURE account transfer to Funding account
- MARGIN_FUNDING MARGIN account transfer to Funding account
- FUNDING_MARGIN Funding account transfer to Margin account
- FUNDING_CMFUTURE Funding account transfer to CMFUTURE account
- CMFUTURE_FUNDING CMFUTURE account transfer to Funding account
- MAIN_OPTION Spot account transfer to Options account
- OPTION_MAIN Options account transfer to Spot account
- UMFUTURE_OPTION USDⓈ-M Futures account transfer to Options account
- OPTION_UMFUTURE Options account transfer to USDⓈ-M Futures account
- MARGIN_OPTION Margin(cross)account transfer to Options account
- OPTION_MARGIN Options account transfer to Margin(cross)account
- FUNDING_OPTION Funding account transfer to Options account
- OPTION_FUNDING Options account transfer to Funding account
- MAIN_PORTFOLIO_MARGIN Spot account transfer to Portfolio Margin account
- PORTFOLIO_MARGIN_MAIN Portfolio Margin account transfer to Spot account
- MAIN_ISOLATED_MARGIN Spot account transfer to Isolated margin account
- ISOLATED_MARGIN_MAIN Isolated margin account transfer to Spot account
Query User Universal Transfer History (USER_DATA)
Response:
{
"total":2,
"rows":[
{
"asset":"USDT",
"amount":"1",
"type":"MAIN_UMFUTURE",
"status": "CONFIRMED", // status: CONFIRMED / FAILED / PENDING
"tranId": 11415955596,
"timestamp":1544433328000
},
{
"asset":"USDT",
"amount":"2",
"type":"MAIN_UMFUTURE",
"status": "CONFIRMED",
"tranId": 11366865406,
"timestamp":1544433328000
}
]
}
GET /sapi/v1/asset/transfer
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
type | ENUM | YES | |
startTime | LONG | NO | |
endTime | LONG | NO | |
current | INT | NO | Default 1 |
size | INT | NO | Default 10, Max 100 |
fromSymbol | STRING | NO | |
toSymbol | STRING | NO | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
-
fromSymbol
must be sent when type are ISOLATEDMARGIN_MARGIN and ISOLATEDMARGIN_ISOLATEDMARGIN -
toSymbol
must be sent when type are MARGIN_ISOLATEDMARGIN and ISOLATEDMARGIN_ISOLATEDMARGIN - Support query within the last 6 months only
- If
startTime
andendTime
not sent, return records of the last 7 days by default
Funding Wallet (USER_DATA)
Response
[
{
"asset": "USDT",
"free": "1", // avalible balance
"locked": "0", // locked asset
"freeze": "0", // freeze asset
"withdrawing": "0",
"btcValuation": "0.00000091"
}
]
POST /sapi/v1/asset/get-funding-asset
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | NO | |
needBtcValuation | STRING | NO | true or false |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- Currently supports querying the following business assets:Binance Pay, Binance Card, Binance Gift Card, Stock Token
User Asset (USER_DATA)
Response
[
{
"asset": "AVAX",
"free": "1",
"locked": "0",
"freeze": "0",
"withdrawing": "0",
"ipoable": "0",
"btcValuation": "0"
},
{
"asset": "BCH",
"free": "0.9",
"locked": "0",
"freeze": "0",
"withdrawing": "0",
"ipoable": "0",
"btcValuation": "0"
},
{
"asset": "BNB",
"free": "887.47061626",
"locked": "0",
"freeze": "10.52",
"withdrawing": "0.1",
"ipoable": "0",
"btcValuation": "0"
},
{
"asset": "BUSD",
"free": "9999.7",
"locked": "0",
"freeze": "0",
"withdrawing": "0",
"ipoable": "0",
"btcValuation": "0"
},
{
"asset": "SHIB",
"free": "532.32",
"locked": "0",
"freeze": "0",
"withdrawing": "0",
"ipoable": "0",
"btcValuation": "0"
},
{
"asset": "USDT",
"free": "50300000001.44911105",
"locked": "0",
"freeze": "0",
"withdrawing": "0",
"ipoable": "0",
"btcValuation": "0"
},
{
"asset": "WRZ",
"free": "1",
"locked": "0",
"freeze": "0",
"withdrawing": "0",
"ipoable": "0",
"btcValuation": "0"
}
]
POST /sapi/v3/asset/getUserAsset
Get user assets, just for positive data.
Weight(IP): 5
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | NO | If asset is blank, then query all positive assets user have. |
needBtcValuation | BOOLEAN | NO | Whether need btc valuation or not. |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- If asset is set, then return this asset, otherwise return all assets positive.
- If needBtcValuation is set, then return btcValudation.
BUSD Convert (TRADE)
Response
{
"tranId": 118263407119,
"status": "S"
}
POST /sapi/v1/asset/convert-transfer
Convert transfer, convert between BUSD and stablecoins.
Weight(UID): 5
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
clientTranId | STRING | YES | The unique user-defined transaction id, min length 20 |
asset | STRING | YES | The current asset |
amount | BigDecimal | YES | The amount must be positive number |
targetAsset | String | YES | Target asset you want to convert |
accountType | String | NO | Only MAIN and CARD , default MAIN |
- If the clientTranId has been used before, will not do the convert transfer, the original transfer will be returned.
BUSD Convert History (USER_DATA)
Response
{
"total":3,
"rows":
[
{
"tranId":118263615991,
"type":244,
"time":1664442078000,
"deductedAsset":"BUSD",
"deductedAmount":"1",
"targetAsset":"USDC",
"targetAmount":"1",
"status":"S",
"accountType":"MAIN"
},{
"tranId":118263598801,
"type":244,
"time":1664442061000,
"deductedAsset":"BUSD",
"deductedAmount":"1",
"targetAsset":"USDC",
"targetAmount":"1",
"status":"S",
"accountType":"MAIN"
},{
"tranId":118263407119,
"type":244,
"time":1664441820000,
"deductedAsset":"BUSD",
"deductedAmount":"1",
"targetAsset":"USDC",
"targetAmount":"1",
"status":"S",
"accountType":"MAIN"
}
]
}
GET /sapi/v1/asset/convert-transfer/queryByPage
Weight(UID): 5
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
tranId | LONG | NO | The transaction id |
clientTranId | STRING | NO | The user-defined transaction id |
asset | STRING | NO | If it is blank, we will match deducted asset and target asset. |
startTime | LONG | YES | inclusive, unit: ms |
endTime | LONG | YES | exclusive, unit: ms |
accountType | STRING | NO | MAIN: main account. CARD: funding account. If it is blank, we will query spot and card wallet, otherwise, we just query the corresponding wallet |
current | INTEGER | NO | current page, default 1, the min value is 1 |
size | INTEGER | NO | page size, default 10, the max value is 100 |
- ENUM of types:
- 244 convert via sapi call
- 11 auto convert when deposit
- 32 auto convert when withdraw
- 34 in case withdraw failed
- 254 busd auto convert job
Get Cloud-Mining payment and refund history (USER_DATA)
Response
{
"total":5,
"rows":[
{"createTime":1667880112000,"tranId":121230610120,"type":248,"asset":"USDT","amount":"25.0068","status":"S"},
{"createTime":1666776366000,"tranId":119991507468,"type":249,"asset":"USDT","amount":"0.027","status":"S"},
{"createTime":1666764505000,"tranId":119977966327,"type":248,"asset":"USDT","amount":"0.027","status":"S"},
{"createTime":1666758189000,"tranId":119973601721,"type":248,"asset":"USDT","amount":"0.018","status":"S"},
{"createTime":1666757278000,"tranId":119973028551,"type":248,"asset":"USDT","amount":"0.018","status":"S"}
]
}
GET /sapi/v1/asset/ledger-transfer/cloud-mining/queryByPage
The query of Cloud-Mining payment and refund history
Weight(UID): 600
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
tranId | LONG | NO | The transaction id |
clientTranId | STRING | NO | The unique flag |
asset | STRING | NO | If it is blank, we will query all assets |
startTime | LONG | YES | inclusive, unit: ms |
endTime | LONG | YES | exclusive, unit: ms |
current | INTEGER | NO | current page, default 1, the min value is 1 |
size | INTEGER | NO | page size, default 10, the max value is 100 |
- Just return the SUCCESS records of payment and refund.
- For response, type = 248 means payment, type = 249 means refund, status =S means SUCCESS.
Get API Key Permission (USER_DATA)
Response
{
"ipRestrict":false,
"createTime":1698645219000,
"enableInternalTransfer":false, // This option authorizes this key to transfer funds between your master account and your sub account instantly
"enableFutures":false, // The Futures API cannot be used if the API key was created before the Futures account was opened, or if you have enabled portfolio margin.
"enablePortfolioMarginTrading":true, // API Key created before your activate portfolio margin does not support portfolio margin API service
"enableVanillaOptions":false, // Authorizes this key to Vanilla options trading
"permitsUniversalTransfer":false, // Authorizes this key to be used for a dedicated universal transfer API to transfer multiple supported currencies. Each business's own transfer API rights are not affected by this authorization
"enableReading":true,
"enableSpotAndMarginTrading":false, // Spot and margin trading
"enableWithdrawals":false, // This option allows you to withdraw via API. You must apply the IP Access Restriction filter in order to enable withdrawals
"enableMargin":false // This option can be adjusted after the Cross Margin account transfer is completed
}
GET /sapi/v1/account/apiRestrictions
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Query auto-converting stable coins (USER_DATA)
Response:
{
"convertEnabled": true,
"coins": [
"USDC",
"USDP",
"TUSD"
],
"exchangeRates": {
"USDC": "1",
"TUSD": "1",
"USDP": "1"
}
}
GET /sapi/v1/capital/contract/convertible-coins
Get a user's auto-conversion settings in deposit/withdrawal
Weight(UID): 600
Parameters: None
Switch on/off BUSD and stable coins conversion (USER_DATA)
Response: Returns code 200 on success without body.
POST /sapi/v1/capital/contract/convertible-coins
User can use it to turn on or turn off the BUSD auto-conversion from/to a specific stable coin.
Weight(UID): 600
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
coin | STRING | YES | Must be USDC, USDP or TUSD |
enable | BOOLEAN | YES | true: turn on the auto-conversion. false: turn off the auto-conversion |
- Params need to be in the POST body
One click arrival deposit apply (for expired address deposit) (USER_DATA)
Response:
{
"code": "000000",
"message": "success",
"data":true,
"success": true
}
POST /sapi/v1/capital/deposit/credit-apply
Apply deposit credit for expired address (One click arrival)
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
depositId | LONG | NO | Deposit record Id, priority use |
txId | STRING | NO | Deposit txId, used when depositId is not specified |
subAccountId | LONG | NO | Sub-accountId of Cloud user |
subUserId | LONG | NO | Sub-userId of parent user |
- Params need to be in the POST body
Fetch deposit address list with network(USER_DATA)
Response:
[
{
"coin": "ETH",
"address": "0xD316E95Fd9E8E237Cb11f8200Babbc5D8D177BA4",
"tag":"",
"isDefault": 0
},
{
"coin": "ETH",
"address": "0xD316E95Fd9E8E237Cb11f8200Babbc5D8D177BA4",
"tag":"",
"isDefault": 0
},
{
"coin": "ETH",
"address": "0x00003ada75e7da97ba0db2fcde72131f712455e2",
"tag":"",
"isDefault": 1 //'isDefault' is 1 means the address is default, same as shown in the app.
}
]
GET /sapi/v1/capital/deposit/address/list
Fetch deposit address list with network.
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
coin | STRING | YES | coin refers to the parent network address format that the address is using |
network | STRING | NO | |
timestamp | LONG | YES |
- 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
.
Query User Wallet Balance (USER_DATA)
Response:
[
{
"activate": true,
"balance": "0",
"walletName": "Spot"
},
{
"activate": true,
"balance": "0",
"walletName": "Funding"
},
{
"activate": true,
"balance": "0",
"walletName": "Cross Margin"
},
{
"activate": true,
"balance": "0",
"walletName": "Isolated Margin"
},
{
"activate": true,
"balance": "0.71842752",
"walletName": "USDⓈ-M Futures"
},
{
"activate": true,
"balance": "0",
"walletName": "COIN-M Futures"
},
{
"activate": true,
"balance": "0",
"walletName": "Earn"
},
{
"activate": false,
"balance": "0",
"walletName": "Options"
}
]
GET /sapi/v1/asset/wallet/balance
Query User Wallet Balance
Weight(IP): 60
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to open Permits Universal Transfer permission for the API Key which requests this endpoint.
Query User Delegation History(For Master Account)(USER_DATA)
Response:
{
"total": 3316,
"rows": [
{
"clientTranId": "293915932290879488",
"transferType": "Undelegate",
"asset": "ETH",
"amount": "1",
"time": 1695205406000
},
{
"clientTranId": "293915892281413632",
"transferType": "Delegate",
"asset": "ETH",
"amount": "1",
"time": 1695205396000
}
]
}
GET /sapi/v1/asset/custody/transfer-history
Query User Delegation History
Weight(IP): 60
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | ||
startTime | LONG | YES | |
endTime | LONG | YES | |
type | ENUM | NO | Delegate/Undelegate |
asset | STRING | NO | |
current | INTEGER | NO | default 1 |
size | INTEGER | NO | default 10, max 100 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to open Enable Spot & Margin Trading permission for the API Key which requests this endpoint
Get symbols delist schedule for spot (MARKET_DATA)
GET /sapi/v1/spot/delist-schedule
Get symbols delist schedule for spot
Response:
[
{
"delistTime": 1686161202000,
"symbols": [
"ADAUSDT",
"BNBUSDT"
]
},
{
"delistTime": 1686222232000,
"symbols": [
"ETHUSDT"
]
}
]
Weight(IP): 100
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Fetch withdraw address list (USER_DATA)
GET /sapi/v1/capital/withdraw/address/list
Fetch withdraw address list
Response:
[
{
"address": "string",
"addressTag": "string",
"coin": "string",
"name": "string", //is a user-defined name
"network": "string",
"origin": "string", //if originType=='others', the address source manually filled in by the user
"originType": "string", //Address source type
"whiteStatus": true //Is it whitelisted
}
]
Weight(IP): 10
Account info (USER_DATA)
GET /sapi/v1/account/info
Fetch account info detail.
Response:
{
"vipLevel": 0,
"isMarginEnabled": true, // true or false for margin
"isFutureEnabled": true // true or false for futures.
}
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Sub-Account Endpoints
- The endpoints documented in this section are for Corporate Accounts.
- To become a corporate account, please refer to this document: Corporate Account Application
Create a Virtual Sub-account(For Master Account)
Response:
{
"email":"addsdd_virtual@aasaixwqnoemail.com"
}
POST /sapi/v1/sub-account/virtualSubAccount
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
subAccountString | STRING | YES | Please input a string. We will create a virtual email using that string for you to register |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- This request will generate a virtual sub account under your master account.
- You need to enable "trade" option for the API Key which requests this endpoint.
Query Sub-account List (For Master Account)
Response:
{
"subAccounts":[
{
"email":"testsub@gmail.com",
"isFreeze":false,
"createTime":1544433328000,
"isManagedSubAccount": false,
"isAssetManagementSubAccount": false
},
{
"email":"virtual@oxebmvfonoemail.com",
"isFreeze":false,
"createTime":1544433328000,
"isManagedSubAccount": false,
"isAssetManagementSubAccount": false
}
]
}
GET /sapi/v1/sub-account/list
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | NO | Sub-account email | |
isFreeze | STRING | NO | true or false |
page | INT | NO | Default value: 1 |
limit | INT | NO | Default value: 1, Max value: 200 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Query Sub-account Spot Asset Transfer History (For Master Account)
Response:
[
{
"from":"aaa@test.com",
"to":"bbb@test.com",
"asset":"BTC",
"qty":"10",
"status": "SUCCESS",
"tranId": 6489943656,
"time":1544433328000
},
{
"from":"bbb@test.com",
"to":"ccc@test.com",
"asset":"ETH",
"qty":"2",
"status": "SUCCESS",
"tranId": 6489938713,
"time":1544433328000
}
]
GET /sapi/v1/sub-account/sub/transfer/history
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
fromEmail | STRING | NO | |
toEmail | STRING | NO | |
startTime | LONG | NO | |
endTime | LONG | NO | |
page | INT | NO | Default value: 1 |
limit | INT | NO | Default value: 500 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- fromEmail and toEmail cannot be sent at the same time.
- Return fromEmail equal master account email by default.
Query Sub-account Futures Asset Transfer History (For Master Account)
Response
{
"success":true,
"futuresType": 2,
"transfers":[
{
"from":"aaa@test.com",
"to":"bbb@test.com",
"asset":"BTC",
"qty":"1",
"tranId":11897001102,
"time":1544433328000
},
{
"from":"bbb@test.com",
"to":"ccc@test.com",
"asset":"ETH",
"qty":"2",
"tranId":11631474902,
"time":1544433328000
}
]
}
GET /sapi/v1/sub-account/futures/internalTransfer
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
futuresType | LONG | YES | 1:USDT-margined Futures,2: Coin-margined Futures |
startTime | LONG | NO | Default return the history with in 100 days |
endTime | LONG | NO | Default return the history with in 100 days |
page | INT | NO | Default value: 1 |
limit | INT | NO | Default value: 50, Max value: 500 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Sub-account Futures Asset Transfer (For Master Account)
Response
{
"success":true,
"txnId":"2934662589"
}
POST /sapi/v1/sub-account/futures/internalTransfer
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
fromEmail | STRING | YES | Sender email |
toEmail | STRING | YES | Recipient email |
futuresType | LONG | YES | 1:USDT-margined Futures,2: Coin-margined Futures |
asset | STRING | YES | |
amount | DECIMAL | YES | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- Master account can transfer max 2000 times a minute
- There must be sufficient margin balance in futures wallet to execute transferring.
Query Sub-account Assets (For Master Account)
Response:
{
"balances":[
{
"asset":"ADA",
"free":10000,
"locked":0
},
{
"asset":"BNB",
"free":10003,
"locked":0
},
{
"asset":"BTC",
"free":11467.6399,
"locked":0
},
{
"asset":"ETH",
"free":10004.995,
"locked":0
},
{
"asset":"USDT",
"free":11652.14213,
"locked":0
}
]
}
GET /sapi/v3/sub-account/assets
Fetch sub-account assets
Weight(UID): 60
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub account email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Query Sub-account Spot Assets Summary (For Master Account)
Response:
{
"totalCount":2,
"masterAccountTotalAsset": "0.23231201",
"spotSubUserAssetBtcVoList":[
{
"email":"sub123@test.com",
"totalAsset":"9999.00000000"
},
{
"email":"test456@test.com",
"totalAsset":"0.00000000"
}
]
}
Get BTC valued asset summary of subaccounts.
GET /sapi/v1/sub-account/spotSummary
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | NO | Sub account email | |
page | LONG | NO | default 1 |
size | LONG | NO | default 10, max 20 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get Sub-account Deposit Address (For Master Account)
Response:
{
"address":"TDunhSa7jkTNuKrusUTU1MUHtqXoBPKETV",
"coin":"USDT",
"tag":"",
"url":"https://tronscan.org/#/address/TDunhSa7jkTNuKrusUTU1MUHtqXoBPKETV"
}
GET /sapi/v1/capital/deposit/subAddress
Fetch sub-account deposit address
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub account email | |
coin | STRING | YES | |
network | STRING | NO | |
amount | DECIMAL | NO | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
amount
needs to be sent if using LIGHTNING network
Get Sub-account Deposit History (For Master Account)
Response:
[
{
"id": "769800519366885376",
"amount": "0.001",
"coin": "BNB",
"network": "BNB",
"status": 0,
"address": "bnb136ns6lfw4zs5hg4n85vdthaad7hq5m4gtkgf23",
"addressTag": "101764890",
"txId": "98A3EA560C6B3336D348B6C83F0F95ECE4F1F5919E94BD006E5BF3BF264FACFC",
"insertTime": 1661493146000,
"transferType": 0,
"confirmTimes": "1/1",
"unlockConfirm": 0,
"walletType": 0
},
{
"id": "769754833590042625",
"amount":"0.50000000",
"coin":"IOTA",
"network":"IOTA",
"status":1,
"address":"SIZ9VLMHWATXKV99LH99CIGFJFUMLEHGWVZVNNZXRJJVWBPHYWPPBOSDORZ9EQSHCZAMPVAPGFYQAUUV9DROOXJLNW",
"addressTag":"",
"txId":"ESBFVQUTPIWQNJSPXFNHNYHSQNTGKRVKPRABQWTAXCDWOAKDKYWPTVG9BGXNVNKTLEJGESAVXIKIZ9999",
"insertTime":1599620082000,
"transferType":0,
"confirmTimes": "1/1",
"unlockConfirm": 0,
"walletType": 0
}
]
GET /sapi/v1/capital/deposit/subHisrec
Fetch sub-account deposit history
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub account email | |
coin | STRING | NO | |
status | INT | NO | 0(0:pending,6: credited but cannot withdraw,7:Wrong Deposit,8:Waiting User confirm,1:success) |
startTime | LONG | NO | |
endTime | LONG | NO | |
limit | INT | NO | |
offset | INT | NO | default:0 |
recvWindow | LONG | NO | |
timestamp | LONG | YES | |
txId | STRING | NO |
Get Sub-account's Status on Margin/Futures (For Master Account)
Response
[
{
"email":"123@test.com", // user email
"isSubUserEnabled": true, // true or false
"isUserActive": true, // true or false
"insertTime": 1570791523523, // sub account create time
"isMarginEnabled": true, // true or false for margin
"isFutureEnabled": true, // true or false for futures.
"mobile": 1570791523523 // user mobile number
}
]
GET /sapi/v1/sub-account/status
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | NO | Sub-account email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- If no email sent, all sub-accounts' information will be returned.
Enable Margin for Sub-account (For Master Account)
Response
{
"email":"123@test.com",
"isMarginEnabled": true
}
POST /sapi/v1/sub-account/margin/enable
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get Detail on Sub-account's Margin Account (For Master Account)
Response
{
"email":"123@test.com",
"marginLevel": "11.64405625",
"totalAssetOfBtc": "6.82728457",
"totalLiabilityOfBtc": "0.58633215",
"totalNetAssetOfBtc": "6.24095242",
"marginTradeCoeffVo":
{
"forceLiquidationBar": "1.10000000", // Liquidation margin ratio
"marginCallBar": "1.50000000", // Margin call margin ratio
"normalBar": "2.00000000" // Initial margin ratio
},
"marginUserAssetVoList": [
{
"asset": "BTC",
"borrowed": "0.00000000",
"free": "0.00499500",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00499500"
},
{
"asset": "BNB",
"borrowed": "201.66666672",
"free": "2346.50000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "2144.83333328"
},
{
"asset": "ETH",
"borrowed": "0.00000000",
"free": "0.00000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00000000"
},
{
"asset": "USDT",
"borrowed": "0.00000000",
"free": "0.00000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00000000"
}
]
}
GET /sapi/v1/sub-account/margin/account
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get Summary of Sub-account's Margin Account (For Master Account)
Response
{
"totalAssetOfBtc": "4.33333333",
"totalLiabilityOfBtc": "2.11111112",
"totalNetAssetOfBtc": "2.22222221",
"subAccountList":[
{
"email":"123@test.com",
"totalAssetOfBtc": "2.11111111",
"totalLiabilityOfBtc": "1.11111111",
"totalNetAssetOfBtc": "1.00000000"
},
{
"email":"345@test.com",
"totalAssetOfBtc": "2.22222222",
"totalLiabilityOfBtc": "1.00000001",
"totalNetAssetOfBtc": "1.22222221"
}
]
}
GET /sapi/v1/sub-account/margin/accountSummary
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Enable Futures for Sub-account (For Master Account)
Response
{
"email":"123@test.com",
"isFuturesEnabled": true // true or false
}
POST /sapi/v1/sub-account/futures/enable
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get Detail on Sub-account's Futures Account (For Master Account)
Response
{
"email": "abc@test.com",
"asset": "USDT",
"assets":[
{
"asset": "USDT",
"initialMargin": "0.00000000",
"maintenanceMargin": "0.00000000",
"marginBalance": "0.88308000",
"maxWithdrawAmount": "0.88308000",
"openOrderInitialMargin": "0.00000000",
"positionInitialMargin": "0.00000000",
"unrealizedProfit": "0.00000000",
"walletBalance": "0.88308000"
}
],
"canDeposit": true,
"canTrade": true,
"canWithdraw": true,
"feeTier": 2,
"maxWithdrawAmount": "0.88308000",
"totalInitialMargin": "0.00000000",
"totalMaintenanceMargin": "0.00000000",
"totalMarginBalance": "0.88308000",
"totalOpenOrderInitialMargin": "0.00000000",
"totalPositionInitialMargin": "0.00000000",
"totalUnrealizedProfit": "0.00000000",
"totalWalletBalance": "0.88308000",
"updateTime": 1576756674610
}
GET /sapi/v1/sub-account/futures/account
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get Summary of Sub-account's Futures Account (For Master Account)
Response
{
"totalInitialMargin": "9.83137400",
"totalMaintenanceMargin": "0.41568700",
"totalMarginBalance": "23.03235621",
"totalOpenOrderInitialMargin": "9.00000000",
"totalPositionInitialMargin": "0.83137400",
"totalUnrealizedProfit": "0.03219710",
"totalWalletBalance": "22.15879444",
"asset": "USD",
"subAccountList":[
{
"email": "123@test.com",
"totalInitialMargin": "9.00000000",
"totalMaintenanceMargin": "0.00000000",
"totalMarginBalance": "22.12659734",
"totalOpenOrderInitialMargin": "9.00000000",
"totalPositionInitialMargin": "0.00000000",
"totalUnrealizedProfit": "0.00000000",
"totalWalletBalance": "22.12659734",
"asset": "USD"
},
{
"email": "345@test.com",
"totalInitialMargin": "0.83137400",
"totalMaintenanceMargin": "0.41568700",
"totalMarginBalance": "0.90575887",
"totalOpenOrderInitialMargin": "0.00000000",
"totalPositionInitialMargin": "0.83137400",
"totalUnrealizedProfit": "0.03219710",
"totalWalletBalance": "0.87356177",
"asset": "USD"
}
]
}
GET /sapi/v1/sub-account/futures/accountSummary
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get Futures Position-Risk of Sub-account (For Master Account)
Response
[
{
"entryPrice": "9975.12000",
"leverage": "50", // current initial leverage
"maxNotional": "1000000", // notional value limit of current initial leverage
"liquidationPrice": "7963.54",
"markPrice": "9973.50770517",
"positionAmount": "0.010",
"symbol": "BTCUSDT",
"unrealizedProfit": "-0.01612295"
}
]
GET /sapi/v1/sub-account/futures/positionRisk
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Futures Transfer for Sub-account (For Master Account)
Response
{
"txnId":"2966662589"
}
POST /sapi/v1/sub-account/futures/transfer
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
asset | STRING | YES | The asset being transferred, e.g., USDT |
amount | DECIMAL | YES | The amount to be transferred |
type | INT | YES | 1: transfer from subaccount's spot account to its USDT-margined futures account 2: transfer from subaccount's USDT-margined futures account to its spot account 3: transfer from subaccount's spot account to its COIN-margined futures account 4:transfer from subaccount's COIN-margined futures account to its spot account |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to open Enable Spot & Margin Trading permission for the API Key which requests this endpoint.
Margin Transfer for Sub-account (For Master Account)
Response
{
"txnId":"2966662589"
}
POST /sapi/v1/sub-account/margin/transfer
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
asset | STRING | YES | The asset being transferred, e.g., BTC |
amount | DECIMAL | YES | The amount to be transferred |
type | INT | YES | 1: transfer from subaccount's spot account to margin account 2: transfer from subaccount's margin account to its spot account |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to open Enable Spot & Margin Trading permission for the API Key which requests this endpoint.
Transfer to Sub-account of Same Master (For Sub-account)
Response
{
"txnId":"2966662589"
}
POST /sapi/v1/sub-account/transfer/subToSub
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
toEmail | STRING | YES | Sub-account email |
asset | STRING | YES | |
amount | DECIMAL | YES | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to open Enable Spot & Margin Trading permission for the API Key which requests this endpoint.
Transfer to Master (For Sub-account)
Response
{
"txnId":"2966662589"
}
POST /sapi/v1/sub-account/transfer/subToMaster
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | YES | |
amount | DECIMAL | YES | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to open Enable Spot & Margin Trading permission for the API Key which requests this endpoint.
Sub-account Transfer History (For Sub-account)
Response
[
{
"counterParty":"master",
"email":"master@test.com",
"type":1, // 1 for transfer in, 2 for transfer out
"asset":"BTC",
"qty":"1",
"fromAccountType":"SPOT",
"toAccountType":"SPOT",
"status":"SUCCESS", // status: PROCESS / SUCCESS / FAILURE
"tranId":11798835829,
"time":1544433325000
},
{
"counterParty":"subAccount",
"email":"sub2@test.com",
"type":1,
"asset":"ETH",
"qty":"2",
"fromAccountType":"SPOT",
"toAccountType":"COIN_FUTURE",
"status":"SUCCESS",
"tranId":11798829519,
"time":1544433326000
}
]
GET /sapi/v1/sub-account/transfer/subUserHistory
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | NO | If not sent, result of all assets will be returned |
type | INT | NO | 1: transfer in, 2: transfer out |
startTime | LONG | NO | |
endTime | LONG | NO | |
limit | INT | NO | Default 500 |
returnFailHistory | BOOLEAN | NO | Default False , return PROCESS and SUCCESS status history; If True ,return PROCESS and SUCCESS and FAILURE status history |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- If type is not sent, the records of type 2: transfer out will be returned by default.
- If startTime and endTime are not sent, the recent 30-day data will be returned.
Universal Transfer (For Master Account)
Response
{
"tranId":11945860693,
"clientTranId":"test"
}
POST /sapi/v1/sub-account/universalTransfer
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
fromEmail | STRING | NO | |
toEmail | STRING | NO | |
fromAccountType | STRING | YES | "SPOT","USDT_FUTURE","COIN_FUTURE","MARGIN"(Cross),"ISOLATED_MARGIN" |
toAccountType | STRING | YES | "SPOT","USDT_FUTURE","COIN_FUTURE","MARGIN"(Cross),"ISOLATED_MARGIN" |
clientTranId | STRING | NO | Must be unique |
symbol | STRING | NO | Only supported under ISOLATED_MARGIN type |
asset | STRING | YES | |
amount | DECIMAL | YES | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to enable "internal transfer" option for the api key which requests this endpoint.
- Transfer from master account by default if fromEmail is not sent.
- Transfer to master account by default if toEmail is not sent.
- At least either fromEmail or toEmail need to be sent when the fromAccountType and the toAccountType are the same.
- Supported transfer scenarios:
SPOT
transfer toSPOT
,USDT_FUTURE
,COIN_FUTURE
(regardless of master or sub)SPOT
,USDT_FUTURE
,COIN_FUTURE
transfer toSPOT
(regardless of master or sub)- Master account
SPOT
transfer to sub-accountMARGIN(Cross)
,ISOLATED_MARGIN
- Sub-account
MARGIN(Cross)
,ISOLATED_MARGIN
transfer to master accountSPOT
- Sub-account
MARGIN(Cross)
transfer to Sub-accountMARGIN(Cross)
Query Universal Transfer History (For Master Account)
Response
{
"result": [
{
"tranId": 92275823339,
"fromEmail": "abctest@gmail.com",
"toEmail": "deftest@gmail.com",
"asset": "BNB",
"amount": "0.01",
"createTimeStamp": 1640317374000,
"fromAccountType": "USDT_FUTURE",
"toAccountType": "SPOT",
"status": "SUCCESS",
"clientTranId": "test"
}
],
"totalCount": 1
}
GET /sapi/v1/sub-account/universalTransfer
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
fromEmail | STRING | NO | |
toEmail | STRING | NO | |
clientTranId | STRING | NO | |
startTime | LONG | NO | |
endTime | LONG | NO | |
page | INT | NO | Default 1 |
limit | INT | NO | Default 500, Max 500 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- fromEmail and toEmail cannot be sent at the same time.
- Return fromEmail equal master account email by default.
- The query time period must be less then 30 days.
- If startTime and endTime not sent, return records of the last 30 days by default.
Get Detail on Sub-account's Futures Account V2 (For Master Account)
Response
USDT Margined Futures:
{
"futureAccountResp": {
"email": "abc@test.com",
"assets":[
{
"asset": "USDT",
"initialMargin": "0.00000000",
"maintenanceMargin": "0.00000000",
"marginBalance": "0.88308000",
"maxWithdrawAmount": "0.88308000",
"openOrderInitialMargin": "0.00000000",
"positionInitialMargin": "0.00000000",
"unrealizedProfit": "0.00000000",
"walletBalance": "0.88308000"
}
],
"canDeposit": true,
"canTrade": true,
"canWithdraw": true,
"feeTier": 2,
"maxWithdrawAmount": "0.88308000",
"totalInitialMargin": "0.00000000",
"totalMaintenanceMargin": "0.00000000",
"totalMarginBalance": "0.88308000",
"totalOpenOrderInitialMargin": "0.00000000",
"totalPositionInitialMargin": "0.00000000",
"totalUnrealizedProfit": "0.00000000",
"totalWalletBalance": "0.88308000",
"updateTime": 1576756674610
}
}
COIN Margined Futures:
{
"deliveryAccountResp": {
"email": "abc@test.com",
"assets":[
{
"asset": "BTC",
"initialMargin": "0.00000000",
"maintenanceMargin": "0.00000000",
"marginBalance": "0.88308000",
"maxWithdrawAmount": "0.88308000",
"openOrderInitialMargin": "0.00000000",
"positionInitialMargin": "0.00000000",
"unrealizedProfit": "0.00000000",
"walletBalance": "0.88308000"
}
],
"canDeposit": true,
"canTrade": true,
"canWithdraw": true,
"feeTier": 2,
"updateTime": 1598959682001
}
}
GET /sapi/v2/sub-account/futures/account
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
futuresType | INT | YES | 1:USDT Margined Futures, 2:COIN Margined Futures |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get Summary of Sub-account's Futures Account V2 (For Master Account)
Response
USDT Margined Futures:
{
"futureAccountSummaryResp": {
"totalInitialMargin": "9.83137400",
"totalMaintenanceMargin": "0.41568700",
"totalMarginBalance": "23.03235621",
"totalOpenOrderInitialMargin": "9.00000000",
"totalPositionInitialMargin": "0.83137400",
"totalUnrealizedProfit": "0.03219710",
"totalWalletBalance": "22.15879444",
"asset": "USD",
"subAccountList":[
{
"email": "123@test.com",
"totalInitialMargin": "9.00000000",
"totalMaintenanceMargin": "0.00000000",
"totalMarginBalance": "22.12659734",
"totalOpenOrderInitialMargin": "9.00000000",
"totalPositionInitialMargin": "0.00000000",
"totalUnrealizedProfit": "0.00000000",
"totalWalletBalance": "22.12659734",
"asset": "USD"
},
{
"email": "345@test.com",
"totalInitialMargin": "0.83137400",
"totalMaintenanceMargin": "0.41568700",
"totalMarginBalance": "0.90575887",
"totalOpenOrderInitialMargin": "0.00000000",
"totalPositionInitialMargin": "0.83137400",
"totalUnrealizedProfit": "0.03219710",
"totalWalletBalance": "0.87356177",
"asset": "USD"
}
]
}
}
COIN Margined Futures:
{
"deliveryAccountSummaryResp": {
"totalMarginBalanceOfBTC": "25.03221121",
"totalUnrealizedProfitOfBTC": "0.12233410",
"totalWalletBalanceOfBTC": "22.15879444",
"asset": "BTC",
"subAccountList":[
{
"email": "123@test.com",
"totalMarginBalance": "22.12659734",
"totalUnrealizedProfit": "0.00000000",
"totalWalletBalance": "22.12659734",
"asset": "BTC"
},
{
"email": "345@test.com",
"totalMarginBalance": "0.90575887",
"totalUnrealizedProfit": "0.03219710",
"totalWalletBalance": "0.87356177",
"asset": "BTC"
}
]
}
}
GET /sapi/v2/sub-account/futures/accountSummary
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
futuresType | INT | YES | 1:USDT Margined Futures, 2:COIN Margined Futures |
page | INT | NO | default:1 |
limit | INT | NO | default:10, max:20 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get Futures Position-Risk of Sub-account V2 (For Master Account)
Response
USDT Margined Futures:
{
"futurePositionRiskVos": [
{
"entryPrice": "9975.12000",
"leverage": "50", // current initial leverage
"maxNotional": "1000000", // notional value limit of current initial leverage
"liquidationPrice": "7963.54",
"markPrice": "9973.50770517",
"positionAmount": "0.010",
"symbol": "BTCUSDT",
"unrealizedProfit": "-0.01612295"
}
]
}
COIN Margined Futures:
{
"deliveryPositionRiskVos": [
{
"entryPrice": "9975.12000",
"markPrice": "9973.50770517",
"leverage": "20",
"isolated": "false",
"isolatedWallet": "9973.50770517",
"isolatedMargin": "0.00000000",
"isAutoAddMargin": "false",
"positionSide": "BOTH",
"positionAmount": "1.230",
"symbol": "BTCUSD_201225",
"unrealizedProfit": "-0.01612295"
}
]
}
GET /sapi/v2/sub-account/futures/positionRisk
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
futuresType | INT | YES | 1:USDT Margined Futures, 2:COIN Margined Futures |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get IP Restriction for a Sub-account API Key (For Master Account)
Response:
{
"ipRestrict": "true",
"ipList": [
"69.210.67.14",
"8.34.21.10"
],
"updateTime": 1636371437000,
"apiKey": "k5V49ldtn4tszj6W3hystegdfvmGbqDzjmkCtpTvC0G74WhK7yd4rfCTo4lShf"
}
GET /sapi/v1/sub-account/subAccountApi/ipRestriction
Weight(UID): 3000
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
subAccountApiKey | STRING | YES | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Delete IP List For a Sub-account API Key (For Master Account)
Response:
{
"ipRestrict": "true",
"ipList": [
"69.210.67.14",
"8.34.21.10"
],
"updateTime": 1636371437000,
"apiKey": "k5V49ldtn4tszj6W3hystegdfvmGbqDzjmkCtpTvC0G74WhK7yd4rfCTo4lShf"
}
DELETE /sapi/v1/sub-account/subAccountApi/ipRestriction/ipList
Weight(UID): 3000
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
subAccountApiKey | STRING | YES | |
ipAddress | STRING | NO | Can be added in batches, separated by commas |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to enable Enable Spot & Margin Trading option for the api key which requests this endpoint
Add IP Restriction for Sub-Account API key (For Master Account)
Response:
{
"status": "2",
"ipList": [
"69.210.67.14",
"8.34.21.10", //only return if you open IP restriction and input IP address.
],
"updateTime": 1636371437000,
"apiKey": "k5V49ldtn4tszj6W3hystegdfvmGbqDzjmkCtpTvC0G74WhK7yd4rfCTo4lShf"
}
POST /sapi/v2/sub-account/subAccountApi/ipRestriction
Weight(UID): 3000
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub-account email | |
subAccountApiKey | STRING | YES | |
status | STRING | YES | IP Restriction status. 1 = IP Unrestricted. 2 = Restrict access to trusted IPs only. |
ipAddress | STRING | NO | Insert static IP in batch, separated by commas. |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to enable Enable Spot & Margin Trading option for the api key which requests this endpoint
Deposit Assets Into The Managed Sub-account(For Investor Master Account)
Response
{
"tranId":66157362489
}
POST /sapi/v1/managed-subaccount/deposit
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
toEmail | STRING | YES | |
asset | STRING | YES | |
amount | DECIMAL | YES | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to enable
Enable Spot & Margin Trading
option for the api key which requests this endpoint
Query Managed Sub-account Asset Details(For Investor Master Account)
Response
[
{
"coin": "INJ",
"name": "Injective Protocol",
"totalBalance": "0",
"availableBalance": "0",
"inOrder": "0",
"btcValue": "0"
},
{
"coin": "FILDOWN",
"name": "FILDOWN",
"totalBalance": "0",
"availableBalance": "0",
"inOrder": "0",
"btcValue": "0"
}
]
GET /sapi/v1/managed-subaccount/asset
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | ||
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Withdrawl Assets From The Managed Sub-account(For Investor Master Account)
Response
{
"tranId":66157362489
}
POST /sapi/v1/managed-subaccount/withdraw
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
fromEmail | STRING | YES | |
asset | STRING | YES | |
amount | DECIMAL | YES | |
transferDate | LONG | NO | Withdrawals is automatically occur on the transfer date(UTC0). If a date is not selected, the withdrawal occurs right now |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- You need to enable
Enable Spot & Margin Trading
option for the api key which requests this endpoint
Query Managed Sub-account Snapshot(For Investor Master Account)
Response:
{
"code":200, // 200 for success; others are error codes
"msg":"", // error message
"snapshotVos":[
{
"data":{
"balances":[
{
"asset":"BTC",
"free":"0.09905021",
"locked":"0.00000000"
},
{
"asset":"USDT",
"free":"1.89109409",
"locked":"0.00000000"
}
],
"totalAssetOfBtc":"0.09942700"
},
"type":"spot",
"updateTime":1576281599000
}
]
}
OR
{
"code":200, // 200 for success; others are error codes
"msg":"", // error message
"snapshotVos":[
{
"data":{
"marginLevel":"2748.02909813",
"totalAssetOfBtc":"0.00274803",
"totalLiabilityOfBtc":"0.00000100",
"totalNetAssetOfBtc":"0.00274750",
"userAssets":[
{
"asset":"XRP",
"borrowed":"0.00000000",
"free":"1.00000000",
"interest":"0.00000000",
"locked":"0.00000000",
"netAsset":"1.00000000"
}
]
},
"type":"margin",
"updateTime":1576281599000
}
]
}
OR
{
"code":200, // 200 for success; others are error codes
"msg":"", // error message
"snapshotVos":[
{
"data":{
"assets":[
{
"asset":"USDT",
"marginBalance":"118.99782335",
"walletBalance":"120.23811389"
}
],
"position":[
{
"entryPrice":"7130.41000000",
"markPrice":"7257.66239673",
"positionAmt":"0.01000000",
"symbol":"BTCUSDT",
"unRealizedProfit":"1.24029054" // Only show the value at the time of opening the position
}
]
},
"type":"futures",
"updateTime":1576281599000
}
]
}
GET /sapi/v1/managed-subaccount/accountSnapshot
Weight(IP): 2400
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | ||
type | STRING | YES | "SPOT", "MARGIN"(cross), "FUTURES"(UM) |
startTime | LONG | NO | |
endTime | LONG | NO | |
limit | INT | NO | min 7, max 30, default 7 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- The query time period must be less then 30 days
- Support query within the last one month only
- If startTimeand endTime not sent, return records of the last 7 days by default
Query Managed Sub Account Transfer Log (For Investor Master Account) (USER_DATA)
Response
{
managerSubTransferHistoryVos: [
{
fromEmail: "test_0_virtual@kq3kno9imanagedsub.com"
fromAccountType: "SPOT"
toEmail: "wdywl0lddakh@test.com"
toAccountType: "SPOT"
asset: "BNB"
amount: "0.01"
scheduledData: 1679416673000
createTime: 1679416673000
status: "SUCCESS"
tranId: 91077779
},
{
fromEmail: "wdywl0lddakh@test.com"
fromAccountType: "SPOT"
toEmail: "test_0_virtual@kq3kno9imanagedsub.com"
toAccountType: "SPOT"
asset: "BNB"
amount: "1"
scheduledData: 1679416616000
createTime: 1679416616000
status: "SUCCESS"
tranId: 91077676
}
]
count: 2
}
GET /sapi/v1/managed-subaccount/queryTransLogForInvestor
Investor can use this api to query managed sub account transfer log. This endpoint is available for investor of Managed Sub-Account. A Managed Sub-Account is an account type for investors who value flexibility in asset allocation and account application, while delegating trades to a professional trading team. Please refer to link
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Managed Sub Account Email | |
startTime | LONG | YES | Start Time |
endTime | LONG | YES | End Time (The start time and end time interval cannot exceed half a year) |
page | INT | YES | Page |
limit | INT | YES | Limit (Max: 500) |
transfers | STRING | NO | Transfer Direction (from/to) |
transferFunctionAccountType | STRING | NO | Transfer function account type (SPOT/MARGIN/ISOLATED_MARGIN/USDT_FUTURE/COIN_FUTURE) |
Query Managed Sub Account Transfer Log (For Trading Team Master Account) (USER_DATA)
Response
{
managerSubTransferHistoryVos: [
{
fromEmail: "test_0_virtual@kq3kno9imanagedsub.com"
fromAccountType: "SPOT"
toEmail: "wdywl0lddakh@test.com"
toAccountType: "SPOT"
asset: "BNB"
amount: "0.01"
scheduledData: 1679416673000
createTime: 1679416673000
status: "SUCCESS"
tranId: 91077779
},
{
fromEmail: "wdywl0lddakh@test.com"
fromAccountType: "SPOT"
toEmail: "test_0_virtual@kq3kno9imanagedsub.com"
toAccountType: "SPOT"
asset: "BNB"
amount: "1"
scheduledData: 1679416616000
createTime: 1679416616000
status: "SUCCESS"
tranId: 91077676
}
]
count: 2
}
GET /sapi/v1/managed-subaccount/queryTransLogForTradeParent
Trading team can use this api to query managed sub account transfer log. This endpoint is available for trading team of Managed Sub-Account. A Managed Sub-Account is an account type for investors who value flexibility in asset allocation and account application, while delegating trades to a professional trading team. Please refer to link
Weight(UID): 60
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Managed Sub Account Email | |
startTime | LONG | YES | Start Time |
endTime | LONG | YES | End Time (The start time and end time interval cannot exceed half a year) |
page | INT | YES | Page |
limit | INT | YES | Limit (Max: 500) |
transfers | STRING | NO | Transfer Direction (FROM/TO) |
transferFunctionAccountType | STRING | NO | Transfer function account type (SPOT/MARGIN/ISOLATED_MARGIN/USDT_FUTURE/COIN_FUTURE) |
Query Managed Sub-account Futures Asset Details(For Investor Master Account)(USER_DATA)
Response
{
"code": "200",
"message": "OK",
"snapshotVos": [
{
"type": "FUTURES",
"updateTime": 1672893855394,
"data": {
"assets": [
{
"asset": "USDT",
"marginBalance": 100,
"walletBalance": 120
}
],
"position": [
{
"symbol": "BTCUSDT",
"entryPrice": 17000,
"markPrice": 17000,
"positionAmt": 0.0001
}
]
}
}
]
}
GET /sapi/v1/managed-subaccount/fetch-future-asset
Investor can use this api to query managed sub account futures asset details
Weight(UID): 60
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Managed Sub Account Email |
Query Managed Sub-account Margin Asset Details (For Investor Master Account) (USER_DATA)
Response
{
marginLevel:"999"
totalAssetOfBtc:"0"
totalLiabilityOfBtc:"0"
totalNetAssetOfBtc:"0"
userAssets:[
0:{
asset:"MATIC"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
1:{
asset:"VET"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
2:{
asset:"BAKE"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
3:{
asset:"SHIB"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
4:{
asset:"USDT"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
5:{
asset:"DOGE"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
6:{
asset:"AAVE"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
7:{
asset:"ONT"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
8:{
asset:"XRP"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
9:{
asset:"XLM"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
10:{
asset:"LINK"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
11:{
asset:"QTUM"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
12:{
asset:"ETHW"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
13:{
asset:"XTZ"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
14:{
asset:"LUNA"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
15:{
asset:"EUR"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
16:{
asset:"IOST"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
17:{
asset:"BCH"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
18:{
asset:"BTC"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
19:{
asset:"IOTA"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
20:{
asset:"CREAM"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
21:{
asset:"BAT"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
22:{
asset:"BNB"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
23:{
asset:"ETH"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
24:{
asset:"ZEC"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
25:{
asset:"USDC"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
26:{
asset:"LTC"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
27:{
asset:"BUSD"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
28:{
asset:"ZIL"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
29:{
asset:"THETA"
borrowed:"0"
free:"0"
interest:"0"
locked:"0"
netAsset:"0"
}
]
}
GET /sapi/v1/managed-subaccount/marginAsset
Investor can use this api to query managed sub account margin asset details
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Managed Sub Account Email |
Query Sub-account Assets (For Master Account)(USER_DATA)
Response
{
"balances":[
{
"asset":"ADA",
"free":"10000",
"locked":"0"
},
{
"asset":"BNB",
"free":"10003",
"locked":"0"
},
{
"asset":"BTC",
"free":"11467.6399",
"locked":"0"
}
]
}
GET /sapi/v4/sub-account/assets
Fetch sub-account assets
Weight(UID): 60
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Managed Sub Account Email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Query Managed Sub-account List (For Investor)(USER_DATA)
Response
{
total: 3
managerSubUserInfoVoList: [
0: {
rootUserId: 1000138475670
managersubUserId: 1000137842513
bindParentUserId: 1000138475669
email: "test_0_virtual@kq3kno9imanagedsub.com"
insertTimeStamp: 1678435149000
bindParentEmail: "wdyw8xsh8pey@test.com"
isSubUserEnabled: true
isUserActive: true
isMarginEnabled: false
isFutureEnabled: false
isSignedLVTRiskAgreement: false
}
1: {
rootUserId: 1000138475670
managersubUserId: 1000137842514
bindParentUserId: 1000138475669
email: "test_1_virtual@4qd2u7zxmanagedsub.com"
insertTimeStamp: 1678435152000
bindParentEmail: "wdyw8xsh8pey@test.com"
isSubUserEnabled: true
isUserActive: true
isMarginEnabled: false
isFutureEnabled: false
isSignedLVTRiskAgreement: false
}
2: {
rootUserId: 1000138475670
managersubUserId: 1000137842515
bindParentUserId: 1000138475669
email: "test_2_virtual@akc05o8hmanagedsub.com"
insertTimeStamp: 1678435153000
bindParentEmail: "wdyw8xsh8pey@test.com"
isSubUserEnabled: true
isUserActive: true
isMarginEnabled: false
isFutureEnabled: false
isSignedLVTRiskAgreement: false
}
]
}
GET /sapi/v1/managed-subaccount/info
Get investor's managed sub-account list.
Weight(UID): 60
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | NO | Managed sub-account email | |
page | INT | NO | Default value: 1 |
limit | INT | NO | Default value: 20, Max value: 20 |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Query Sub-account Transaction Statistics (For Master Account) (USER_DATA)
Response example:
{
"recent30BtcTotal": "0",
"recent30BtcFuturesTotal": "0",
"recent30BtcMarginTotal": "0",
"recent30BusdTotal": "0",
"recent30BusdFuturesTotal": "0",
"recent30BusdMarginTotal": "0",
"tradeInfoVos": []
}
OR
{
"recent30BtcTotal": "0",
"recent30BtcFuturesTotal": "0",
"recent30BtcMarginTotal": "0",
"recent30BusdTotal": "0",
"recent30BusdFuturesTotal": "0",
"recent30BusdMarginTotal": "0",
"tradeInfoVos": [
{
"userId": 1000138138384,
"btc": 0,
"btcFutures": 0,
"btcMargin": 0,
"busd": 0,
"busdFutures": 0,
"busdMargin": 0,
"date": 1676851200000
},
{
"userId": 1000138138384,
"btc": 0,
"btcFutures": 0,
"btcMargin": 0,
"busd": 0,
"busdFutures": 0,
"busdMargin": 0,
"date": 1677110400000
},
{
"userId": 1000138138384,
"btc": 0,
"btcFutures": 0,
"btcMargin": 0,
"busd": 0,
"busdFutures": 0,
"busdMargin": 0,
"date": 1677369600000
}
]
}
GET /sapi/v1/sub-account/transaction-statistics
Query Sub-account Transaction statistics (For Master Account).
Weight(UID): 60
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub user email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get Managed Sub-account Deposit Address (For Investor Master Account) (USER_DATA)
Response:
{
"coin": "USDT",
"address": "0x206c22d833bb0bb2102da6b7c7d4c3eb14bcf73d",
"tag": "",
"url": "https://etherscan.io/address/0x206c22d833bb0bb2102da6b7c7d4c3eb14bcf73d"
}
GET /sapi/v1/managed-subaccount/deposit/address
Get investor's managed sub-account deposit address.
Weight(UID): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub user email | |
coin | STRING | YES | |
network | STRING | NO | networks can be found in GET /sapi/v1/capital/deposit/address |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- If
network
is not send, return with defaultnetwork
of thecoin
.
Enable Options for Sub-account (For Master Account)(USER_DATA)
Response:
{
"email":"123@test.com",
"isEOptionsEnabled": true // true or false
}
POST /sapi/v1/sub-account/eoptions/enable
Enable Options for Sub-account (For Master Account).
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
STRING | YES | Sub user email | |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Query Managed Sub Account Transfer Log (For Trading Team Sub Account)(USER_DATA)
Response:
{
"managerSubTransferHistoryVos": [
{
"fromEmail": "test_0_virtual@kq3kno9imanagedsub.com",
"fromAccountType": "SPOT",
"toEmail": "wdywl0lddakh@test.com",
"toAccountType": "SPOT",
"asset": "BNB",
"amount": "0.01",
"scheduledData": 1679416673000,
"createTime": 1679416673000,
"status": "SUCCESS",
"tranId": 91077779
},
{
"fromEmail": "wdywl0lddakh@test.com",
"fromAccountType": "SPOT",
"toEmail": "test_0_virtual@kq3kno9imanagedsub.com",
"toAccountType": "SPOT",
"asset": "BNB",
"amount": "1",
"scheduledData": 1679416616000,
"createTime": 1679416616000,
"status": "SUCCESS",
"tranId": 91077676
}
],
"count": 2
}
GET /sapi/v1/managed-subaccount/query-trans-log
Query Managed Sub Account Transfer Log (For Trading Team Sub Account)
Weight(UID): 60
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
startTime | LONG | YES | Start Time |
endTime | LONG | YES | End Time (The start time and end time interval cannot exceed half a year) |
page | INT | YES | Page |
limit | INT | YES | Limit (Max: 500) |
transfers | STRING | NO | Transfer Direction (FROM/TO) |
transferFunctionAccountType | STRING | NO | Transfer function account type (SPOT/MARGIN/ISOLATED_MARGIN/USDT_FUTURE/COIN_FUTURE) |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Market Data Endpoints
Test Connectivity
Response:
{}
GET /api/v3/ping
Test connectivity to the Rest API.
Weight(IP): 1
Parameters:
NONE
Data Source: Memory
Check Server Time
Response:
{
"serverTime": 1499827319559
}
GET /api/v3/time
Test connectivity to the Rest API and get the current server time.
Weight(IP): 1
Parameters:
NONE
Data Source: Memory
Exchange Information
Response:
{
"timezone": "UTC",
"serverTime": 1565246363776,
"rateLimits": [
{
//These are defined in the `ENUM definitions` section under `Rate Limiters (rateLimitType)`.
//All limits are optional
}
],
"exchangeFilters": [
//These are the defined filters in the `Filters` section.
//All filters are optional.
],
"symbols": [
{
"symbol": "ETHBTC",
"status": "TRADING",
"baseAsset": "ETH",
"baseAssetPrecision": 8,
"quoteAsset": "BTC",
"quotePrecision": 8,
"quoteAssetPrecision": 8,
"orderTypes": [
"LIMIT",
"LIMIT_MAKER",
"MARKET",
"STOP_LOSS",
"STOP_LOSS_LIMIT",
"TAKE_PROFIT",
"TAKE_PROFIT_LIMIT"
],
"icebergAllowed": true,
"ocoAllowed": true,
"quoteOrderQtyMarketAllowed": true,
"allowTrailingStop": false,
"cancelReplaceAllowed": false,
"isSpotTradingAllowed": true,
"isMarginTradingAllowed": true,
"filters": [
//These are defined in the Filters section.
//All filters are optional
],
"permissions": [],
"permissionSets": [
[
"SPOT",
"MARGIN"
]
],
"defaultSelfTradePreventionMode": "NONE",
"allowedSelfTradePreventionModes": [
"NONE"
]
}
]
}
GET /api/v3/exchangeInfo
Current exchange trading rules and symbol information
Weight(IP): 20
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | No | Example: curl -X GET "https://api.binance.com/api/v3/exchangeInfo?symbol=BNBBTC" |
symbols | ARRAY OF STRING | No | Examples: curl -X GET "https://api.binance.com/api/v3/exchangeInfo?symbols=%5B%22BNBBTC%22,%22BTCUSDT%22%5D" or curl -g -X GET 'https://api.binance.com/api/v3/exchangeInfo?symbols=["BTCUSDT","BNBBTC"]' |
permissions | ENUM | No | Examples: curl -X GET "https://api.binance.com/api/v3/exchangeInfo?permissions=SPOT" or curl -X GET "https://api.binance.com/api/v3/exchangeInfo?permissions=%5B%22MARGIN%22%2C%22LEVERAGED%22%5D" or curl -g -X GET 'https://api.binance.com/api/v3/exchangeInfo?permissions=["MARGIN","LEVERAGED"]' |
showPermissionSets | BOOLEAN | No | Controls whether the content of the permissionSets field is populated or not. Defaults to true . |
symbolStatus | ENUM | No | Filters symbols that have this tradingStatus . Valid values: TRADING , HALT , BREAK Cannot be used in combination with symbols or symbol . |
Notes:
- If the value provided to
symbol
orsymbols
do not exist, the endpoint will throw an error saying the symbol is invalid. - All parameters are optional.
permissions
can support single or multiple values (e.g.SPOT
,["MARGIN","LEVERAGED"]
). This cannot be used in combination withsymbol
orsymbols
.- If
permissions
parameter not provided, all symbols that have eitherSPOT
,MARGIN
, orLEVERAGED
permission will be exposed.- To display symbols with any permission you need to specify them explicitly in
permissions
: (e.g.["SPOT","MARGIN",...]
.). See Account and Symbol Permissions for the full list.
- To display symbols with any permission you need to specify them explicitly in
Examples of Symbol Permissions Interpretation from the Response:
[["A","B"]]
means you may place an order if your account has either permission "A" or permission "B".[["A"],["B"]]
means you can place an order if your account has permission "A" and permission "B".[["A"],["B","C"]]
means you can place an order if your account has permission "A" and permission "B" or permission "C". (Inclusive or is applied here, not exclusive or, so your account may have both permission "B" and permission "C".)
Data Source: Memory
Order Book
Response:
{
"lastUpdateId": 1027024,
"bids": [
[
"4.00000000", // PRICE
"431.00000000" // QTY
]
],
"asks": [
[
"4.00000200",
"12.00000000"
]
]
}
GET /api/v3/depth
Weight(IP):
Adjusted based on the limit:
Limit | Weight |
---|---|
1-100 | 5 |
101-500 | 25 |
501-1000 | 50 |
1001-5000 | 250 |
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
limit | INT | NO | Default 100; max 5000. If limit > 5000, then the response will truncate to 5000. |
Data Source: Memory
Recent Trades List
Response:
[
{
"id": 28457,
"price": "4.00000100",
"qty": "12.00000000",
"quoteQty": "48.000012",
"time": 1499865549590,
"isBuyerMaker": true,
"isBestMatch": true
}
]
GET /api/v3/trades
Get recent trades.
Weight(IP): 25
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
limit | INT | NO | Default 500; max 1000. |
Data Source: Memory
Old Trade Lookup
Response:
[
{
"id": 28457,
"price": "4.00000100",
"qty": "12.00000000",
"quoteQty": "48.000012",
"time": 1499865549590, // Trade executed timestamp, as same as `T` in the stream
"isBuyerMaker": true,
"isBestMatch": true
}
]
GET /api/v3/historicalTrades
Get older market trades.
Weight(IP): 25
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
limit | INT | NO | Default 500; max 1000. |
fromId | LONG | NO | Trade id to fetch from. Default gets most recent trades. |
Data Source: Database
Compressed/Aggregate Trades List
Response:
[
{
"a": 26129, // Aggregate tradeId
"p": "0.01633102", // Price
"q": "4.70443515", // Quantity
"f": 27781, // First tradeId
"l": 27781, // Last tradeId
"T": 1498793709153, // Timestamp
"m": true, // Was the buyer the maker?
"M": true // Was the trade the best price match?
}
]
GET /api/v3/aggTrades
Get compressed, aggregate trades. Trades that fill at the time, from the same order, with the same price will have the quantity aggregated.
Weight(IP): 2
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
fromId | LONG | NO | id to get aggregate trades from INCLUSIVE. |
startTime | LONG | NO | Timestamp in ms to get aggregate trades from INCLUSIVE. |
endTime | LONG | NO | Timestamp in ms to get aggregate trades until INCLUSIVE. |
limit | INT | NO | Default 500; max 1000. |
- If fromId, startTime, and endTime are not sent, the most recent aggregate trades will be returned.
- Note that if a trade has the following values, this was a duplicate aggregate trade and marked as invalid:
- p = '0' // price
- q = '0' // qty
- f = -1 // first_trade_id
- l = -1 // last_trade_id
Data Source: Database
Kline/Candlestick Data
Response:
[
[
1499040000000, // Kline open time
"0.01634790", // Open price
"0.80000000", // High price
"0.01575800", // Low price
"0.01577100", // Close price
"148976.11427815", // Volume
1499644799999, // Kline Close time
"2434.19055334", // Quote asset volume
308, // Number of trades
"1756.87402397", // Taker buy base asset volume
"28.46694368", // Taker buy quote asset volume
"0" // Unused field, ignore.
]
]
GET /api/v3/klines
Kline/candlestick bars for a symbol.
Klines are uniquely identified by their open time.
Weight(IP): 2
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
interval | ENUM | YES | |
startTime | LONG | NO | |
endTime | LONG | NO | |
timeZone | STRING | NO | Default: 0 (UTC) |
limit | INT | NO | Default 500; max 1000. |
- If startTime and endTime are not sent, the most recent klines are returned.
- Supported values for
timeZone
:- Hours and minutes (e.g.
-1:00
,05:45
) - Only hours (e.g.
0
,8
,4
) - Accepted range is strictly [-12:00 to +14:00] inclusive
- Hours and minutes (e.g.
- If
timeZone
provided, kline intervals are interpreted in that timezone instead of UTC. - Note that
startTime
andendTime
are always interpreted in UTC, regardless oftimeZone
.
Data Source: Database
UIKlines
Response:
[
[
1499040000000, // Kline open time
"0.01634790", // Open price
"0.80000000", // High price
"0.01575800", // Low price
"0.01577100", // Close price
"148976.11427815", // Volume
1499644799999, // Kline close time
"2434.19055334", // Quote asset volume
308, // Number of trades
"1756.87402397", // Taker buy base asset volume
"28.46694368", // Taker buy quote asset volume
"0" // Unused field. Ignore.
]
]
GET /api/v3/uiKlines
The request is similar to klines having the same parameters and response.
uiKlines
return modified kline data, optimized for presentation of candlestick charts.
Weight: 2
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
interval | ENUM | YES | |
startTime | LONG | NO | |
endTime | LONG | NO | |
timeZone | STRING | NO | Default: 0 (UTC) |
limit | INT | NO | Default 500; max 1000. |
- If
startTime
andendTime
are not sent, the most recent klines are returned. - Supported values for
timeZone
:- Hours and minutes (e.g.
-1:00
,05:45
) - Only hours (e.g.
0
,8
,4
) - Accepted range is strictly [-12:00 to +14:00] inclusive
- Hours and minutes (e.g.
- If
timeZone
provided, kline intervals are interpreted in that timezone instead of UTC. - Note that
startTime
andendTime
are always interpreted in UTC, regardless oftimeZone
.
Data Source: Database
Current Average Price
Response:
{
"mins": 5, // Average price interval (in minutes)
"price": "9.35751834", // Average price
"closeTime": 1694061154503 // Last trade time
}
GET /api/v3/avgPrice
Current average price for a symbol.
Weight(IP): 2
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES |
Data Source: Memory
24hr Ticker Price Change Statistics
Response: - FULL
{
"symbol": "BNBBTC",
"priceChange": "-94.99999800",
"priceChangePercent": "-95.960",
"weightedAvgPrice": "0.29628482",
"prevClosePrice": "0.10002000",
"lastPrice": "4.00000200",
"lastQty": "200.00000000",
"bidPrice": "4.00000000",
"bidQty": "100.00000000",
"askPrice": "4.00000200",
"askQty": "100.00000000",
"openPrice": "99.00000000",
"highPrice": "100.00000000",
"lowPrice": "0.10000000",
"volume": "8913.30000000",
"quoteVolume": "15.30000000",
"openTime": 1499783499040,
"closeTime": 1499869899040,
"firstId": 28385, // First tradeId
"lastId": 28460, // Last tradeId
"count": 76 // Trade count
}
OR
[
{
"symbol": "BNBBTC",
"priceChange": "-94.99999800",
"priceChangePercent": "-95.960",
"weightedAvgPrice": "0.29628482",
"prevClosePrice": "0.10002000",
"lastPrice": "4.00000200",
"lastQty": "200.00000000",
"bidPrice": "4.00000000",
"bidQty": "100.00000000",
"askPrice": "4.00000200",
"askQty": "100.00000000",
"openPrice": "99.00000000",
"highPrice": "100.00000000",
"lowPrice": "0.10000000",
"volume": "8913.30000000",
"quoteVolume": "15.30000000",
"openTime": 1499783499040,
"closeTime": 1499869899040,
"firstId": 28385, // First tradeId
"lastId": 28460, // Last tradeId
"count": 76 // Trade count
}
]
Response - MINI
{
"symbol": "BNBBTC", // Symbol Name
"openPrice": "99.00000000", // Opening price of the Interval
"highPrice": "100.00000000", // Highest price in the interval
"lowPrice": "0.10000000", // Lowest price in the interval
"lastPrice": "4.00000200", // Closing price of the interval
"volume": "8913.30000000", // Total trade volume (in base asset)
"quoteVolume": "15.30000000", // Total trade volume (in quote asset)
"openTime": 1499783499040, // Start of the ticker interval
"closeTime": 1499869899040, // End of the ticker interval
"firstId": 28385, // First tradeId considered
"lastId": 28460, // Last tradeId considered
"count": 76 // Total trade count
}
OR
[
{
"symbol": "BNBBTC",
"openPrice": "99.00000000",
"highPrice": "100.00000000",
"lowPrice": "0.10000000",
"lastPrice": "4.00000200",
"volume": "8913.30000000",
"quoteVolume": "15.30000000",
"openTime": 1499783499040,
"closeTime": 1499869899040,
"firstId": 28385,
"lastId": 28460,
"count": 76
},
{
"symbol": "LTCBTC",
"openPrice": "0.07000000",
"highPrice": "0.07000000",
"lowPrice": "0.07000000",
"lastPrice": "0.07000000",
"volume": "11.00000000",
"quoteVolume": "0.77000000",
"openTime": 1656908192899,
"closeTime": 1656994592899,
"firstId": 0,
"lastId": 10,
"count": 11
}
]
GET /api/v3/ticker/24hr
24 hour rolling window price change statistics. Careful when accessing this with no symbol.
Weight(IP):
Parameter | Symbols Provided | Weight |
---|---|---|
symbol | 1 | 2 |
symbol parameter is omitted | 80 | |
symbols | 1-20 | 2 |
21-100 | 40 | |
101 or more | 80 | |
symbols parameter is omitted | 80 |
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | NO | Parameter symbol and symbols cannot be used in combination. If neither parameter is sent, tickers for all symbols will be returned in an array. Examples of accepted format for the symbols parameter: ["BTCUSDT","BNBUSDT"] or %5B%22BTCUSDT%22,%22BNBUSDT%22%5D |
symbols | STRING | NO | |
type | ENUM | NO | Supported values: FULL or MINI. If none provided, the default is FULL |
Data Source: Memory
Trading Day Ticker
Response: - FULL
{
"symbol": "BTCUSDT",
"priceChange": "-83.13000000", // Absolute price change
"priceChangePercent": "-0.317", // Relative price change in percent
"weightedAvgPrice": "26234.58803036", // quoteVolume / volume
"openPrice": "26304.80000000",
"highPrice": "26397.46000000",
"lowPrice": "26088.34000000",
"lastPrice": "26221.67000000",
"volume": "18495.35066000", // Volume in base asset
"quoteVolume": "485217905.04210480", // Volume in quote asset
"openTime": 1695686400000,
"closeTime": 1695772799999,
"firstId": 3220151555, // Trade ID of the first trade in the interval
"lastId": 3220849281, // Trade ID of the last trade in the interval
"count": 697727 // Number of trades in the interval
}
OR
[
{
"symbol": "BTCUSDT",
"priceChange": "-83.13000000",
"priceChangePercent": "-0.317",
"weightedAvgPrice": "26234.58803036",
"openPrice": "26304.80000000",
"highPrice": "26397.46000000",
"lowPrice": "26088.34000000",
"lastPrice": "26221.67000000",
"volume": "18495.35066000",
"quoteVolume": "485217905.04210480",
"openTime": 1695686400000,
"closeTime": 1695772799999,
"firstId": 3220151555,
"lastId": 3220849281,
"count": 697727
},
{
"symbol": "BNBUSDT",
"priceChange": "2.60000000",
"priceChangePercent": "1.238",
"weightedAvgPrice": "211.92276958",
"openPrice": "210.00000000",
"highPrice": "213.70000000",
"lowPrice": "209.70000000",
"lastPrice": "212.60000000",
"volume": "280709.58900000",
"quoteVolume": "59488753.54750000",
"openTime": 1695686400000,
"closeTime": 1695772799999,
"firstId": 672397461,
"lastId": 672496158,
"count": 98698
}
]
Response: - MINI
{
"symbol": "BTCUSDT",
"openPrice": "26304.80000000",
"highPrice": "26397.46000000",
"lowPrice": "26088.34000000",
"lastPrice": "26221.67000000",
"volume": "18495.35066000", // Volume in base asset
"quoteVolume": "485217905.04210480", // Volume in quote asset
"openTime": 1695686400000,
"closeTime": 1695772799999,
"firstId": 3220151555, // Trade ID of the first trade in the interval
"lastId": 3220849281, // Trade ID of the last trade in the interval
"count": 697727 // Number of trades in the interval
}
OR
[
{
"symbol": "BTCUSDT",
"openPrice": "26304.80000000",
"highPrice": "26397.46000000",
"lowPrice": "26088.34000000",
"lastPrice": "26221.67000000",
"volume": "18495.35066000",
"quoteVolume": "485217905.04210480",
"openTime": 1695686400000,
"closeTime": 1695772799999,
"firstId": 3220151555,
"lastId": 3220849281,
"count": 697727
},
{
"symbol": "BNBUSDT",
"openPrice": "210.00000000",
"highPrice": "213.70000000",
"lowPrice": "209.70000000",
"lastPrice": "212.60000000",
"volume": "280709.58900000",
"quoteVolume": "59488753.54750000",
"openTime": 1695686400000,
"closeTime": 1695772799999,
"firstId": 672397461,
"lastId": 672496158,
"count": 98698
}
]
GET /api/v3/ticker/tradingDay
Price change statistics for a trading day.
Weight:
4 for each requested symbol.
The weight for this request will cap at 200 once the number of symbols
in the request is more than 50.
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | Either symbol or symbols must be provided. Examples of accepted format for the symbols parameter: ["BTCUSDT","BNBUSDT"] or %5B%22BTCUSDT%22,%22BNBUSDT%22%5D The maximum number of symbols allowed in a request is 100. |
symbols | |||
timeZone | STRING | NO | Default: 0 (UTC) |
type | ENUM | NO | Supported values: FULL or MINI. If none provided, the default is FULL. |
Notes:
- Supported values for
timeZone
:- Hours and minutes (e.g.
-1:00
,05:45
) - Only hours (e.g.
0
,8
,4
)
- Hours and minutes (e.g.
Data Source: Database
Symbol Price Ticker
Response:
{
"symbol": "LTCBTC",
"price": "4.00000200"
}
OR
[
{
"symbol": "LTCBTC",
"price": "4.00000200"
},
{
"symbol": "ETHBTC",
"price": "0.07946600"
}
]
GET /api/v3/ticker/price
Latest price for a symbol or symbols.
Weight(IP):
Parameter | Symbols Provided | Weight |
---|---|---|
symbol | 1 | 2 |
symbol parameter is omitted | 4 | |
symbols | Any | 4 |
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | NO | Parameter symbol and symbols cannot be used in combination. If neither parameter is sent, prices for all symbols will be returned in an array. Examples of accepted format for the symbols parameter: ["BTCUSDT","BNBUSDT"] or %5B%22BTCUSDT%22,%22BNBUSDT%22%5D |
symbols | STRING | NO |
Data Source: Memory
Symbol Order Book Ticker
Response:
{
"symbol": "LTCBTC",
"bidPrice": "4.00000000",
"bidQty": "431.00000000",
"askPrice": "4.00000200",
"askQty": "9.00000000"
}
OR
[
{
"symbol": "LTCBTC",
"bidPrice": "4.00000000",
"bidQty": "431.00000000",
"askPrice": "4.00000200",
"askQty": "9.00000000"
},
{
"symbol": "ETHBTC",
"bidPrice": "0.07946700",
"bidQty": "9.00000000",
"askPrice": "100000.00000000",
"askQty": "1000.00000000"
}
]
GET /api/v3/ticker/bookTicker
Best price/qty on the order book for a symbol or symbols.
Weight(IP):
Parameter | Symbols Provided | Weight |
---|---|---|
symbol | 1 | 2 |
symbol parameter is omitted | 4 | |
symbols | Any | 4 |
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | NO | Parameter symbol and symbols cannot be used in combination. If neither parameter is sent, bookTickers for all symbols will be returned in an array. Examples of accepted format for the symbols parameter: ["BTCUSDT","BNBUSDT"] or %5B%22BTCUSDT%22,%22BNBUSDT%22%5D |
symbols | STRING | NO |
Data Source: Memory
Rolling window price change statistics
Response: - FULL
{
"symbol": "BNBBTC",
"priceChange": "-8.00000000", // Absolute price change
"priceChangePercent": "-88.889", // Relative price change in percent
"weightedAvgPrice": "2.60427807", // QuoteVolume / Volume
"openPrice": "9.00000000",
"highPrice": "9.00000000",
"lowPrice": "1.00000000",
"lastPrice": "1.00000000",
"volume": "187.00000000",
"quoteVolume": "487.00000000", // Sum of (price * volume) for all trades
"openTime": 1641859200000, // Open time for ticker window
"closeTime": 1642031999999, // Current Time of the Request
"firstId": 0, // Trade IDs
"lastId": 60,
"count": 61 // Number of trades in the interval
}
OR
[
{
"symbol": "BTCUSDT",
"priceChange": "-154.13000000", // Absolute price change
"priceChangePercent": "-0.740", // Relative price change in percent
"weightedAvgPrice": "20677.46305250", // QuoteVolume / Volume
"openPrice": "20825.27000000",
"highPrice": "20972.46000000",
"lowPrice": "20327.92000000",
"lastPrice": "20671.14000000",
"volume": "72.65112300",
"quoteVolume": "1502240.91155513", // Sum of (price * volume) for all trades
"openTime": 1655432400000, // Open time for ticker window
"closeTime": 1655446835460, // Close time for ticker window
"firstId": 11147809, // Trade IDs
"lastId": 11149775,
"count": 1967 // Number of trades in the interval
},
{
"symbol": "BNBBTC",
"priceChange": "0.00008530",
"priceChangePercent": "0.823",
"weightedAvgPrice": "0.01043129",
"openPrice": "0.01036170",
"highPrice": "0.01049850",
"lowPrice": "0.01033870",
"lastPrice": "0.01044700",
"volume": "166.67000000",
"quoteVolume": "1.73858301",
"openTime": 1655432400000,
"closeTime": 1655446835460,
"firstId": 2351674,
"lastId": 2352034,
"count": 361
}
]
Response - MINI
{
"symbol": "LTCBTC",
"openPrice": "0.10000000",
"highPrice": "2.00000000",
"lowPrice": "0.10000000",
"lastPrice": "2.00000000",
"volume": "39.00000000",
"quoteVolume": "13.40000000", // Sum of (price * volume) for all trades
"openTime": 1656986580000, // Open time for ticker window
"closeTime": 1657001016795, // Close time for ticker window
"firstId": 0, // Trade IDs
"lastId": 34,
"count": 35 // Number of trades in the interval
}
OR
[
{
"symbol": "BNBBTC",
"openPrice": "0.10000000",
"highPrice": "2.00000000",
"lowPrice": "0.10000000",
"lastPrice": "2.00000000",
"volume": "39.00000000",
"quoteVolume": "13.40000000", // Sum of (price * volume) for all trades
"openTime": 1656986880000, // Open time for ticker window
"closeTime": 1657001297799, // Close time for ticker window
"firstId": 0, // Trade IDs
"lastId": 34,
"count": 35 // Number of trades in the interval
},
{
"symbol": "LTCBTC",
"openPrice": "0.07000000",
"highPrice": "0.07000000",
"lowPrice": "0.07000000",
"lastPrice": "0.07000000",
"volume": "33.00000000",
"quoteVolume": "2.31000000",
"openTime": 1656986880000,
"closeTime": 1657001297799,
"firstId": 0,
"lastId": 32,
"count": 33
}
]
GET /api/v3/ticker
Note: This endpoint is different from the GET /api/v3/ticker/24hr
endpoint.
The window used to compute statistics will be no more than 59999ms from the requested windowSize
.
openTime
for /api/v3/ticker
always starts on a minute, while the closeTime
is the current time of the request.
As such, the effective window will be up to 59999ms wider than windowSize
.
E.g. If the closeTime
is 1641287867099 (January 04, 2022 09:17:47:099 UTC) , and the windowSize
is 1d
. the openTime
will be: 1641201420000 (January 3, 2022, 09:17:00 UTC)
Weight:(IP)
4 for each requested symbol regardless of windowSize
The weight for this request will cap at 200 once the number of symbols
in the request is more than 50.
Parameters
Name | Type | Mandatory | Description | |
---|---|---|---|---|
symbol | STRING | YES | Either symbol or symbols must be provided. Examples of accepted format for the symbols parameter: ["BTCUSDT","BNBUSDT"] or %5B%22BTCUSDT%22,%22BNBUSDT%22%5D The maximum number of symbols allowed in a request is 100. |
|
symbols | ||||
windowSize | ENUM | NO | Defaults to 1d if no parameter provided. Supported windowSize values: 1m,2m....59m for minutes 1h, 2h....23h - for hours 1d...7d - for days Units cannot be combined (e.g. 1d2h is not allowed). | |
type | ENUM | NO | Supported values: FULL or MINI. If none provided, the default is FULL. |
Data Source: Database
Websocket Market Streams
- The base endpoint is: wss://stream.binance.com:9443 or wss://stream.binance.com:443
- Streams can be accessed either in a single raw stream or in a combined stream.
- Users can listen to multiple streams.
- Raw streams are accessed at /ws/<streamName>
- Combined streams are accessed at /stream?streams=<streamName1>/<streamName2>/<streamName3>
- Combined stream events are wrapped as follows: {"stream":"<streamName>","data":<rawPayload>}
- All symbols for streams are lowercase
- A single connection to stream.binance.com is only valid for 24 hours; expect to be disconnected at the 24 hour mark
- Websocket server will send a
ping frame
every 3 minutes.- If the websocket server does not receive a
pong frame
back from the connection within a 10 minute period, the connection will be disconnected. - When you receive a ping, you must send a pong with a copy of ping's payload as soon as possible.
- Unsolicited
pong frames
are allowed, but will not prevent disconnection. It is recommended that the payload for these pong frames are empty.
- If the websocket server does not receive a
- The base endpoint wss://data-stream.binance.vision can be subscribed to receive market data messages. User data stream is NOT available from this URL.
Live Subscribing/Unsubscribing to streams
- The following data can be sent through the websocket instance in order to subscribe/unsubscribe from streams. Examples can be seen below.
- The
id
is used as an identifier to uniquely identify the messages going back and forth. The following formats are accepted:- 64-bit signed integer
- alphanumeric strings; max length 36
null
- In the response, if the
result
received isnull
this means the request sent was a success.
Subscribe to a stream
Response
{
"result": null,
"id": 1
}
Request
{
"method": "SUBSCRIBE",
"params":
[
"btcusdt@aggTrade",
"btcusdt@depth"
],
"id": 1
}
Unsubscribe to a stream
Response
{
"result": null,
"id": 312
}
- Request
{
"method": "UNSUBSCRIBE",
"params":
[
"btcusdt@depth"
],
"id": 312
}
Listing Subscriptions
Response
{
"result": [
"btcusdt@aggTrade"
],
"id": 3
}
- Request
{
"method": "LIST_SUBSCRIPTIONS",
"id": 3
}
Setting Properties
Currently, the only property can be set is to set whether combined
stream payloads are enabled or not.
The combined property is set to false
when connecting using /ws/
("raw streams") and true
when connecting using /stream/
.
Response
{
"result": null,
"id": 5
}
- Request
{
"method": "SET_PROPERTY",
"params":
[
"combined",
true
],
"id": 5
}
Retrieving Properties
Response
{
"result": true, // Indicates that combined is set to true.
"id": 2
}
- Request
{
"method": "GET_PROPERTY",
"params":
[
"combined"
],
"id": 2
}
Error Messages
Error Message | Description |
---|---|
{"code": 0, "msg": "Unknown property", "id": '%s'} | Parameter used in the SET_PROPERTY or GET_PROPERTY was invalid |
{"code": 1, "msg": "Invalid value type: expected Boolean", "id": '%s'} | Value should only be true or false |
{"code": 2, "msg": "Invalid request: property name must be a string"} | Property name provided was invalid |
{"code": 2, "msg": "Invalid request: request ID must be an unsigned integer"} | Parameter id had to be provided or the value provided in the id parameter is an unsupported type |
{"code": 2, "msg": "Invalid request: unknown variant %s, expected one of SUBSCRIBE , UNSUBSCRIBE , LIST_SUBSCRIPTIONS , SET_PROPERTY , GET_PROPERTY at line 1 column 28"} |
Possible typo in the provided method or provided method was neither of the expected values |
{"code": 2, "msg": "Invalid request: too many parameters"} | Unnecessary parameters provided in the data |
{"code": 2, "msg": "Invalid request: property name must be a string"} | Property name was not provided |
{"code": 2, "msg": "Invalid request: missing field method at line 1 column 73"} |
method was not provided in the data |
{"code":3,"msg":"Invalid JSON: expected value at line %s column %s"} | JSON data sent has incorrect syntax. |
Aggregate Trade Streams
Payload:
{
"e": "aggTrade", // Event type
"E": 1672515782136, // Event time
"s": "BNBBTC", // Symbol
"a": 12345, // Aggregate trade ID
"p": "0.001", // Price
"q": "100", // Quantity
"f": 100, // First trade ID
"l": 105, // Last trade ID
"T": 1672515782136, // Trade time
"m": true, // Is the buyer the market maker?
"M": true // Ignore
}
The Aggregate Trade Streams push trade information that is aggregated for a single taker order.
Stream Name: <symbol>@aggTrade
Update Speed: Real-time
Trade Streams
Payload:
{
"e": "trade", // Event type
"E": 1672515782136, // Event time
"s": "BNBBTC", // Symbol
"t": 12345, // Trade ID
"p": "0.001", // Price
"q": "100", // Quantity
"T": 1672515782136, // Trade time
"m": true, // Is the buyer the market maker?
"M": true // Ignore
}
The Trade Streams push raw trade information; each trade has a unique buyer and seller.
Stream Name: <symbol>@trade
Update Speed: Real-time
Kline/Candlestick Streams for UTC
Payload:
{
"e": "kline", // Event type
"E": 1672515782136, // Event time
"s": "BNBBTC", // Symbol
"k": {
"t": 123400000, // Kline start time
"T": 123460000, // Kline close time
"s": "BNBBTC", // Symbol
"i": "1m", // Interval
"f": 100, // First trade ID
"L": 200, // Last trade ID
"o": "0.0010", // Open price
"c": "0.0020", // Close price
"h": "0.0025", // High price
"l": "0.0015", // Low price
"v": "1000", // Base asset volume
"n": 100, // Number of trades
"x": false, // Is this kline closed?
"q": "1.0000", // Quote asset volume
"V": "500", // Taker buy base asset volume
"Q": "0.500", // Taker buy quote asset volume
"B": "123456" // Ignore
}
}
The Kline/Candlestick Stream push updates to the current klines/candlestick every secondin UTC+0
timezone.
Stream Name: <symbol>@kline_<interval>
Update Speed: 1000ms for 1s
, 2000ms for the other intervals
Kline/Candlestick chart intervals:
s-> seconds; m -> minutes; h -> hours; d -> days; w -> weeks; M -> months
- 1s
- 1m
- 3m
- 5m
- 15m
- 30m
- 1h
- 2h
- 4h
- 6h
- 8h
- 12h
- 1d
- 3d
- 1w
- 1M
Kline/Candlestick Streams with timezone offset
Payload:
{
"e": "kline", // Event type
"E": 1672515782136, // Event time
"s": "BNBBTC", // Symbol
"k": {
"t": 1672515780000, // Kline start time
"T": 1672515839999, // Kline close time
"s": "BNBBTC", // Symbol
"i": "1m", // Interval
"f": 100, // First trade ID
"L": 200, // Last trade ID
"o": "0.0010", // Open price
"c": "0.0020", // Close price
"h": "0.0025", // High price
"l": "0.0015", // Low price
"v": "1000", // Base asset volume
"n": 100, // Number of trades
"x": false, // Is this kline closed?
"q": "1.0000", // Quote asset volume
"V": "500", // Taker buy base asset volume
"Q": "0.500", // Taker buy quote asset volume
"B": "123456" // Ignore
}
}
The Kline/Candlestick Stream push updates to the current klines/candlestick every second in UTC+8
timezone.
UTC+8 timezone offset:
- Kline intervals open and close in the
UTC+8
timezone. For example the1d
klines will open at the beginning of theUTC+8
day, and close at the end of theUTC+8
day. - Note that
E
(event time),t
(start time) andT
(close time) in the payload are Unix timestamps, which are always interpreted in UTC.
Stream Name: <symbol>@kline_<interval>@+08:00
Update Speed: 1000ms for 1s
, 2000ms for the other intervals
Supported intervals: See Kline/Candlestick chart intervals
Individual Symbol Mini Ticker Stream
Payload:
{
"e": "24hrMiniTicker", // Event type
"E": 1672515782136, // Event time
"s": "BNBBTC", // Symbol
"c": "0.0025", // Close price
"o": "0.0010", // Open price
"h": "0.0025", // High price
"l": "0.0010", // Low price
"v": "10000", // Total traded base asset volume
"q": "18" // Total traded quote asset volume
}
24hr rolling window mini-ticker statistics. These are NOT the statistics of the UTC day, but a 24hr rolling window for the previous 24hrs.
Stream Name: <symbol>@miniTicker
Update Speed: 1000ms
All Market Mini Tickers Stream
Payload:
[
{
// Same as <symbol>@miniTicker payload
}
]
24hr rolling window mini-ticker statistics for all symbols that changed in an array. These are NOT the statistics of the UTC day, but a 24hr rolling window for the previous 24hrs. Note that only tickers that have changed will be present in the array.
Stream Name: !miniTicker@arr
Update Speed: 1000ms
Individual Symbol Ticker Streams
Payload:
{
"e": "24hrTicker", // Event type
"E": 1672515782136, // Event time
"s": "BNBBTC", // Symbol
"p": "0.0015", // Price change
"P": "250.00", // Price change percent
"w": "0.0018", // Weighted average price
"x": "0.0009", // First trade(F)-1 price (first trade before the 24hr rolling window)
"c": "0.0025", // Last price
"Q": "10", // Last quantity
"b": "0.0024", // Best bid price
"B": "10", // Best bid quantity
"a": "0.0026", // Best ask price
"A": "100", // Best ask quantity
"o": "0.0010", // Open price
"h": "0.0025", // High price
"l": "0.0010", // Low price
"v": "10000", // Total traded base asset volume
"q": "18", // Total traded quote asset volume
"O": 0, // Statistics open time
"C": 86400000, // Statistics close time
"F": 0, // First trade ID
"L": 18150, // Last trade Id
"n": 18151 // Total number of trades
}
24hr rolling window ticker statistics for a single symbol. These are NOT the statistics of the UTC day, but a 24hr rolling window for the previous 24hrs.
Stream Name: <symbol>@ticker
Update Speed: 1000ms
Average Price
Payload:
{
"e": "avgPrice", // Event type
"E": 1693907033000, // Event time
"s": "BTCUSDT", // Symbol
"i": "5m", // Average price interval
"w": "25776.86000000", // Average price
"T": 1693907032213 // Last trade time
}
Average price streams push changes in the average price over a fixed time interval.
Stream Name: <symbol>@avgPrice
Update Speed: 1000ms
All Market Tickers Stream
Payload:
[
{
// Same as <symbol>@ticker payload
}
]
24hr rolling window ticker statistics for all symbols that changed in an array. These are NOT the statistics of the UTC day, but a 24hr rolling window for the previous 24hrs. Note that only tickers that have changed will be present in the array.
Stream Name: !ticker@arr
Update Speed: 1000ms
Individual Symbol Rolling Window Statistics Streams
Payload:
{
"e": "1hTicker", // Event type
"E": 1672515782136, // Event time
"s": "BNBBTC", // Symbol
"p": "0.0015", // Price change
"P": "250.00", // Price change percent
"o": "0.0010", // Open price
"h": "0.0025", // High price
"l": "0.0010", // Low price
"c": "0.0025", // Last price
"w": "0.0018", // Weighted average price
"v": "10000", // Total traded base asset volume
"q": "18", // Total traded quote asset volume
"O": 0, // Statistics open time
"C": 86400000, // Statistics close time
"F": 0, // First trade ID
"L": 18150, // Last trade Id
"n": 18151 // Total number of trades
}
Rolling window ticker statistics for a single symbol, computed over multiple windows.
Stream Name: <symbol>@ticker_<window_size>
Window Sizes: 1h,4h,1d
Update Speed: 1000ms
Note: This stream is different from the <symbol>@ticker
stream.
The open time O
always starts on a minute, while the closing time C
is the current time of the update.
As such, the effective window might be up to 59999ms wider that <window_size>
.
All Market Rolling Window Statistics Streams
Payload:
[
{
// Same as <symbol>@ticker_<window-size> payload,
// one for each symbol updated within the interval.
}
]
Rolling window ticker statistics for all market symbols, computed over multiple windows. Note that only tickers that have changed will be present in the array.
Stream Name: !ticker_<window-size>@arr
Window Size: 1h,4h,1d
Update Speed: 1000ms
Individual Symbol Book Ticker Streams
Payload:
{
"u":400900217, // order book updateId
"s":"BNBUSDT", // symbol
"b":"25.35190000", // best bid price
"B":"31.21000000", // best bid qty
"a":"25.36520000", // best ask price
"A":"40.66000000" // best ask qty
}
Pushes any update to the best bid or ask's price or quantity in real-time for a specified symbol.
Multiple <symbol>@bookTicker
streams can be subscribed to over one connection.
Stream Name: <symbol>@bookTicker
Update Speed: 1ms
Partial Book Depth Streams
Payload:
{
"lastUpdateId": 160, // Last update ID
"bids": [ // Bids to be updated
[
"0.0024", // Price level to be updated
"10" // Quantity
]
],
"asks": [ // Asks to be updated
[
"0.0026", // Price level to be updated
"100" // Quantity
]
]
}
Top
Stream Names: <symbol>@depth<levels>
OR <symbol>@depth<levels>@100ms
.
Update Speed: 1000ms or 100ms
Diff. Depth Stream
Payload:
{
"e": "depthUpdate", // Event type
"E": 1672515782136, // Event time
"s": "BNBBTC", // Symbol
"U": 157, // First update ID in event
"u": 160, // Final update ID in event
"b": [ // Bids to be updated
[
"0.0024", // Price level to be updated
"10" // Quantity
]
],
"a": [ // Asks to be updated
[
"0.0026", // Price level to be updated
"100" // Quantity
]
]
}
Stream Name: <symbol>@depth
OR <symbol>@depth@100ms
Update Speed: 1000ms or 100ms
Order book price and quantity depth updates used to locally manage an order book.
How to manage a local order book correctly
- Open a stream to wss://stream.binance.com:9443/ws/bnbbtc@depth.
- Buffer the events you receive from the stream.
- Get a depth snapshot from https://api.binance.com/api/v3/depth?symbol=BNBBTC&limit=1000 .
- Drop any event where
u
is <=lastUpdateId
in the snapshot. - The first processed event should have
U
<=lastUpdateId
+1 ANDu
>=lastUpdateId
+1. - While listening to the stream, each new event's
U
should be equal to the previous event'su
+1. - The data in each event is the absolute quantity for a price level.
- If the quantity is 0, remove the price level.
- Receiving an event that removes a price level that is not in your local order book can happen and is normal.
Note: Due to depth snapshots having a limit on the number of price levels, a price level outside of the initial snapshot that doesn't have a quantity change won't have an update in the Diff. Depth Stream. Consequently, those price levels will not be visible in the local order book even when applying all updates from the Diff. Depth Stream correctly and cause the local order book to have some slight differences with the real order book. However, for most use cases the depth limit of 5000 is enough to understand the market and trade effectively.
Spot Trading Endpoints
Test New Order (TRADE)
Response:
{}
OR
{
"standardCommissionForOrder": { //Standard commission rates on trades from the order.
"maker": "0.00000112",
"taker": "0.00000114",
},
"taxCommissionForOrder": { //Tax commission rates for trades from the order.
"maker": "0.00000112",
"taker": "0.00000114",
},
"discount": { //Discount on standard commissions when paying in BNB.
"enabledForAccount": true,
"enabledForSymbol": true,
"discountAsset": "BNB",
"discount": "0.25000000" //Standard commission is reduced by this rate when paying commission in BNB.
}
}
POST /api/v3/order/test
Test new order creation and signature/recvWindow long. Creates and validates a new order but does not send it into the matching engine.
Weight:
Condition | Request Weight |
---|---|
Without computeCommissionRates |
1 |
With computeCommissionRates |
20 |
Parameters:
In addition to all parameters accepted by POST /api/v3/order
,
the following optional parameters are also accepted:
Name | Type | Mandatory | Description |
---|---|---|---|
computeCommissionRates | BOOLEAN | NO | Default: false |
Data Source: Memory
New Order (TRADE)
Response ACK:
{
"symbol": "BTCUSDT",
"orderId": 28,
"orderListId": -1, //Unless an order list, value will be -1
"clientOrderId": "6gCrw2kRUAF9CvJDGP16IP",
"transactTime": 1507725176595
}
Response RESULT:
{
"symbol": "BTCUSDT",
"orderId": 28,
"orderListId": -1, //Unless an order list, value will be -1
"clientOrderId": "6gCrw2kRUAF9CvJDGP16IP",
"transactTime": 1507725176595,
"price": "0.00000000",
"origQty": "10.00000000",
"executedQty": "10.00000000",
"cummulativeQuoteQty": "10.00000000",
"status": "FILLED",
"timeInForce": "GTC",
"type": "MARKET",
"side": "SELL",
"workingTime": 1507725176595,
"selfTradePreventionMode": "NONE"
}
Response FULL:
{
"symbol": "BTCUSDT",
"orderId": 28,
"orderListId": -1, //Unless an order list, value will be -1
"clientOrderId": "6gCrw2kRUAF9CvJDGP16IP",
"transactTime": 1507725176595,
"price": "0.00000000",
"origQty": "10.00000000",
"executedQty": "10.00000000",
"cummulativeQuoteQty": "10.00000000",
"status": "FILLED",
"timeInForce": "GTC",
"type": "MARKET",
"side": "SELL",
"workingTime": 1507725176595,
"selfTradePreventionMode": "NONE",
"fills": [
{
"price": "4000.00000000",
"qty": "1.00000000",
"commission": "4.00000000",
"commissionAsset": "USDT",
"tradeId": 56
},
{
"price": "3999.00000000",
"qty": "5.00000000",
"commission": "19.99500000",
"commissionAsset": "USDT",
"tradeId": 57
},
{
"price": "3998.00000000",
"qty": "2.00000000",
"commission": "7.99600000",
"commissionAsset": "USDT",
"tradeId": 58
},
{
"price": "3997.00000000",
"qty": "1.00000000",
"commission": "3.99700000",
"commissionAsset": "USDT",
"tradeId": 59
},
{
"price": "3995.00000000",
"qty": "1.00000000",
"commission": "3.99500000",
"commissionAsset": "USDT",
"tradeId": 60
}
]
}
POST /api/v3/order
Send in a new order.
Weight(UID): 1 Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
side | ENUM | YES | |
type | ENUM | YES | |
timeInForce | ENUM | NO | |
quantity | DECIMAL | NO | |
quoteOrderQty | DECIMAL | NO | |
price | DECIMAL | NO | |
newClientOrderId | STRING | NO | A unique id among open orders. Automatically generated if not sent. |
strategyId | INT | NO | |
strategyType | INT | NO | The value cannot be less than 1000000 . |
stopPrice | DECIMAL | NO | Used with STOP_LOSS , STOP_LOSS_LIMIT , TAKE_PROFIT , and TAKE_PROFIT_LIMIT orders. |
trailingDelta | LONG | NO | Used with STOP_LOSS , STOP_LOSS_LIMIT , TAKE_PROFIT , and TAKE_PROFIT_LIMIT orders. For more details on SPOT implementation on trailing stops, please refer to Trailing Stop FAQ |
icebergQty | DECIMAL | NO | Used with LIMIT , STOP_LOSS_LIMIT , and TAKE_PROFIT_LIMIT to create an iceberg order. |
newOrderRespType | ENUM | NO | Set the response JSON. ACK , RESULT , or FULL ; MARKET and LIMIT order types default to FULL , all other orders default to ACK . |
selfTradePreventionMode | ENUM | NO | The allowed enums is dependent on what is configured on the symbol. The possible supported values are EXPIRE_TAKER , EXPIRE_MAKER , EXPIRE_BOTH , NONE . |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Additional mandatory parameters based on type
:
Type | Additional mandatory parameters |
---|---|
LIMIT |
timeInForce , quantity , price |
MARKET |
quantity or quoteOrderQty |
STOP_LOSS |
quantity , stopPrice or trailingDelta |
STOP_LOSS_LIMIT |
timeInForce , quantity , price , stopPrice or trailingDelta |
TAKE_PROFIT |
quantity , stopPrice or trailingDelta |
TAKE_PROFIT_LIMIT |
timeInForce , quantity , price , stopPrice or trailingDelta |
LIMIT_MAKER |
quantity , price |
Other info:
LIMIT_MAKER
areLIMIT
orders that will be rejected if they would immediately match and trade as a taker.STOP_LOSS
andTAKE_PROFIT
will execute aMARKET
order when thestopPrice
is reached.- Any
LIMIT
orLIMIT_MAKER
type order can be made an iceberg order by sending anicebergQty
. - Any order with an
icebergQty
MUST havetimeInForce
set toGTC
. MARKET
orders using thequantity
field specifies the amount of thebase asset
the user wants to buy or sell at the market price.- For example, sending a
MARKET
order on BTCUSDT will specify how much BTC the user is buying or selling.
- For example, sending a
MARKET
orders usingquoteOrderQty
specifies the amount the user wants to spend (when buying) or receive (when selling) thequote
asset; the correctquantity
will be determined based on the market liquidity andquoteOrderQty
.- Using BTCUSDT as an example:
- On the
BUY
side, the order will buy as many BTC asquoteOrderQty
USDT can. - On the
SELL
side, the order will sell as much BTC needed to receivequoteOrderQty
USDT.
- On the
- Using BTCUSDT as an example:
MARKET
orders usingquoteOrderQty
will not breakLOT_SIZE
filter rules; the order will execute aquantity
that will have the notional value as close as possible toquoteOrderQty
.- same
newClientOrderId
can be accepted only when the previous one is filled, otherwise the order will be rejected. - For
STOP_LOSS
,STOP_LOSS_LIMIT
,TAKE_PROFIT_LIMIT
andTAKE_PROFIT
orders,trailingDelta
can be combined withstopPrice
.
Trigger order price rules against market price for both MARKET and LIMIT versions:
- Price above market price:
STOP_LOSS
BUY
,TAKE_PROFIT
SELL
- Price below market price:
STOP_LOSS
SELL
,TAKE_PROFIT
BUY
Data Source: Matching Engine
Conditional fields in Order Responses
There are fields in the order responses (e.g. order placement, order query, order cancellation) that appear only if certain conditions are met.
These fields can apply to Order lists.
The fields are listed below:
Field | Description | Visibility conditions | Examples |
---|---|---|---|
icebergQty |
Quantity for the iceberg order | Appears only if the parameter icebergQty was sent in the request. |
"icebergQty": "0.00000000" |
preventedMatchId |
When used in combination with symbol , can be used to query a prevented match. |
Appears only if the order expired due to STP. | "preventedMatchId": 0 |
preventedQuantity |
Order quantity that expired due to STP | Appears only if the order expired due to STP. | "preventedQuantity": "1.200000" |
stopPrice |
Price when the algorithmic order will be triggered | Appears for STOP_LOSS . TAKE_PROFIT , STOP_LOSS_LIMIT and TAKE_PROFIT_LIMIT orders. |
"stopPrice": "23500.00000000" |
strategyId |
Can be used to label an order that's part of an order strategy. | Appears if the parameter was populated in the request. | "strategyId": 37463720 |
strategyType |
Can be used to label an order that is using an order strategy. | Appears if the parameter was populated in the request. | "strategyType": 1000000 |
trailingDelta |
Delta price change required before order activation | Appears for Trailing Stop Orders. | "trailingDelta": 10 |
trailingTime |
Time when the trailing order is now active and tracking price changes | Appears only for Trailing Stop Orders. | "trailingTime": -1 |
Cancel Order (TRADE)
Response:
{
"symbol": "LTCBTC",
"origClientOrderId": "myOrder1",
"orderId": 4,
"orderListId": -1, //Unless part of an order list, the value will always be -1.
"clientOrderId": "cancelMyOrder1",
"transactTime": 1684804350068,
"price": "2.00000000",
"origQty": "1.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"selfTradePreventionMode": "NONE"
}
DELETE /api/v3/order
Cancel an active order.
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
orderId | LONG | NO | |
origClientOrderId | STRING | NO | |
newClientOrderId | STRING | NO | Used to uniquely identify this cancel. Automatically generated by default. |
cancelRestrictions | ENUM | NO | Supported values: ONLY_NEW - Cancel will succeed if the order status is NEW .ONLY_PARTIALLY_FILLED - Cancel will succeed if order status is PARTIALLY_FILLED . |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Either orderId
or origClientOrderId
must be sent.
If both orderId
and origClientOrderId
are provided, orderId
takes precedence.
Data Source: Matching Engine
Regarding cancelRestrictions
- If the
cancelRestrictions
value is not any of the supported values, the error will be:{"code": -1145,"msg": "Invalid cancelRestrictions"}
- If the order did not pass the conditions for
cancelRestrictions
, the error will be:{"code": -2011,"msg": "Order was not canceled due to cancel restrictions."}
Note: The payload sample does not show all fields that can appear. Please refer to Conditional fields in Order Responses.
Cancel all Open Orders on a Symbol (TRADE)
Response:
[
{
"symbol": "BTCUSDT",
"origClientOrderId": "E6APeyTJvkMvLMYMqu1KQ4",
"orderId": 11,
"orderListId": -1,
"clientOrderId": "pXLV6Hz6mprAcVYpVMTGgx",
"transactTime": 1684804350068,
"price": "0.089853",
"origQty": "0.178622",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"selfTradePreventionMode": "NONE"
},
{
"symbol": "BTCUSDT",
"origClientOrderId": "A3EF2HCwxgZPFMrfwbgrhv",
"orderId": 13,
"orderListId": -1,
"clientOrderId": "pXLV6Hz6mprAcVYpVMTGgx",
"transactTime": 1684804350069,
"price": "0.090430",
"origQty": "0.178622",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"selfTradePreventionMode": "NONE"
},
{
"orderListId": 1929,
"contingencyType": "OCO",
"listStatusType": "ALL_DONE",
"listOrderStatus": "ALL_DONE",
"listClientOrderId": "2inzWQdDvZLHbbAmAozX2N",
"transactionTime": 1585230948299,
"symbol": "BTCUSDT",
"orders": [
{
"symbol": "BTCUSDT",
"orderId": 20,
"clientOrderId": "CwOOIPHSmYywx6jZX77TdL"
},
{
"symbol": "BTCUSDT",
"orderId": 21,
"clientOrderId": "461cPg51vQjV3zIMOXNz39"
}
],
"orderReports": [
{
"symbol": "BTCUSDT",
"origClientOrderId": "CwOOIPHSmYywx6jZX77TdL",
"orderId": 20,
"orderListId": 1929,
"clientOrderId": "pXLV6Hz6mprAcVYpVMTGgx",
"transactTime": 1688005070874,
"price": "0.668611",
"origQty": "0.690354",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "STOP_LOSS_LIMIT",
"side": "BUY",
"stopPrice": "0.378131",
"icebergQty": "0.017083",
"selfTradePreventionMode": "NONE"
},
{
"symbol": "BTCUSDT",
"origClientOrderId": "461cPg51vQjV3zIMOXNz39",
"orderId": 21,
"orderListId": 1929,
"clientOrderId": "pXLV6Hz6mprAcVYpVMTGgx",
"transactTime": 1688005070874,
"price": "0.008791",
"origQty": "0.690354",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT_MAKER",
"side": "BUY",
"icebergQty": "0.639962",
"selfTradePreventionMode": "NONE"
}
]
}
]
DELETE /api/v3/openOrders
Cancels all active orders on a symbol.
This includes orders that are part of an order list.
Weight(IP): 1
Parameters
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Data Source: Matching Engine
Note: The payload sample does not show all fields that can appear. Please refer to Conditional fields in Order Responses.
Query Order (USER_DATA)
Response:
{
"symbol": "LTCBTC",
"orderId": 1,
"orderListId": -1, //Unless an order list, value will be -1
"clientOrderId": "myOrder1",
"price": "0.1",
"origQty": "1.0",
"executedQty": "0.0",
"cummulativeQuoteQty": "0.0",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"stopPrice": "0.0",
"icebergQty": "0.0",
"time": 1499827319559,
"updateTime": 1499827319559,
"isWorking": true,
"workingTime":1499827319559,
"origQuoteOrderQty": "0.000000",
"selfTradePreventionMode": "NONE"
}
GET /api/v3/order
Check an order's status.
Weight(IP): 4
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
orderId | LONG | NO | |
origClientOrderId | STRING | NO | |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Notes:
- Either
orderId
ororigClientOrderId
must be sent. - For some historical orders
cummulativeQuoteQty
will be < 0, meaning the data is not available at this time. - The payload sample does not show all fields that can appear. Please refer to Conditional fields in Order Responses.
Data Source: Memory => Database
Cancel an Existing Order and Send a New Order (TRADE)
Response SUCCESS and account has not exceeded the order rate limit:
//Both the cancel order placement and new order placement succeeded.
{
"cancelResult": "SUCCESS",
"newOrderResult": "SUCCESS",
"cancelResponse": {
"symbol": "BTCUSDT",
"origClientOrderId": "DnLo3vTAQcjha43lAZhZ0y",
"orderId": 9,
"orderListId": -1,
"clientOrderId": "osxN3JXAtJvKvCqGeMWMVR",
"transactTime": 1684804350068,
"price": "0.01000000",
"origQty": "0.000100",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "SELL",
"selfTradePreventionMode": "NONE"
},
"newOrderResponse": {
"symbol": "BTCUSDT",
"orderId": 10,
"orderListId": -1,
"clientOrderId": "wOceeeOzNORyLiQfw7jd8S",
"transactTime": 1652928801803,
"price": "0.02000000",
"origQty": "0.040000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"workingTime": 1669277163808,
"fills": [],
"selfTradePreventionMode": "NONE"
}
}
Response when Cancel Order Fails with STOP_ON_FAILURE:
{
"code": -2022,
"msg": "Order cancel-replace failed.",
"data": {
"cancelResult": "FAILURE",
"newOrderResult": "NOT_ATTEMPTED",
"cancelResponse": {
"code": -2011,
"msg": "Unknown order sent."
},
"newOrderResponse": null
}
}
Response when Cancel Order Succeeds but New Order Placement Fails and account has not exceeded the order rate limit:
{
"code": -2021,
"msg": "Order cancel-replace partially failed.",
"data": {
"cancelResult": "SUCCESS",
"newOrderResult": "FAILURE",
"cancelResponse": {
"symbol": "BTCUSDT",
"origClientOrderId": "86M8erehfExV8z2RC8Zo8k",
"orderId": 3,
"orderListId": -1,
"clientOrderId": "G1kLo6aDv2KGNTFcjfTSFq",
"transactTime": 1684804350068,
"price": "0.006123",
"origQty": "10000.000000",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT_MAKER",
"side": "SELL",
"selfTradePreventionMode": "NONE"
},
"newOrderResponse": {
"code": -2010,
"msg": "Order would immediately match and take."
}
}
}
Response when Cancel Order fails with ALLOW_FAILURE and account has not exceeded the order rate limit:
{
"code": -2021,
"msg": "Order cancel-replace partially failed.",
"data": {
"cancelResult": "FAILURE",
"newOrderResult": "SUCCESS",
"cancelResponse": {
"code": -2011,
"msg": "Unknown order sent."
},
"newOrderResponse": {
"symbol": "BTCUSDT",
"orderId": 11,
"orderListId": -1,
"clientOrderId": "pfojJMg6IMNDKuJqDxvoxN",
"transactTime": 1648540168818
}
}
}
Response when both Cancel Order and New Order Placement fail using
cancelReplaceMode=ALLOW_FAILURE
and account has not exceeded the order rate limit:
{
"code": -2022,
"msg": "Order cancel-replace failed.",
"data": {
"cancelResult": "FAILURE",
"newOrderResult": "FAILURE",
"cancelResponse": {
"code": -2011,
"msg": "Unknown order sent."
},
"newOrderResponse": {
"code": -2010,
"msg": "Order would immediately match and take."
}
}
}
Response when using
orderRateLimitExceededMode=DO_NOTHING
and account's order rate limit has been exceeded:
{
"code": -1015,
"msg": "Too many new orders; current limit is 1 orders per 10 SECOND."
}
Response when using
orderRateLimitExceededMode=CANCEL_ONLY
and account's order rate limit has been exceeded:
{
"code": -2021,
"msg": "Order cancel-replace partially failed.",
"data": {
"cancelResult": "SUCCESS",
"newOrderResult": "FAILURE",
"cancelResponse": {
"symbol": "LTCBNB",
"origClientOrderId": "GKt5zzfOxRDSQLveDYCTkc",
"orderId": 64,
"orderListId": -1,
"clientOrderId": "loehOJF3FjoreUBDmv739R",
"transactTime": 1715779007228,
"price": "1.00",
"origQty": "10.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "SELL",
"selfTradePreventionMode": "NONE"
},
"newOrderResponse": {
"code": -1015,
"msg": "Too many new orders; current limit is 1 orders per 10 SECOND."
}
}
}
POST /api/v3/order/cancelReplace
Cancels an existing order and places a new order on the same symbol.
Filters and Order Count are evaluated before the processing of the cancellation and order placement occurs.
A new order that was not attempted (i.e. when newOrderResult: NOT_ATTEMPTED
), will still increase the order count by 1.
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
side | ENUM | YES | |
type | ENUM | YES | |
cancelReplaceMode | ENUM | YES | The allowed values are: STOP_ON_FAILURE - If the cancel request fails, the new order placement will not be attempted. ALLOW_FAILURE - new order placement will be attempted even if cancel request fails. |
timeInForce | ENUM | NO | |
quantity | DECIMAL | NO | |
quoteOrderQty | DECIMAL | NO | |
price | DECIMAL | NO | |
cancelNewClientOrderId | STRING | NO | Used to uniquely identify this cancel. Automatically generated by default. |
cancelOrigClientOrderId | STRING | NO | Either the cancelOrigClientOrderId or cancelOrderId must be provided. If both are provided, cancelOrderId takes precedence. |
cancelOrderId | LONG | NO | Either the cancelOrigClientOrderId or cancelOrderId must be provided. If both are provided, cancelOrderId takes precedence. |
newClientOrderId | STRING | NO | Used to identify the new order. |
strategyId | INT | NO | |
strategyType | INT | NO | The value cannot be less than 1000000 . |
stopPrice | DECIMAL | NO | |
trailingDelta | LONG | NO | |
icebergQty | DECIMAL | NO | |
newOrderRespType | ENUM | NO | Allowed values: ACK , RESULT , FULL MARKET and LIMIT orders types default to FULL ; all other orders default to ACK |
selfTradePreventionMode | ENUM | NO | The allowed enums is dependent on what is configured on the symbol. The possible supported values are EXPIRE_TAKER , EXPIRE_MAKER , EXPIRE_BOTH , NONE . |
cancelRestrictions | ENUM | NO | Supported values: ONLY_NEW - Cancel will succeed if the order status is NEW .ONLY_PARTIALLY_FILLED - Cancel will succeed if order status is PARTIALLY_FILLED . For more information please refer to Regarding cancelRestrictions |
orderRateLimitExceededMode | ENUM | No | Supported values: DO_NOTHING (default)- will only attempt to cancel the order if account has not exceeded the unfilled order rate limitCANCEL_ONLY - will always cancel the order |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Similar to POST /api/v3/order
, additional mandatory parameters are determined by type
.
Response format varies depending on whether the processing of the message succeeded, partially succeeded, or failed.
Data Source: Matching Engine
Request | Response | ||||
---|---|---|---|---|---|
cancelReplaceMode |
orderRateLimitExceededMode |
Order Count Usage | cancelResult |
newOrderResult |
status |
STOP_ON_FAILURE |
DO_NOTHING |
Within Limits | ✅ SUCCESS |
✅ SUCCESS |
200 |
❌ FAILURE |
➖ NOT_ATTEMPTED |
400 |
|||
✅ SUCCESS |
❌ FAILURE |
409 |
|||
Exceeds Limits | ✅ SUCCESS |
✅ SUCCESS |
N/A | ||
❌ FAILURE |
➖ NOT_ATTEMPTED |
N/A | |||
✅ SUCCESS |
❌ FAILURE |
N/A | |||
CANCEL_ONLY |
Within Limits | ✅ SUCCESS |
✅ SUCCESS |
200 |
|
❌ FAILURE |
➖ NOT_ATTEMPTED |
400 |
|||
✅ SUCCESS |
❌ FAILURE |
409 |
|||
Exceeds Limits | ❌ FAILURE |
➖ NOT_ATTEMPTED |
429 |
||
✅ SUCCESS |
❌ FAILURE |
429 |
|||
ALLOW_FAILURE |
DO_NOTHING |
Within Limits | ✅ SUCCESS |
✅ SUCCESS |
200 |
❌ FAILURE |
❌ FAILURE |
400 |
|||
❌ FAILURE |
✅ SUCCESS |
409 |
|||
✅ SUCCESS |
❌ FAILURE |
409 |
|||
Exceeds Limits | ✅ SUCCESS |
✅ SUCCESS |
N/A | ||
❌ FAILURE |
❌ FAILURE |
N/A | |||
❌ FAILURE |
✅ SUCCESS |
N/A | |||
✅ SUCCESS |
❌ FAILURE |
N/A | |||
CANCEL_ONLY |
Within Limits | ✅ SUCCESS |
✅ SUCCESS |
200 |
|
❌ FAILURE |
❌ FAILURE |
400 |
|||
❌ FAILURE |
✅ SUCCESS |
409 |
|||
✅ SUCCESS |
❌ FAILURE |
409 |
|||
Exceeds Limits | ✅ SUCCESS |
✅ SUCCESS |
200 |
||
❌ FAILURE |
❌ FAILURE |
400 |
|||
❌ FAILURE |
✅ SUCCESS |
N/A | |||
✅ SUCCESS |
❌ FAILURE |
409 |
Note: The payload sample does not show all fields that can appear. Please refer to Conditional fields in Order Responses.
Current Open Orders (USER_DATA)
Response:
[
{
"symbol": "LTCBTC",
"orderId": 1,
"orderListId": -1, //Unless an order list, the value will always be -1
"clientOrderId": "myOrder1",
"price": "0.1",
"origQty": "1.0",
"executedQty": "0.0",
"cummulativeQuoteQty": "0.0",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"stopPrice": "0.0",
"icebergQty": "0.0",
"time": 1499827319559,
"updateTime": 1499827319559,
"isWorking": true,
"workingTime": 1499827319559,
"origQuoteOrderQty": "0.000000",
"selfTradePreventionMode": "NONE"
}
]
GET /api/v3/openOrders
Get all open orders on a symbol. Careful when accessing this with no symbol.
Weight(IP): 6 for a single symbol; 80 when the symbol parameter is omitted;
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | NO | |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- If the symbol is not sent, orders for all symbols will be returned in an array.
Data Source: Memory => Database
Note: The payload sample does not show all fields that can appear. Please refer to Conditional fields in Order Responses.
All Orders (USER_DATA)
Response:
[
{
"symbol": "LTCBTC",
"orderId": 1,
"orderListId": -1, //Unless an order list, the value will always be -1
"clientOrderId": "myOrder1",
"price": "0.1",
"origQty": "1.0",
"executedQty": "0.0",
"cummulativeQuoteQty": "0.0",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"stopPrice": "0.0",
"icebergQty": "0.0",
"time": 1499827319559,
"updateTime": 1499827319559,
"isWorking": true,
"origQuoteOrderQty": "0.000000",
"workingTime": 1499827319559,
"selfTradePreventionMode": "NONE"
}
]
GET /api/v3/allOrders
Get all account orders; active, canceled, or filled.
Weight(IP): 20
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
orderId | LONG | NO | |
startTime | LONG | NO | |
endTime | LONG | NO | |
limit | INT | NO | Default 500; max 1000. |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Notes:
- If
orderId
is set, it will get orders >= thatorderId
. Otherwise most recent orders are returned. - For some historical orders
cummulativeQuoteQty
will be < 0, meaning the data is not available at this time. - If
startTime
and/orendTime
provided,orderId
is not required. - The payload sample does not show all fields that can appear. Please refer to Conditional fields in Order Responses.
Data Source: Database
New OCO - Deprecated (TRADE)
Response:
{
"orderListId": 0,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "JYVpp3F0f5CAG15DhtrqLp",
"transactionTime": 1563417480525,
"symbol": "LTCBTC",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 2,
"clientOrderId": "Kk7sqHb9J6mJWTMDVW7Vos"
},
{
"symbol": "LTCBTC",
"orderId": 3,
"clientOrderId": "xTXKaGYd4bluPVp78IVRvl"
}
],
"orderReports": [
{
"symbol": "LTCBTC",
"orderId": 2,
"orderListId": 0,
"clientOrderId": "Kk7sqHb9J6mJWTMDVW7Vos",
"transactTime": 1563417480525,
"price": "0.000000",
"origQty": "0.624363",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "STOP_LOSS",
"side": "BUY",
"stopPrice": "0.960664",
"workingTime": -1,
"selfTradePreventionMode": "NONE"
},
{
"symbol": "LTCBTC",
"orderId": 3,
"orderListId": 0,
"clientOrderId": "xTXKaGYd4bluPVp78IVRvl",
"transactTime": 1563417480525,
"price": "0.036435",
"origQty": "0.624363",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT_MAKER",
"side": "BUY",
"workingTime": 1563417480525,
"selfTradePreventionMode": "NONE"
}
]
}
POST /api/v3/order/oco
Send in a new OCO
Weight(UID): 2 Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
listClientOrderId | STRING | NO | A unique Id for the entire orderList |
side | ENUM | YES | |
quantity | DECIMAL | YES | |
limitClientOrderId | STRING | NO | A unique Id for the limit order |
limitStrategyId | INT | NO | |
limitStrategyType | INT | NO | The value cannot be less than 1000000 . |
price | DECIMAL | YES | |
limitIcebergQty | DECIMAL | NO | |
trailingDelta | LONG | NO | |
stopClientOrderId | STRING | NO | A unique Id for the stop loss/stop loss limit leg |
stopPrice | DECIMAL | YES | |
stopStrategyId | INT | NO | |
stopStrategyType | INT | NO | The value cannot be less than 1000000 . |
stopLimitPrice | DECIMAL | NO | If provided, stopLimitTimeInForce is required. |
stopIcebergQty | DECIMAL | NO | |
stopLimitTimeInForce | ENUM | NO | Valid values are GTC /FOK /IOC |
newOrderRespType | ENUM | NO | Set the response JSON. |
selfTradePreventionMode | ENUM | NO | The allowed enums is dependent on what is configured on the symbol. The possible supported values are EXPIRE_TAKER , EXPIRE_MAKER , EXPIRE_BOTH , NONE . |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Other Info:
- Price Restrictions:
SELL
: Limit Price > Last Price > Stop PriceBUY
: Limit Price < Last Price < Stop Price
- Quantity Restrictions:
- Both legs must have the same quantity.
ICEBERG
quantities however do not have to be the same
OCO
adds 2 orders to the unfilled order count,EXCHANGE_MAX_ORDERS
filter and theMAX_NUM_ORDERS
filter.
Data Source: Matching Engine
New Order List - OCO (TRADE)
Response:
{
"orderListId": 1,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "lH1YDkuQKWiXVXHPSKYEIp",
"transactionTime": 1710485608839,
"symbol": "LTCBTC",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 10,
"clientOrderId": "44nZvqpemY7sVYgPYbvPih"
},
{
"symbol": "LTCBTC",
"orderId": 11,
"clientOrderId": "NuMp0nVYnciDiFmVqfpBqK"
}
],
"orderReports": [
{
"symbol": "LTCBTC",
"orderId": 10,
"orderListId": 1,
"clientOrderId": "44nZvqpemY7sVYgPYbvPih",
"transactTime": 1710485608839,
"price": "1.00000000",
"origQty": "5.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "STOP_LOSS_LIMIT",
"side": "SELL",
"stopPrice": "1.00000000",
"workingTime": -1,
"icebergQty": "1.00000000",
"selfTradePreventionMode": "NONE"
},
{
"symbol": "LTCBTC",
"orderId": 11,
"orderListId": 1,
"clientOrderId": "NuMp0nVYnciDiFmVqfpBqK",
"transactTime": 1710485608839,
"price": "3.00000000",
"origQty": "5.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT_MAKER",
"side": "SELL",
"workingTime": 1710485608839,
"selfTradePreventionMode": "NONE"
}
]
}
POST /api/v3/orderList/oco
Send in an one-cancels-the-other (OCO) pair, where activation of one order immediately cancels the other.
- An OCO has 2 legs called the above leg and below leg.
- One of the legs must be a
LIMIT_MAKER
order and the other leg must beSTOP_LOSS
orSTOP_LOSS_LIMIT
order. - Price restrictions:
- If the OCO is on the
SELL
side:LIMIT_MAKER
price
> Last Traded Price >stopPrice
- If the OCO is on the
BUY
side:LIMIT_MAKER
price
< Last Traded Price <stopPrice
- If the OCO is on the
- OCOs add 2 orders to the unfilled order count,
EXCHANGE_MAX_ORDERS
filter, and theMAX_NUM_ORDERS
filter.
Response format for orderReports
is selected using the newOrderRespType
parameter.
The response example is for the RESULT
response type. See POST /api/v3/order
for more examples.
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | Yes | |
listClientOrderId | STRING | No | Arbitrary unique ID among open order lists. Automatically generated if not sent. A new order list with the same listClientOrderId is accepted only when the previous one is filled or completely expired. listClientOrderId is distinct from the aboveClientOrderId and the belowCLientOrderId . |
side | ENUM | Yes | BUY or SELL |
quantity | DECIMAL | Yes | Quantity for both legs of the order list. |
aboveType | ENUM | Yes | Supported values : STOP_LOSS_LIMIT , STOP_LOSS , LIMIT_MAKER |
aboveClientOrderId | STRING | No | Arbitrary unique ID among open orders for the above leg order. Automatically generated if not sent |
aboveIcebergQty | LONG | No | Note that this can only be used if aboveTimeInForce is GTC . |
abovePrice | DECIMAL | No | |
aboveStopPrice | DECIMAL | No | Can be used if aboveType is STOP_LOSS or STOP_LOSS_LIMIT . Either aboveStopPrice or aboveTrailingDelta or both, must be specified. |
aboveTrailingDelta | LONG | No | See Trailing Stop order FAQ. |
aboveTimeInForce | DECIMAL | No | Required if the aboveType is STOP_LOSS_LIMIT . |
aboveStrategyId | INT | No | Arbitrary numeric value identifying the above leg order within an order strategy. |
aboveStrategyType | INT | No | Arbitrary numeric value identifying the above leg order strategy. Values smaller than 1000000 are reserved and cannot be used. |
belowType | ENUM | Yes | Supported values : STOP_LOSS_LIMIT , STOP_LOSS , LIMIT_MAKER |
belowClientOrderId | STRING | No | Arbitrary unique ID among open orders for the below leg order. Automatically generated if not sent |
belowIcebergQty | LONG | No | Note that this can only be used if belowTimeInForce is GTC . |
belowPrice | DECIMAL | No | |
belowStopPrice | DECIMAL | No | Can be used if belowType is STOP_LOSS or STOP_LOSS_LIMIT . Either belowStopPrice or belowTrailingDelta or both, must be specified. |
belowTrailingDelta | LONG | No | See Trailing Stop order FAQ. |
belowTimeInForce | ENUM | No | Required if the belowType is STOP_LOSS_LIMIT . |
belowStrategyId | INT | No | Arbitrary numeric value identifying the below leg order within an order strategy. |
belowStrategyType | INT | No | Arbitrary numeric value identifying the below leg order strategy. Values smaller than 1000000 are reserved and cannot be used. |
newOrderRespType | ENUM | No | Select response format: ACK , RESULT , FULL |
selfTradePreventionMode | ENUM | No | The allowed enums is dependent on what is configured on the symbol. The possible supported values are EXPIRE_TAKER , EXPIRE_MAKER , EXPIRE_BOTH , NONE . |
recvWindow | LONG | No | The value cannot be greater than 60000 . |
timestamp | LONG | Yes |
Data Source: Matching Engine
New Order List - OTO (TRADE)
Response:
{
"orderListId": 0,
"contingencyType": "OTO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "yl2ERtcar1o25zcWtqVBTC",
"transactionTime": 1712289389158,
"symbol": "ABCDEF",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 4,
"clientOrderId": "Bq17mn9fP6vyCn75Jw1xya"
},
{
"symbol": "LTCBTC",
"orderId": 5,
"clientOrderId": "arLFo0zGJVDE69cvGBaU0d"
}
],
"orderReports": [
{
"symbol": "LTCBTC",
"orderId": 4,
"orderListId": 0,
"clientOrderId": "Bq17mn9fP6vyCn75Jw1xya",
"transactTime": 1712289389158,
"price": "1.00000000",
"origQty": "1.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "SELL",
"workingTime": 1712289389158,
"selfTradePreventionMode": "NONE"
},
{
"symbol": "LTCBTC",
"orderId": 5,
"orderListId": 0,
"clientOrderId": "arLFo0zGJVDE69cvGBaU0d",
"transactTime": 1712289389158,
"price": "0.00000000",
"origQty": "5.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "PENDING_NEW",
"timeInForce": "GTC",
"type": "MARKET",
"side": "BUY",
"workingTime": -1,
"selfTradePreventionMode": "NONE"
}
]
}
POST /api/v3/orderList/oto
- An OTO (One-Triggers-the-Other) is an order list comprised of 2 orders.
- The first order is called the working order and must be
LIMIT
orLIMIT_MAKER
. Initially, only the working order goes on the order book. - The second order is called the pending order. It can be any order type except for
MARKET
orders using parameterquoteOrderQty
. The pending order is only placed on the order book when the working order gets fully filled. - If either the working order or the pending order is cancelled individually, the other order in the order list will also be canceled or expired.
- When the order list is placed, if the working order gets immediately fully filled, the placement response will show the working order as
FILLED
but the pending order will still appear asPENDING_NEW
. You need to query the status of the pending order again to see its updated status. - OTOs add 2 orders to the unfilled order count.,
EXCHANGE_MAX_NUM_ORDERS
filter andMAX_NUM_ORDERS
filter.
Weight:(IP) 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
listClientOrderId | STRING | NO | Arbitrary unique ID among open order lists. Automatically generated if not sent. A new order list with the same listClientOrderId is accepted only when the previous one is filled or completely expired. listClientOrderId is distinct from the workingClientOrderId and the pendingClientOrderId . |
newOrderRespType | ENUM | NO | Format of the JSON response. Supported values: ACK , FULL , RESULT |
selfTradePreventionMode | ENUM | NO | The allowed values are dependent on what is configured on the symbol. |
workingType | ENUM | YES | Supported values: LIMIT ,LIMIT_MAKER |
workingSide | ENUM | YES | Supported values: BUY , SELL |
workingClientOrderId | STRING | NO | Arbitrary unique ID among open orders for the working order. Automatically generated if not sent. |
workingPrice | DECIMAL | YES | |
workingQuantity | DECIMAL | YES | Sets the quantity for the working order. |
workingIcebergQty | DECIMAL | YES | This can only be used if workingTimeInForce is GTC or if workingType is LIMIT_MAKER . |
workingTimeInForce | ENUM | NO | Supported values: FOK , IOC , GTC |
workingStrategyId | INT | NO | Arbitrary numeric value identifying the working order within an order strategy. |
workingStrategyType | INT | NO | Arbitrary numeric value identifying the working order strategy. Values smaller than 1000000 are reserved and cannot be used. |
pendingType | ENUM | YES | Note that MARKET orders using quoteOrderQty are not supported. |
pendingSide | ENUM | YES | Supported values: BUY , SELL |
pendingClientOrderId | STRING | NO | Arbitrary unique ID among open orders for the pending order. Automatically generated if not sent. |
pendingPrice | DECIMAL | NO | |
pendingStopPrice | DECIMAL | NO | |
pendingTrailingDelta | DECIMAL | NO | |
pendingQuantity | DECIMAL | YES | Sets the quantity for the pending order. |
pendingIcebergQty | DECIMAL | NO | This can only be used if pendingTimeInForce is GTC or if pendingType is LIMIT_MAKER . |
pendingTimeInForce | ENUM | NO | Supported values: GTC , FOK , IOC |
pendingStrategyId | INT | NO | Arbitrary numeric value identifying the pending order within an order strategy. |
pendingStrategyType | INT | NO | Arbitrary numeric value identifying the pending order strategy. Values smaller than 1000000 are reserved and cannot be used. |
recvWindow | LONG | NO | The value cannot be greater than 60000 . |
timestamp | LONG | YES |
Mandatory parameters based on pendingType
or workingType
Depending on the pendingType
or workingType
, some optional parameters will become mandatory.
Type | Additional mandatory parameters | Additional information |
---|---|---|
workingType = LIMIT |
workingTimeInForce |
|
pendingType = LIMIT |
pendingPrice , pendingTimeInForce |
|
pendingType = STOP_LOSS or TAKE_PROFIT |
pendingStopPrice and/or pendingTrailingDelta |
|
pendingType = STOP_LOSS_LIMIT or TAKE_PROFIT_LIMIT |
pendingPrice , pendingStopPrice and/or pendingTrailingDelta , pendingTimeInForce |
Data Source:
Matching Engine
New Order List - OTOCO (TRADE)
Response:
{
"orderListId": 1,
"contingencyType": "OTO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "RumwQpBaDctlUu5jyG5rs0",
"transactionTime": 1712291372842,
"symbol": "ABCDEF",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 6,
"clientOrderId": "fM9Y4m23IFJVCQmIrlUmMK"
},
{
"symbol": "LTCBTC",
"orderId": 7,
"clientOrderId": "6pcQbFIzTXGZQ1e2MkGDq4"
},
{
"symbol": "LTCBTC",
"orderId": 8,
"clientOrderId": "r4JMv9cwAYYUwwBZfbussx"
}
],
"orderReports": [
{
"symbol": "LTCBTC",
"orderId": 6,
"orderListId": 1,
"clientOrderId": "fM9Y4m23IFJVCQmIrlUmMK",
"transactTime": 1712291372842,
"price": "1.00000000",
"origQty": "1.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "SELL",
"workingTime": 1712291372842,
"selfTradePreventionMode": "NONE"
},
{
"symbol": "LTCBTC",
"orderId": 7,
"orderListId": 1,
"clientOrderId": "6pcQbFIzTXGZQ1e2MkGDq4",
"transactTime": 1712291372842,
"price": "1.00000000",
"origQty": "5.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "PENDING_NEW",
"timeInForce": "IOC",
"type": "STOP_LOSS_LIMIT",
"side": "BUY",
"stopPrice": "6.00000000",
"workingTime": -1,
"selfTradePreventionMode": "NONE"
},
{
"symbol": "LTCBTC",
"orderId": 8,
"orderListId": 1,
"clientOrderId": "r4JMv9cwAYYUwwBZfbussx",
"transactTime": 1712291372842,
"price": "3.00000000",
"origQty": "5.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "PENDING_NEW",
"timeInForce": "GTC",
"type": "LIMIT_MAKER",
"side": "BUY",
"workingTime": -1,
"selfTradePreventionMode": "NONE"
}
]
}
POST /api/v3/orderList/otoco
Place an OTOCO.
An OTOCO (One-Triggers-One-Cancels-the-Other) is an order list comprised of 3 orders.
The first order is called the working order and must be
LIMIT
orLIMIT_MAKER
. Initially, only the working order goes on the order book.- The behavior of the working order is the same as the OTO.
OTOCO has 2 pending orders (pending above and pending below), forming an OCO pair. The pending orders are only placed on the order book when the working order gets fully filled.
- The rules of the pending above and pending below follow the same rules as the Order List OCO.
OTOCOs add 3 orders against the unfilled order count,
EXCHANGE_MAX_NUM_ORDERS
filter, andMAX_NUM_ORDERS
filter.
Weight:(IP) 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
listClientOrderId | STRING | NO | Arbitrary unique ID among open order lists. Automatically generated if not sent. A new order list with the same listClientOrderId is accepted only when the previous one is filled or completely expired. listClientOrderId is distinct from the workingClientOrderId , pendingAboveClientOrderId , and the pendingBelowClientOrderId . |
newOrderRespType | ENUM | NO | Format the JSON response. Supported values: ACK , FULL , RESPONSE |
selfTradePreventionMode | ENUM | NO | The allowed values are dependent on what is configured on the symbol. |
workingType | ENUM | YES | Supported values: LIMIT , LIMIT_MAKER |
workingSide | ENUM | YES | Supported values: BUY , SELL |
workingClientOrderId | STRING | NO | Arbitrary unique ID among open orders for the working order. Automatically generated if not sent. |
workingPrice | DECIMAL | YES | |
workingQuantity | DECIMAL | YES | |
workingIcebergQty | DECIMAL | NO | This can only be used if workingTimeInForce is GTC or if workingType is LIMIT_MAKER . |
workingTimeInForce | ENUM | NO | Supported values: GTC , IOC , FOK |
workingStrategyId | INT | NO | Arbitrary numeric value identifying the working order within an order strategy. |
workingStrategyType | INT | NO | Arbitrary numeric value identifying the working order strategy. Values smaller than 1000000 are reserved and cannot be used. |
pendingSide | ENUM | YES | Supported values: BUY , SELL |
pendingQuantity | DECIMAL | YES | |
pendingAboveType | ENUM | YES | Supported values: LIMIT_MAKER , STOP_LOSS , and STOP_LOSS_LIMIT |
pendingAboveClientOrderId | STRING | NO | Arbitrary unique ID among open orders for the pending above order. Automatically generated if not sent. |
pendingAbovePrice | DECIMAL | NO | |
pendingAboveStopPrice | DECIMAL | NO | |
pendingAboveTrailingDelta | DECIMAL | NO | |
pendingAboveIcebergQty | DECIMAL | NO | This can only be used if pendingAboveTimeInForce is GTC or if pendingAboveType is LIMIT_MAKER . |
pendingAboveTimeInForce | ENUM | NO | |
pendingAboveStrategyId | INT | NO | Arbitrary numeric value identifying the pending above order within an order strategy. |
pendingAboveStrategyType | INT | NO | Arbitrary numeric value identifying the pending above order strategy. Values smaller than 1000000 are reserved and cannot be used. |
pendingBelowType | ENUM | NO | Supported values: LIMIT_MAKER , STOP_LOSS , and STOP_LOSS_LIMIT |
pendingBelowClientOrderId | STRING | NO | Arbitrary unique ID among open orders for the pending below order. Automatically generated if not sent. |
pendingBelowPrice | DECIMAL | NO | |
pendingBelowStopPrice | DECIMAL | NO | |
pendingBelowTrailingDelta | DECIMAL | NO | |
pendingBelowIcebergQty | DECIMAL | NO | This can only be used if pendingBelowTimeInForce is GTC or if pendingBelowType is LIMIT_MAKER . |
pendingBelowTimeInForce | ENUM | NO | |
pendingBelowStrategyId | INT | NO | Arbitrary numeric value identifying the pending below order within an order strategy. |
pendingBelowStrategyType | INT | NO | Arbitrary numeric value identifying the pending below order strategy. Values smaller than 1000000 are reserved and cannot be used. |
recvWindow | LONG | NO | The value cannot be greater than 60000 . |
timestamp | LONG | YES |
Mandatory parameters based on pendingAboveType
, pendingBelowType
or workingType
Depending on the pendingAboveType
/pendingBelowType
or workingType
, some optional parameters will become mandatory.
Type | Additional mandatory parameters | Additional information |
---|---|---|
workingType = LIMIT |
workingTimeInForce |
|
pendingAboveType = LIMIT_MAKER |
pendingAbovePrice |
|
pendingAboveType = STOP_LOSS |
pendingAboveStopPrice and/or pendingAboveTrailingDelta |
|
pendingAboveType =STOP_LOSS_LIMIT |
pendingAbovePrice , pendingAboveStopPrice and/or pendingAboveTrailingDelta , pendingAboveTimeInForce |
|
pendingBelowType = LIMIT_MAKER |
pendingBelowPrice |
|
pendingBelowType = STOP_LOSS |
pendingBelowStopPrice and/or pendingBelowTrailingDelta |
|
pendingBelowType =STOP_LOSS_LIMIT |
pendingBelowPrice , pendingBelowStopPrice and/or pendingBelowTrailingDelta , pendingBelowTimeInForce |
Data Source:
Matching Engine
Cancel Order lists (TRADE)
Response:
{
"orderListId": 0,
"contingencyType": "OCO",
"listStatusType": "ALL_DONE",
"listOrderStatus": "ALL_DONE",
"listClientOrderId": "C3wyj4WVEktd7u9aVBRXcN",
"transactionTime": 1574040868128,
"symbol": "LTCBTC",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 2,
"clientOrderId": "pO9ufTiFGg3nw2fOdgeOXa"
},
{
"symbol": "LTCBTC",
"orderId": 3,
"clientOrderId": "TXOvglzXuaubXAaENpaRCB"
}
],
"orderReports": [
{
"symbol": "LTCBTC",
"origClientOrderId": "pO9ufTiFGg3nw2fOdgeOXa",
"orderId": 2,
"orderListId": 0,
"clientOrderId": "unfWT8ig8i0uj6lPuYLez6",
"transactTime": 1688005070874,
"price": "1.00000000",
"origQty": "10.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "STOP_LOSS_LIMIT",
"side": "SELL",
"stopPrice": "1.00000000",
"selfTradePreventionMode": "NONE"
},
{
"symbol": "LTCBTC",
"origClientOrderId": "TXOvglzXuaubXAaENpaRCB",
"orderId": 3,
"orderListId": 0,
"clientOrderId": "unfWT8ig8i0uj6lPuYLez6",
"transactTime": 1688005070874,
"price": "3.00000000",
"origQty": "10.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT_MAKER",
"side": "SELL",
"selfTradePreventionMode": "NONE"
}
]
}
DELETE /api/v3/orderList
Cancel an entire Order List.
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
orderListId | LONG | NO | Either orderListId or listClientOrderId must be provided |
listClientOrderId | STRING | NO | Either orderListId or listClientOrderId must be provided |
newClientOrderId | STRING | NO | Used to uniquely identify this cancel. Automatically generated by default |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Additional notes:
- Canceling an individual leg will cancel the entire OCO
- If both
orderListId
andlistClientOrderID
are provided,orderId
takes precedence.
Data Source: Matching Engine
Query Order lists (USER_DATA)
Response:
{
"orderListId": 27,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "h2USkA5YQpaXHPIrkd96xE",
"transactionTime": 1565245656253,
"symbol": "LTCBTC",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 4,
"clientOrderId": "qD1gy3kc3Gx0rihm9Y3xwS"
},
{
"symbol": "LTCBTC",
"orderId": 5,
"clientOrderId": "ARzZ9I00CPM8i3NhmU9Ega"
}
]
}
GET /api/v3/orderList
Retrieves a specific Order list based on provided optional parameters
Weight(IP): 4
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
orderListId | LONG | NO | Either orderListId or origClientOrderId must be provided |
origClientOrderId | STRING | NO | Either orderListId or origClientOrderId must be provided |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Data Source: Database
Query all Order lists (USER_DATA)
Response:
[
{
"orderListId": 29,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "amEEAXryFzFwYF1FeRpUoZ",
"transactionTime": 1565245913483,
"symbol": "LTCBTC",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 4,
"clientOrderId": "oD7aesZqjEGlZrbtRpy5zB"
},
{
"symbol": "LTCBTC",
"orderId": 5,
"clientOrderId": "Jr1h6xirOxgeJOUuYQS7V3"
}
]
},
{
"orderListId": 28,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "hG7hFNxJV6cZy3Ze4AUT4d",
"transactionTime": 1565245913407,
"symbol": "LTCBTC",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 2,
"clientOrderId": "j6lFOfbmFMRjTYA7rRJ0LP"
},
{
"symbol": "LTCBTC",
"orderId": 3,
"clientOrderId": "z0KCjOdditiLS5ekAFtK81"
}
]
}
]
GET /api/v3/allOrderList
Retrieves all Order lists based on provided optional parameters
Weight(IP): 20
Parameters
Name | Type | Mandatory | Description |
---|---|---|---|
fromId | LONG | NO | If supplied, neither startTime or endTime can be provided |
startTime | LONG | NO | |
endTime | LONG | NO | |
limit | INT | NO | Default Value: 500; Max Value: 1000 |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Data Source: Database
Query Open Order lists (USER_DATA)
Response:
[
{
"orderListId": 31,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "wuB13fmulKj3YjdqWEcsnp",
"transactionTime": 1565246080644,
"symbol": "LTCBTC",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 4,
"clientOrderId": "r3EH2N76dHfLoSZWIUw1bT"
},
{
"symbol": "LTCBTC",
"orderId": 5,
"clientOrderId": "Cv1SnyPD3qhqpbjpYEHbd2"
}
]
}
]
GET /api/v3/openOrderList
Weight(IP): 6
Parameters
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Data Source: Database
New order using SOR (TRADE)
Response:
{
"symbol": "BTCUSDT",
"orderId": 2,
"orderListId": -1,
"clientOrderId": "sBI1KM6nNtOfj5tccZSKly",
"transactTime": 1689149087774,
"price": "31000.00000000",
"origQty": "0.50000000",
"executedQty": "0.50000000",
"cummulativeQuoteQty": "14000.00000000",
"status": "FILLED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"workingTime": 1689149087774,
"fills": [
{
"matchType": "ONE_PARTY_TRADE_REPORT",
"price": "28000.00000000",
"qty": "0.50000000",
"commission": "0.00000000",
"commissionAsset": "BTC",
"tradeId": -1,
"allocId": 0
}
],
"workingFloor": "SOR",
"selfTradePreventionMode": "NONE",
"usedSor": true
}
POST /api/v3/sor/order
Places an order using smart order routing (SOR).
Weight: 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
side | ENUM | YES | |
type | ENUM | YES | |
timeInForce | ENUM | NO | |
quantity | DECIMAL | YES | |
price | DECIMAL | NO | |
newClientOrderId | STRING | NO | A unique id among open orders. Automatically generated if not sent. Orders with the same newClientOrderID can be accepted only when the previous one is filled, otherwise the order will be rejected. |
strategyId | INT | NO | |
strategyType | INT | NO | The value cannot be less than 1000000 . |
icebergQty | DECIMAL | NO | Used with LIMIT to create an iceberg order. |
newOrderRespType | ENUM | NO | Set the response JSON. ACK , RESULT , or FULL . Default to FULL |
selfTradePreventionMode | ENUM | NO | The allowed enums is dependent on what is configured on the symbol. The possible supported values are EXPIRE_TAKER , EXPIRE_MAKER , EXPIRE_BOTH , NONE . |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Note: POST /api/v3/sor/order
only supports LIMIT
and MARKET
orders. quoteOrderQty
is not supported.
Data Source: Matching Engine
Test new order using SOR (TRADE)
Response:
{}
OR
{
"standardCommissionForOrder": { //Standard commission rates on trades from the order.
"maker": "0.00000112",
"taker": "0.00000114",
},
"taxCommissionForOrder": { //Tax commission rates for trades from the order.
"maker": "0.00000112",
"taker": "0.00000114",
},
"discount": { //Discount on standard commissions when paying in BNB.
"enabledForAccount": true,
"enabledForSymbol": true,
"discountAsset": "BNB",
"discount": "0.25000000" //Standard commission is reduced by this rate when paying commission in BNB.
}
}
POST /api/v3/sor/order/test
Test new order creation and signature/recvWindow using smart order routing (SOR). Creates and validates a new order but does not send it into the matching engine.
Weight:
Condition | Request Weight |
---|---|
Without computeCommissionRates |
1 |
With computeCommissionRates |
20 |
Parameters:
In addition to all parameters accepted by POST /api/v3/sor/order
,
the following optional parameters are also accepted:
Name | Type | Mandatory | Description |
---|---|---|---|
computeCommissionRates | BOOLEAN | NO | Default: false |
Spot Account Endpoints
Account Information (USER_DATA)
Response:
{
"makerCommission": 15,
"takerCommission": 15,
"buyerCommission": 0,
"sellerCommission": 0,
"commissionRates": {
"maker": "0.00150000",
"taker": "0.00150000",
"buyer": "0.00000000",
"seller": "0.00000000"
},
"canTrade": true,
"canWithdraw": true,
"canDeposit": true,
"brokered": false,
"requireSelfTradePrevention": false,
"preventSor": false,
"updateTime": 123456789,
"accountType": "SPOT",
"balances": [
{
"asset": "BTC",
"free": "4723846.89208129",
"locked": "0.00000000"
},
{
"asset": "LTC",
"free": "4763368.68006011",
"locked": "0.00000000"
}
],
"permissions": [
"SPOT"
],
"uid": 354937868
}
GET /api/v3/account
Get current account information.
Weight(IP): 20
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
omitZeroBalances | BOOLEAN | NO | When set to true , emits only the non-zero balances of an account. Default value: false |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Data Source: Memory => Database
Account Trade List (USER_DATA)
Response:
[
{
"symbol": "BNBBTC",
"id": 28457,
"orderId": 100234,
"orderListId": -1, //Unless an order list, the value will always be -1
"price": "4.00000100",
"qty": "12.00000000",
"quoteQty": "48.000012",
"commission": "10.10000000",
"commissionAsset": "BNB",
"time": 1499865549590,
"isBuyer": true,
"isMaker": false,
"isBestMatch": true
}
]
GET /api/v3/myTrades
Get trades for a specific account and symbol.
Weight(IP): 20
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
orderId | LONG | NO | This can only be used in combination with symbol . |
startTime | LONG | NO | |
endTime | LONG | NO | |
fromId | LONG | NO | TradeId to fetch from. Default gets most recent trades. |
limit | INT | NO | Default 500; max 1000. |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Notes:
- If
fromId
is set, it will get id >= thatfromId
. Otherwise most recent trades are returned. - The time between
startTime
andendTime
can't be longer than 24 hours. - These are the supported combinations of all parameters:
symbol
symbol
+orderId
symbol
+startTime
symbol
+endTime
symbol
+fromId
symbol
+startTime
+endTime
symbol
+orderId
+fromId
Data Source: Memory => Database
Query Unfilled Order Count (USER_DATA)
Response:
[
{
"rateLimitType": "ORDERS",
"interval": "SECOND",
"intervalNum": 10,
"limit": 10000,
"count": 0
},
{
"rateLimitType": "ORDERS",
"interval": "DAY",
"intervalNum": 1,
"limit": 20000,
"count": 0
}
]
GET /api/v3/rateLimit/order
Displays the user's unfilled order count for all intervals.
Weight(IP): 40
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Data Source: Memory
Query Prevented Matches (USER_DATA)
Response:
[
{
"symbol": "BTCUSDT",
"preventedMatchId": 1,
"takerOrderId": 5,
"makerOrderId": 3,
"tradeGroupId": 1,
"selfTradePreventionMode": "EXPIRE_MAKER",
"price": "1.100000",
"makerPreventedQuantity": "1.300000",
"transactTime": 1669101687094
}
]
GET /api/v3/myPreventedMatches
Displays the list of orders that were expired because of STP.
For additional information on what a Prevented match is, as well as Self Trade Prevention (STP), please refer to our STP FAQ page.
These are the combinations supported:
symbol
+preventedMatchId
symbol
+orderId
symbol
+orderId
+fromPreventedMatchId
(limit
will default to 500)symbol
+orderId
+fromPreventedMatchId
+limit
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
preventedMatchId | LONG | NO | |
orderId | LONG | NO | |
fromPreventedMatchId | LONG | NO | |
limit | INT | NO | Default: 500 ; Max: 1000 |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Weight(IP)
Case | Weight |
---|---|
If symbol is invalid |
2 |
Querying by preventedMatchId |
2 |
Querying by orderId |
20 |
Data Source:
Database
Query Allocations (USER_DATA)
Response:
[
{
"symbol": "BTCUSDT",
"allocationId": 0,
"allocationType": "SOR",
"orderId": 1,
"orderListId": -1,
"price": "1.00000000",
"qty": "5.00000000",
"quoteQty": "5.00000000",
"commission": "0.00000000",
"commissionAsset": "BTC",
"time": 1687506878118,
"isBuyer": true,
"isMaker": false,
"isAllocator": false
}
]
GET /api/v3/myAllocations
Retrieves allocations resulting from SOR order placement.
Weight: 20
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | Yes | |
startTime | LONG | No | |
endTime | LONG | No | |
fromAllocationId | INT | No | |
limit | INT | No | Default 500;Max 1000 |
orderId | LONG | No | |
recvWindow | LONG | No | The value cannot be greater than 60000 . |
timestamp | LONG | No |
Supported parameter combinations:
Parameters | Response |
---|---|
symbol |
allocations from oldest to newest |
symbol + startTime |
oldest allocations since startTime |
symbol + endTime |
newest allocations until endTime |
symbol + startTime + endTime |
allocations within the time range |
symbol + fromAllocationId |
allocations by allocation ID |
symbol + orderId |
allocations related to an order starting with oldest |
symbol + orderId + fromAllocationId |
allocations related to an order by allocation ID |
Note: The time between startTime
and endTime
can't be longer than 24 hours.
Data Source: Database
Query Commission Rates (USER_DATA)
Response:
{
"symbol": "BTCUSDT",
"standardCommission": { //Standard commission rates on trades from the order.
"maker": "0.00000010",
"taker": "0.00000020",
"buyer": "0.00000030",
"seller": "0.00000040"
},
"taxCommission": { //Tax commission rates for trades from the order.
"maker": "0.00000112",
"taker": "0.00000114",
"buyer": "0.00000118",
"seller": "0.00000116"
},
"discount": { //Discount commission when paying in BNB
"enabledForAccount": true,
"enabledForSymbol": true,
"discountAsset": "BNB",
"discount": "0.75000000" //Standard commission is reduced by this rate when paying commission in BNB.
}
}
GET /api/v3/account/commission
Get current account commission rates.
Weight: 20
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES |
Data Source: Database
Margin Account/Trade
Margin account borrow/repay(MARGIN)
Response:
{
//transaction id
"tranId": 100000001
}
POST /sapi/v1/margin/borrow-repay
Margin account borrow/repay(MARGIN)
Weight(UID): 1500
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | YES | |
isIsolated | STRING | YES | TRUE for Isolated Margin, FALSE for Cross Margin, Default FALSE |
symbol | STRING | YES | Only for Isolated margin |
amount | STRING | YES | |
type | STRING | YES | BORROW or REPAY |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Query borrow/repay records in Margin account(USER_DATA)
Response:
{
"rows": [
{
"isolatedSymbol": "BNBUSDT", // isolated symbol, will not be returned for crossed margin
"amount": "14.00000000", // Total amount borrowed/repaid
"asset": "BNB",
"interest": "0.01866667", // Interest repaid
"principal": "13.98133333", // Principal repaid
"status": "CONFIRMED", //one of PENDING (pending execution), CONFIRMED (successfully execution), FAILED (execution failed, nothing happened to your account);
"timestamp": 1563438204000,
"txId": 2970933056
}
],
"total": 1
}
GET /sapi/v1/margin/borrow-repay
Query borrow/repay records in Margin account
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | NO | |
isolatedSymbol | STRING | NO | Symbol in Isolated Margin |
txId | LONG | NO | tranId in POST /sapi/v1/margin/loan |
startTime | LONG | NO | |
endTime | LONG | NO | |
current | LONG | NO | Current querying page. Start from 1. Default:1 |
size | LONG | NO | Default:10 Max:100 |
type | STRING | YES | BORROW or REPAY |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
txId
orstartTime
must be sent.txId
takes precedence. Response in descending order- If an asset is sent, data within 30 days before
endTime
; If an asset is not sent, data within 7 days beforeendTime
- If neither
startTime
norendTime
is sent, the recent 7-day data will be returned. startTime
set asendTime
- 7days by default,endTime
set as current time by default
Get All Margin Assets (MARKET_DATA)
Response:
[
{
"assetFullName": "USD coin",
"assetName": "USDC",
"isBorrowable": true,
"isMortgageable": true,
"userMinBorrow": "0.00000000",
"userMinRepay": "0.00000000",
"delistTime": 1704973040
}
]
GET /sapi/v1/margin/allAssets
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | NO |
Get All Cross Margin Pairs (MARKET_DATA)
Response:
[
{
"base": "BNB",
"id": 351637150141315861,
"isBuyAllowed": true,
"isMarginTrade": true,
"isSellAllowed": true,
"quote": "BTC",
"symbol": "BNBBTC"
},
{
"base": "TRX",
"id": 351637923235429141,
"isBuyAllowed": true,
"isMarginTrade": true,
"isSellAllowed": true,
"quote": "BTC",
"symbol": "TRXBTC",
"delistTime": 1704973040
},
{
"base": "XRP",
"id": 351638112213990165,
"isBuyAllowed": true,
"isMarginTrade": true,
"isSellAllowed": true,
"quote": "BTC",
"symbol": "XRPBTC"
},
{
"base": "ETH",
"id": 351638524530850581,
"isBuyAllowed": true,
"isMarginTrade": true,
"isSellAllowed": true,
"quote": "BTC",
"symbol": "ETHBTC"
}
]
GET /sapi/v1/margin/allPairs
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | NO |
Query Margin PriceIndex (MARKET_DATA)
Response:
{
"calcTime": 1562046418000,
"price": "0.00333930",
"symbol": "BNBBTC"
}
GET /sapi/v1/margin/priceIndex
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES |
Margin Account New Order (TRADE)
Response ACK:
{
"symbol": "BTCUSDT",
"orderId": 28,
"clientOrderId": "6gCrw2kRUAF9CvJDGP16IP",
"isIsolated": true, // if isolated margin
"transactTime": 1507725176595
}
Response RESULT:
{
"symbol": "BTCUSDT",
"orderId": 28,
"clientOrderId": "6gCrw2kRUAF9CvJDGP16IP",
"transactTime": 1507725176595,
"price": "1.00000000",
"origQty": "10.00000000",
"executedQty": "10.00000000",
"cummulativeQuoteQty": "30000",
"status": "FILLED",
"timeInForce": "GTC",
"type": "MARKET",
"isIsolated": true, // if isolated margin
"side": "SELL",
"selfTradePreventionMode": "NONE"
}
Response FULL:
{
"symbol": "BTCUSDT",
"orderId": 28,
"clientOrderId": "6gCrw2kRUAF9CvJDGP16IP",
"transactTime": 1507725176595,
"price": "1.00000000",
"origQty": "10.00000000",
"executedQty": "10.00000000",
"cummulativeQuoteQty": "39983.00000000",
"status": "FILLED",
"timeInForce": "GTC",
"type": "MARKET",
"side": "SELL",
"marginBuyBorrowAmount": 5, // will not return if no margin trade happens
"marginBuyBorrowAsset": "BTC", // will not return if no margin trade happens
"isIsolated": true, // if isolated margin
"selfTradePreventionMode": "NONE",
"fills": [
{
"price": "4000.00000000",
"qty": "1.00000000",
"commission": "4.00000000",
"commissionAsset": "USDT"
},
{
"price": "3999.00000000",
"qty": "5.00000000",
"commission": "19.99500000",
"commissionAsset": "USDT"
},
{
"price": "3998.00000000",
"qty": "2.00000000",
"commission": "7.99600000",
"commissionAsset": "USDT"
},
{
"price": "3997.00000000",
"qty": "1.00000000",
"commission": "3.99700000",
"commissionAsset": "USDT"
},
{
"price": "3995.00000000",
"qty": "1.00000000",
"commission": "3.99500000",
"commissionAsset": "USDT"
}
]
}
POST /sapi/v1/margin/order
Post a new order for margin account.
Weight(UID): 6
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
side | ENUM | YES | BUY SELL |
type | ENUM | YES | |
quantity | DECIMAL | NO | |
quoteOrderQty | DECIMAL | NO | |
price | DECIMAL | NO | |
stopPrice | DECIMAL | NO | Used with STOP_LOSS , STOP_LOSS_LIMIT , TAKE_PROFIT , and TAKE_PROFIT_LIMIT orders. |
newClientOrderId | STRING | NO | A unique id among open orders. Automatically generated if not sent. |
icebergQty | DECIMAL | NO | Used with LIMIT , STOP_LOSS_LIMIT , and TAKE_PROFIT_LIMIT to create an iceberg order. |
newOrderRespType | ENUM | NO | Set the response JSON. ACK, RESULT, or FULL; MARKET and LIMIT order types default to FULL, all other orders default to ACK. |
sideEffectType | ENUM | NO | NO_SIDE_EFFECT, MARGIN_BUY, AUTO_REPAY,AUTO_BORROW_REPAY; default NO_SIDE_EFFECT. More info in FAQ |
timeInForce | ENUM | NO | GTC,IOC,FOK |
selfTradePreventionMode | ENUM | NO | The allowed enums is dependent on what is configured on the symbol. The possible supported values are EXPIRE_TAKER, EXPIRE_MAKER, EXPIRE_BOTH, NONE |
autoRepayAtCancel | BOOLEAN | NO | Only when MARGIN_BUY or AUTO_BORROW_REPAY order takes effect, true means that the debt generated by the order needs to be repay after the order is cancelled. The default is true |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- autoRepayAtCancel is suggested to set as “FALSE” to keep liability unrepaid under high frequent new order/cancel order execution
Margin Account Cancel Order (TRADE)
Response:
{
"symbol": "LTCBTC",
"isIsolated": true, // if isolated margin
"orderId": "28",
"origClientOrderId": "myOrder1",
"clientOrderId": "cancelMyOrder1",
"price": "1.00000000",
"origQty": "10.00000000",
"executedQty": "8.00000000",
"cummulativeQuoteQty": "8.00000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "SELL"
}
DELETE /sapi/v1/margin/order
Cancel an active order for margin account.
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
orderId | LONG | NO | |
origClientOrderId | STRING | NO | |
newClientOrderId | STRING | NO | Used to uniquely identify this cancel. Automatically generated by default. |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- Either orderId or origClientOrderId must be sent.
Margin Account Cancel all Open Orders on a Symbol (TRADE)
Response:
[
{
"symbol": "BTCUSDT",
"isIsolated": true, // if isolated margin
"origClientOrderId": "E6APeyTJvkMvLMYMqu1KQ4",
"orderId": 11,
"orderListId": -1,
"clientOrderId": "pXLV6Hz6mprAcVYpVMTGgx",
"price": "0.089853",
"origQty": "0.178622",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"selfTradePreventionMode": "NONE"
},
{
"symbol": "BTCUSDT",
"isIsolated": false, // if isolated margin
"origClientOrderId": "A3EF2HCwxgZPFMrfwbgrhv",
"orderId": 13,
"orderListId": -1,
"clientOrderId": "pXLV6Hz6mprAcVYpVMTGgx",
"price": "0.090430",
"origQty": "0.178622",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT",
"side": "BUY",
"selfTradePreventionMode": "NONE"
},
{
"orderListId": 1929,
"contingencyType": "OCO",
"listStatusType": "ALL_DONE",
"listOrderStatus": "ALL_DONE",
"listClientOrderId": "2inzWQdDvZLHbbAmAozX2N",
"transactionTime": 1585230948299,
"symbol": "BTCUSDT",
"isIsolated": true, // if isolated margin
"orders": [
{
"symbol": "BTCUSDT",
"orderId": 20,
"clientOrderId": "CwOOIPHSmYywx6jZX77TdL"
},
{
"symbol": "BTCUSDT",
"orderId": 21,
"clientOrderId": "461cPg51vQjV3zIMOXNz39"
}
],
"orderReports": [
{
"symbol": "BTCUSDT",
"origClientOrderId": "CwOOIPHSmYywx6jZX77TdL",
"orderId": 20,
"orderListId": 1929,
"clientOrderId": "pXLV6Hz6mprAcVYpVMTGgx",
"price": "0.668611",
"origQty": "0.690354",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "STOP_LOSS_LIMIT",
"side": "BUY",
"stopPrice": "0.378131",
"icebergQty": "0.017083"
},
{
"symbol": "BTCUSDT",
"origClientOrderId": "461cPg51vQjV3zIMOXNz39",
"orderId": 21,
"orderListId": 1929,
"clientOrderId": "pXLV6Hz6mprAcVYpVMTGgx",
"price": "0.008791",
"origQty": "0.690354",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT_MAKER",
"side": "BUY",
"icebergQty": "0.639962"
}
]
}
]
DELETE /sapi/v1/margin/openOrders
Cancels all active orders on a symbol for margin account.
This includes Order list orders.
Weight(IP): 1
Parameters
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Adjust cross margin max leverage (USER_DATA)
Response:
{
"success": true
}
POST /sapi/v1/margin/max-leverage
Adjust cross margin max leverage
Weight(UID): 3000
Request Limit: 1 times/min per UID
Parameters
Name | Type | Mandatory | Description |
---|---|---|---|
maxLeverage | Integer | YES | Can only adjust 3 , 5 or 10,Example: maxLeverage=10 for Cross Margin Pro ,maxLeverage = 5 or 3 for Cross Margin Classic |
- The margin level need higher than the initial risk ratio of adjusted leverage, the initial risk ratio of 3x is 1.5 , the initial risk ratio of 5x is 1.25, the initial risk ratio of 10x is 2.5.
Get Cross Margin Transfer History (USER_DATA)
Response:
{
"rows": [
{
"amount": "0.10000000",
"asset": "BNB",
"status": "CONFIRMED",
"timestamp": 1566898617,
"txId": 5240372201,
"type": "ROLL_IN",
"transFrom": "SPOT", //SPOT,FUTURES,FIAT,DELIVERY,MINING,ISOLATED_MARGIN,FUNDING,MOTHER_SPOT,OPTION,SUB_SPOT,SUB_MARGIN,CROSS_MARGIN
"transTo": "ISOLATED_MARGIN",//SPOT,FUTURES,FIAT,DELIVERY,MINING,ISOLATED_MARGIN,FUNDING,MOTHER_SPOT,OPTION,SUB_SPOT,SUB_MARGIN,CROSS_MARGIN
},
{
"amount": "5.00000000",
"asset": "USDT",
"status": "CONFIRMED",
"timestamp": 1566888436,
"txId": 5239810406,
"type": "ROLL_OUT",
"transFrom": "ISOLATED_MARGIN",//SPOT,FUTURES,FIAT,DELIVERY,MINING,ISOLATED_MARGIN,FUNDING,MOTHER_SPOT,OPTION,SUB_SPOT,SUB_MARGIN,CROSS_MARGIN
"transTo": "ISOLATED_MARGIN", //SPOT,FUTURES,FIAT,DELIVERY,MINING,ISOLATED_MARGIN,FUNDING,MOTHER_SPOT,OPTION,SUB_SPOT,SUB_MARGIN,CROSS_MARGIN
"fromSymbol": "BNBUSDT",
"toSymbol": "BTCUSDT"
},
{
"amount": "1.00000000",
"asset": "EOS",
"status": "CONFIRMED",
"timestamp": 1566888403,
"txId": 5239808703,
"type": "ROLL_IN"
}
],
"total": 3
}
GET /sapi/v1/margin/transfer
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | NO | |
type | STRING | NO | Transfer Type: ROLL_IN, ROLL_OUT |
startTime | LONG | NO | |
endTime | LONG | NO | |
current | LONG | NO | Currently querying page. Start from 1. Default:1 |
size | LONG | NO | Default:10 Max:100 |
isolatedSymbol | STRING | NO | Symbol in Isolated Margin |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- Response in descending order
- The max interval between
startTime
andendTime
is 30 days. - Returns data for last 7 days by default
Get Interest History (USER_DATA)
Response:
{
"rows": [
{
"txId": 1352286576452864727,
"interestAccuredTime": 1672160400000,
"asset": "USDT",
"rawAsset": "USDT", // will not be returned for isolated margin
"principal": "45.3313",
"interest": "0.00024995",
"interestRate": "0.00013233",
"type": "ON_BORROW",
"isolatedSymbol": "BNBUSDT" // isolated symbol, will not be returned for crossed margin
}
],
"total": 1
}
GET /sapi/v1/margin/interestHistory
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | NO | |
isolatedSymbol | STRING | NO | isolated symbol |
startTime | LONG | NO | per-second accuracy. milliseconds input will be ignored. e.g. XXXXXXXXXX000ms |
endTime | LONG | NO | per-second accuracy. milliseconds input will be ignored. e.g. XXXXXXXXXX000ms |
current | LONG | NO | Currently querying page. Start from 1. Default:1 |
size | LONG | NO | Default:10 Max:100 |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- Response in descending order
- If isolatedSymbol is not sent, crossed margin data will be returned
- The max interval between
startTime
andendTime
is 30 days. - If
startTime
andendTime
not sent, return records of the last 7 days by default - Set
archived
totrue
to query data from 6 months ago type
in response has 4 enums:PERIODIC
interest charged per hourON_BORROW
first interest charged on borrowPERIODIC_CONVERTED
interest charged per hour converted into BNBON_BORROW_CONVERTED
first interest charged on borrow converted into BNBPORTFOLIO
interest charged daily on the portfolio margin negative balance
Get Force Liquidation Record (USER_DATA)
Response:
{
"rows": [
{
"avgPrice": "0.00388359",
"executedQty": "31.39000000",
"orderId": 180015097,
"price": "0.00388110",
"qty": "31.39000000",
"side": "SELL",
"symbol": "BNBBTC",
"timeInForce": "GTC",
"isIsolated": true,
"updatedTime": 1558941374745
}
],
"total": 1
}
GET /sapi/v1/margin/forceLiquidationRec
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
startTime | LONG | NO | |
endTime | LONG | NO | |
isolatedSymbol | STRING | NO | |
current | LONG | NO | Currently querying page. Start from 1. Default:1 |
size | LONG | NO | Default:10 Max:100 |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- Response in descending order
Query Cross Margin Account Details (USER_DATA)
Response:
{
"created" : true, // True means margin account created , false means margin account not created.
"borrowEnabled": true,
"marginLevel": "11.64405625",
"collateralMarginLevel" : "3.2",
"totalAssetOfBtc": "6.82728457",
"totalLiabilityOfBtc": "0.58633215",
"totalNetAssetOfBtc": "6.24095242",
"totalCollateralValueInUSDT": "5.82728457",
"tradeEnabled": true,
"transferEnabled": true,
"accountType": "MARGIN_1", // //MARGIN_1 for Cross Margin Classic, MARGIN_2 for Cross Margin Pro
"userAssets": [
{
"asset": "BTC",
"borrowed": "0.00000000",
"free": "0.00499500",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00499500"
},
{
"asset": "BNB",
"borrowed": "201.66666672",
"free": "2346.50000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "2144.83333328"
},
{
"asset": "ETH",
"borrowed": "0.00000000",
"free": "0.00000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00000000"
},
{
"asset": "USDT",
"borrowed": "0.00000000",
"free": "0.00000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00000000"
}
]
}
GET /sapi/v1/margin/account
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Query Margin Account's Order (USER_DATA)
Response:
{
"clientOrderId": "ZwfQzuDIGpceVhKW5DvCmO",
"cummulativeQuoteQty": "0.00000000",
"executedQty": "0.00000000",
"icebergQty": "0.00000000",
"isWorking": true,
"orderId": 213205622,
"origQty": "0.30000000",
"price": "0.00493630",
"side": "SELL",
"status": "NEW",
"stopPrice": "0.00000000",
"symbol": "BNBBTC",
"isIsolated": true,
"time": 1562133008725,
"timeInForce": "GTC",
"type": "LIMIT",
"selfTradePreventionMode": "NONE",
"updateTime": 1562133008725
}
GET /sapi/v1/margin/order
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
orderId | LONG | NO | |
origClientOrderId | STRING | NO | |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- Either orderId or origClientOrderId must be sent.
- For some historical orders cummulativeQuoteQty will be < 0, meaning the data is not available at this time.
Query Margin Account's Open Orders (USER_DATA)
Response:
[
{
"clientOrderId": "qhcZw71gAkCCTv0t0k8LUK",
"cummulativeQuoteQty": "0.00000000",
"executedQty": "0.00000000",
"icebergQty": "0.00000000",
"isWorking": true,
"orderId": 211842552,
"origQty": "0.30000000",
"price": "0.00475010",
"side": "SELL",
"status": "NEW",
"stopPrice": "0.00000000",
"symbol": "BNBBTC",
"isIsolated": true,
"time": 1562040170089,
"timeInForce": "GTC",
"type": "LIMIT",
"selfTradePreventionMode": "NONE",
"updateTime": 1562040170089
}
]
GET /sapi/v1/margin/openOrders
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | NO | |
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- If the symbol is not sent, orders for all symbols will be returned in an array.
- When all symbols are returned, the number of requests counted against the rate limiter is equal to the number of symbols currently trading on the exchange.
- If isIsolated ="TRUE", symbol must be sent.
Query Margin Account's All Orders (USER_DATA)
Response:
[
{
"clientOrderId": "D2KDy4DIeS56PvkM13f8cP",
"cummulativeQuoteQty": "0.00000000",
"executedQty": "0.00000000",
"icebergQty": "0.00000000",
"isWorking": false,
"orderId": 41295,
"origQty": "5.31000000",
"price": "0.22500000",
"side": "SELL",
"status": "CANCELED",
"stopPrice": "0.18000000",
"symbol": "BNBBTC",
"isIsolated": false,
"time": 1565769338806,
"timeInForce": "GTC",
"type": "TAKE_PROFIT_LIMIT",
"selfTradePreventionMode": "NONE",
"updateTime": 1565769342148
},
{
"clientOrderId": "gXYtqhcEAs2Rn9SUD9nRKx",
"cummulativeQuoteQty": "0.00000000",
"executedQty": "0.00000000",
"icebergQty": "1.00000000",
"isWorking": true,
"orderId": 41296,
"origQty": "6.65000000",
"price": "0.18000000",
"side": "SELL",
"status": "CANCELED",
"stopPrice": "0.00000000",
"symbol": "BNBBTC",
"isIsolated": false,
"time": 1565769348687,
"timeInForce": "GTC",
"type": "LIMIT",
"selfTradePreventionMode": "NONE",
"updateTime": 1565769352226
}
]
GET /sapi/v1/margin/allOrders
Weight(IP): 200
Request Limit
60times/min per IP
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
orderId | LONG | NO | |
startTime | LONG | NO | |
endTime | LONG | NO | |
limit | INT | NO | Default 500; max 500. |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- If orderId is set, it will get orders >= that orderId. Otherwise most recent orders are returned.
- For some historical orders cummulativeQuoteQty will be < 0, meaning the data is not available at this time.
Margin Account New OCO (TRADE)
Response:
{
"orderListId": 0,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "JYVpp3F0f5CAG15DhtrqLp",
"transactionTime": 1563417480525,
"symbol": "LTCBTC",
"marginBuyBorrowAmount": "5", // will not return if no margin trade happens
"marginBuyBorrowAsset": "BTC", // will not return if no margin trade happens
"isIsolated": false, // if isolated margin
"orders": [
{
"symbol": "LTCBTC",
"orderId": 2,
"clientOrderId": "Kk7sqHb9J6mJWTMDVW7Vos"
},
{
"symbol": "LTCBTC",
"orderId": 3,
"clientOrderId": "xTXKaGYd4bluPVp78IVRvl"
}
],
"orderReports": [
{
"symbol": "LTCBTC",
"orderId": 2,
"orderListId": 0,
"clientOrderId": "Kk7sqHb9J6mJWTMDVW7Vos",
"transactTime": 1563417480525,
"price": "0.000000",
"origQty": "0.624363",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "STOP_LOSS",
"side": "BUY",
"stopPrice": "0.960664",
"selfTradePreventionMode": "NONE"
},
{
"symbol": "LTCBTC",
"orderId": 3,
"orderListId": 0,
"clientOrderId": "xTXKaGYd4bluPVp78IVRvl",
"transactTime": 1563417480525,
"price": "0.036435",
"origQty": "0.624363",
"executedQty": "0.000000",
"cummulativeQuoteQty": "0.000000",
"status": "NEW",
"timeInForce": "GTC",
"type": "LIMIT_MAKER",
"side": "BUY",
"selfTradePreventionMode": "NONE"
}
]
}
POST /sapi/v1/margin/order/oco
Send in a new OCO for a margin account
Weight(UID): 6
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
listClientOrderId | STRING | NO | A unique Id for the entire orderList |
side | ENUM | YES | |
quantity | DECIMAL | YES | |
limitClientOrderId | STRING | NO | A unique Id for the limit order |
price | DECIMAL | YES | |
limitIcebergQty | DECIMAL | NO | |
stopClientOrderId | STRING | NO | A unique Id for the stop loss/stop loss limit leg |
stopPrice | DECIMAL | YES | |
stopLimitPrice | DECIMAL | NO | If provided, stopLimitTimeInForce is required. |
stopIcebergQty | DECIMAL | NO | |
stopLimitTimeInForce | ENUM | NO | Valid values are GTC /FOK /IOC |
newOrderRespType | ENUM | NO | Set the response JSON. |
sideEffectType | ENUM | NO | NO_SIDE_EFFECT, MARGIN_BUY, AUTO_REPAY,AUTO_BORROW_REPAY; default NO_SIDE_EFFECT. More info in FAQ |
selfTradePreventionMode | ENUM | NO | The allowed enums is dependent on what is configured on the symbol. The possible supported values are EXPIRE_TAKER, EXPIRE_MAKER, EXPIRE_BOTH, NONE |
autoRepayAtCancel | BOOLEAN | NO | Only when MARGIN_BUY or AUTO_BORROW_REPAY order takes effect, true means that the debt generated by the order needs to be repay after the order is cancelled. The default is true |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Other Info:
- Price Restrictions:
SELL
: Limit Price > Last Price > Stop PriceBUY
: Limit Price < Last Price < Stop Price
- Quantity Restrictions:
- Both legs must have the same quantity
ICEBERG
quantities however do not have to be the same.
Order Rate Limit
OCO
counts as 2 orders against the order rate limit.
autoRepayAtCancel is suggested to set as “FALSE” to keep liability unrepaid under high frequent new order/cancel order execution
Margin Account Cancel OCO (TRADE)
Response:
{
"orderListId": 0,
"contingencyType": "OCO",
"listStatusType": "ALL_DONE",
"listOrderStatus": "ALL_DONE",
"listClientOrderId": "C3wyj4WVEktd7u9aVBRXcN",
"transactionTime": 1574040868128,
"symbol": "LTCBTC",
"isIsolated": false, // if isolated margin
"orders": [
{
"symbol": "LTCBTC",
"orderId": 2,
"clientOrderId": "pO9ufTiFGg3nw2fOdgeOXa"
},
{
"symbol": "LTCBTC",
"orderId": 3,
"clientOrderId": "TXOvglzXuaubXAaENpaRCB"
}
],
"orderReports": [
{
"symbol": "LTCBTC",
"origClientOrderId": "pO9ufTiFGg3nw2fOdgeOXa",
"orderId": 2,
"orderListId": 0,
"clientOrderId": "unfWT8ig8i0uj6lPuYLez6",
"price": "1.00000000",
"origQty": "10.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "STOP_LOSS_LIMIT",
"side": "SELL",
"stopPrice": "1.00000000",
"selfTradePreventionMode": "NONE"
},
{
"symbol": "LTCBTC",
"origClientOrderId": "TXOvglzXuaubXAaENpaRCB",
"orderId": 3,
"orderListId": 0,
"clientOrderId": "unfWT8ig8i0uj6lPuYLez6",
"price": "3.00000000",
"origQty": "10.00000000",
"executedQty": "0.00000000",
"cummulativeQuoteQty": "0.00000000",
"status": "CANCELED",
"timeInForce": "GTC",
"type": "LIMIT_MAKER",
"side": "SELL",
"selfTradePreventionMode": "NONE"
}
]
}
DELETE /sapi/v1/margin/orderList
Cancel an entire Order List for a margin account.
Weight(UID): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
orderListId | LONG | NO | Either orderListId or listClientOrderId must be provided |
listClientOrderId | STRING | NO | Either orderListId or listClientOrderId must be provided |
newClientOrderId | STRING | NO | Used to uniquely identify this cancel. Automatically generated by default |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Additional notes:
- Canceling an individual leg will cancel the entire OCO
Query Margin Account's OCO (USER_DATA)
Response:
{
"orderListId": 27,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "h2USkA5YQpaXHPIrkd96xE",
"transactionTime": 1565245656253,
"symbol": "LTCBTC",
"isIsolated": false, // if isolated margin
"orders": [
{
"symbol": "LTCBTC",
"orderId": 4,
"clientOrderId": "qD1gy3kc3Gx0rihm9Y3xwS"
},
{
"symbol": "LTCBTC",
"orderId": 5,
"clientOrderId": "ARzZ9I00CPM8i3NhmU9Ega"
}
]
}
GET /sapi/v1/margin/orderList
Retrieves a specific OCO based on provided optional parameters
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
symbol | STRING | NO | mandatory for isolated margin, not supported for cross margin |
orderListId | LONG | NO | Either orderListId or origClientOrderId must be provided |
origClientOrderId | STRING | NO | Either orderListId or origClientOrderId must be provided |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Query Margin Account's all OCO (USER_DATA)
Response:
[
{
"orderListId": 29,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "amEEAXryFzFwYF1FeRpUoZ",
"transactionTime": 1565245913483,
"symbol": "LTCBTC",
"isIsolated": true, // if isolated margin
"orders": [
{
"symbol": "LTCBTC",
"orderId": 4,
"clientOrderId": "oD7aesZqjEGlZrbtRpy5zB"
},
{
"symbol": "LTCBTC",
"orderId": 5,
"clientOrderId": "Jr1h6xirOxgeJOUuYQS7V3"
}
]
},
{
"orderListId": 28,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "hG7hFNxJV6cZy3Ze4AUT4d",
"transactionTime": 1565245913407,
"symbol": "LTCBTC",
"orders": [
{
"symbol": "LTCBTC",
"orderId": 2,
"clientOrderId": "j6lFOfbmFMRjTYA7rRJ0LP"
},
{
"symbol": "LTCBTC",
"orderId": 3,
"clientOrderId": "z0KCjOdditiLS5ekAFtK81"
}
]
}
]
GET /sapi/v1/margin/allOrderList
Retrieves all OCO for a specific margin account based on provided optional parameters
Weight(IP): 200
Parameters
Name | Type | Mandatory | Description |
---|---|---|---|
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
symbol | STRING | NO | mandatory for isolated margin, not supported for cross margin |
fromId | LONG | NO | If supplied, neither startTime or endTime can be provided |
startTime | LONG | NO | |
endTime | LONG | NO | |
limit | INT | NO | Default Value: 500; Max Value: 1000 |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Query Margin Account's Open OCO (USER_DATA)
Response:
[
{
"orderListId": 31,
"contingencyType": "OCO",
"listStatusType": "EXEC_STARTED",
"listOrderStatus": "EXECUTING",
"listClientOrderId": "wuB13fmulKj3YjdqWEcsnp",
"transactionTime": 1565246080644,
"symbol": "LTCBTC",
"isIsolated": false, // if isolated margin
"orders": [
{
"symbol": "LTCBTC",
"orderId": 4,
"clientOrderId": "r3EH2N76dHfLoSZWIUw1bT"
},
{
"symbol": "LTCBTC",
"orderId": 5,
"clientOrderId": "Cv1SnyPD3qhqpbjpYEHbd2"
}
]
}
]
GET /sapi/v1/margin/openOrderList
Weight(IP): 10
Parameters
Name | Type | Mandatory | Description |
---|---|---|---|
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
symbol | STRING | NO | mandatory for isolated margin, not supported for cross margin |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Query Margin Account's Trade List (USER_DATA)
Response:
[
{
"commission": "0.00006000",
"commissionAsset": "BTC",
"id": 34,
"isBestMatch": true,
"isBuyer": false,
"isMaker": false,
"orderId": 39324,
"price": "0.02000000",
"qty": "3.00000000",
"symbol": "BNBBTC",
"isIsolated": false,
"time": 1561973357171
}
]
GET /sapi/v1/margin/myTrades
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
orderId | LONG | NO | |
startTime | LONG | NO | |
endTime | LONG | NO | |
fromId | LONG | NO | TradeId to fetch from. Default gets most recent trades. |
limit | INT | NO | Default 500; max 1000. |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- If fromId is set, it will get trades >= that fromId. Otherwise most recent trades are returned.
Query Max Borrow (USER_DATA)
Response:
{
"amount": "1.69248805", // account's currently max borrowable amount with sufficient system availability
"borrowLimit": "60" // max borrowable amount limited by the account level
}
GET /sapi/v1/margin/maxBorrowable
Weight(IP): 50
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | YES | |
isolatedSymbol | STRING | NO | isolated symbol |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- If isolatedSymbol is not sent, crossed margin data will be sent.
borrowLimit
is also available from https://www.binance.com/en/margin-fee
Query Max Transfer-Out Amount (USER_DATA)
Response:
{
"amount": "3.59498107"
}
GET /sapi/v1/margin/maxTransferable
Weight(IP): 50
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | YES | |
isolatedSymbol | STRING | NO | isolated symbol |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
- If isolatedSymbol is not sent, crossed margin data will be sent.
Get Summary of Margin account (USER_DATA)
Response:
{
"normalBar": "1.5",
"marginCallBar": "1.3",
"forceLiquidationBar": "1.1"
}
GET /sapi/v1/margin/tradeCoeff
Get personal margin level information
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Query Isolated Margin Account Info (USER_DATA)
Response:
If "symbols" is not sent
{
"assets":[
{
"baseAsset":
{
"asset": "BTC",
"borrowEnabled": true,
"borrowed": "0.00000000",
"free": "0.00000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00000000",
"netAssetOfBtc": "0.00000000",
"repayEnabled": true,
"totalAsset": "0.00000000"
},
"quoteAsset":
{
"asset": "USDT",
"borrowEnabled": true,
"borrowed": "0.00000000",
"free": "0.00000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00000000",
"netAssetOfBtc": "0.00000000",
"repayEnabled": true,
"totalAsset": "0.00000000"
},
"symbol": "BTCUSDT",
"isolatedCreated": true,
"enabled": true, // true-enabled, false-disabled
"marginLevel": "0.00000000",
"marginLevelStatus": "EXCESSIVE", // "EXCESSIVE", "NORMAL", "MARGIN_CALL", "PRE_LIQUIDATION", "FORCE_LIQUIDATION"
"marginRatio": "0.00000000",
"indexPrice": "10000.00000000",
"liquidatePrice": "1000.00000000",
"liquidateRate": "1.00000000",
"tradeEnabled": true
}
],
"totalAssetOfBtc": "0.00000000",
"totalLiabilityOfBtc": "0.00000000",
"totalNetAssetOfBtc": "0.00000000"
}
If "symbols" is sent
{
"assets":[
{
"baseAsset":
{
"asset": "BTC",
"borrowEnabled": true,
"borrowed": "0.00000000",
"free": "0.00000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00000000",
"netAssetOfBtc": "0.00000000",
"repayEnabled": true,
"totalAsset": "0.00000000"
},
"quoteAsset":
{
"asset": "USDT",
"borrowEnabled": true,
"borrowed": "0.00000000",
"free": "0.00000000",
"interest": "0.00000000",
"locked": "0.00000000",
"netAsset": "0.00000000",
"netAssetOfBtc": "0.00000000",
"repayEnabled": true,
"totalAsset": "0.00000000"
},
"symbol": "BTCUSDT",
"isolatedCreated": true,
"enabled": true, // true-enabled, false-disabled
"marginLevel": "0.00000000",
"marginLevelStatus": "EXCESSIVE", // "EXCESSIVE", "NORMAL", "MARGIN_CALL", "PRE_LIQUIDATION", "FORCE_LIQUIDATION"
"marginRatio": "0.00000000",
"indexPrice": "10000.00000000",
"liquidatePrice": "1000.00000000",
"liquidateRate": "1.00000000",
"tradeEnabled": true
}
]
}
GET /sapi/v1/margin/isolated/account
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbols | STRING | NO | Max 5 symbols can be sent; separated by ",". e.g. "BTCUSDT,BNBUSDT,ADAUSDT" |
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
- If "symbols" is not sent, all isolated assets will be returned.
- If "symbols" is sent, only the isolated assets of the sent symbols will be returned.
Disable Isolated Margin Account (TRADE)
Response:
{
"success": true,
"symbol": "BTCUSDT"
}
DELETE /sapi/v1/margin/isolated/account (HMAC SHA256)
Disable isolated margin account for a specific symbol. Each trading pair can only be deactivated once every 24 hours.
Weight(UID): 300
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
Enable Isolated Margin Account (TRADE)
Response:
{
"success": true,
"symbol": "BTCUSDT"
}
POST /sapi/v1/margin/isolated/account
Enable isolated margin account for a specific symbol(Only supports activation of previously disabled accounts).
Weight(UID): 300
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
Query Enabled Isolated Margin Account Limit (USER_DATA)
Response:
{
"enabledAccount": 5,
"maxAccount": 20
}
GET /sapi/v1/margin/isolated/accountLimit
Query enabled isolated margin account limit.
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
Get All Isolated Margin Symbol(MARKET_DATA)
Response:
[
{
"base": "BNB",
"isBuyAllowed": true,
"isMarginTrade": true,
"isSellAllowed": true,
"quote": "BTC",
"symbol": "BNBBTC"
},
{
"base": "TRX",
"isBuyAllowed": true,
"isMarginTrade": true,
"isSellAllowed": true,
"quote": "BTC",
"symbol": "TRXBTC",
"delistTime": 1704973040
},
{
"base": "XRP",
"isBuyAllowed": true,
"isMarginTrade": true,
"isSellAllowed": true,
"quote": "BTC",
"symbol": "XRPBTC"
},
{
"base": "ETH",
"isBuyAllowed": true,
"isMarginTrade": true,
"isSellAllowed": true,
"quote": "BTC",
"symbol": "ETHBTC"
}
]
GET /sapi/v1/margin/isolated/allPairs
Weight(IP): 10
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | NO |
Toggle BNB Burn On Spot Trade And Margin Interest (USER_DATA)
Response:
{
"spotBNBBurn":true,
"interestBNBBurn": false
}
POST /sapi/v1/bnbBurn
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
spotBNBBurn | STRING | NO | "true" or "false"; Determines whether to use BNB to pay for trading fees on SPOT |
interestBNBBurn | STRING | NO | "true" or "false"; Determines whether to use BNB to pay for margin loan's interest |
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
- "spotBNBBurn" and "interestBNBBurn" should be sent at least one.
Get BNB Burn Status (USER_DATA)
Response:
{
"spotBNBBurn":true,
"interestBNBBurn": false
}
GET /sapi/v1/bnbBurn
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
Query Margin Interest Rate History (USER_DATA)
Response:
[
{
"asset": "BTC",
"dailyInterestRate": "0.00025000",
"timestamp": 1611544731000,
"vipLevel": 1
},
{
"asset": "BTC",
"dailyInterestRate": "0.00035000",
"timestamp": 1610248118000,
"vipLevel": 1
}
]
GET /sapi/v1/margin/interestRateHistory
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
asset | STRING | YES | |
vipLevel | INT | NO | Default: user's vip level |
startTime | LONG | NO | Default: 7 days ago |
endTime | LONG | NO | Default: present. Maximum range: 1 months. |
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
Query Cross Margin Fee Data (USER_DATA)
Response:
[
{
"vipLevel": 0,
"coin": "BTC",
"transferIn": true,
"borrowable": true,
"dailyInterest": "0.00026125",
"yearlyInterest": "0.0953",
"borrowLimit": "180",
"marginablePairs": [
"BNBBTC",
"TRXBTC",
"ETHBTC",
"BTCUSDT"
]
}
]
GET /sapi/v1/margin/crossMarginData
Get cross margin fee data collection with any vip level or user's current specific data as https://www.binance.com/en/margin-fee
Weight(IP): 1 when coin is specified; 5 when the coin parameter is omitted
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
vipLevel | INT | NO | when parameter vipLevel is not sent, it returns data associated with the user's specific config; when parameter vipLevel is sent, it returns the default tier data (assuming user is not logged in) |
coin | STRING | NO | |
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
Query Isolated Margin Fee Data (USER_DATA)
Response:
[
{
"vipLevel": 0,
"symbol": "BTCUSDT",
"leverage": "10",
"data": [
{
"coin": "BTC",
"dailyInterest": "0.00026125",
"borrowLimit": "270"
},
{
"coin": "USDT",
"dailyInterest": "0.000475",
"borrowLimit": "2100000"
}
]
}
]
GET /sapi/v1/margin/isolatedMarginData
Get isolated margin fee data collection with any vip level or user's current specific data as https://www.binance.com/en/margin-fee
Weight(IP): 1 when a single is specified; 10 when the symbol parameter is omitted
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
vipLevel | INT | NO | User's current specific margin data will be returned if vipLevel is omitted |
symbol | STRING | NO | |
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
Query Isolated Margin Tier Data (USER_DATA)
Response:
[
{
"symbol": "BTCUSDT",
"tier": 1,
"effectiveMultiple": "10",
"initialRiskRatio": "1.111",
"liquidationRiskRatio": "1.05",
"baseAssetMaxBorrowable": "9",
"quoteAssetMaxBorrowable": "70000"
}
]
GET /sapi/v1/margin/isolatedMarginTier
Get isolated margin tier data collection with any tier as https://www.binance.com/en/margin-data
Weight(IP): 1
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
symbol | STRING | YES | |
tier | INTEGER | NO | All margin tier data will be returned if tier is omitted |
recvWindow | LONG | NO | No more than 60000 |
timestamp | LONG | YES |
Query Current Margin Order Count Usage (TRADE)
Response:
[
{
"rateLimitType": "ORDERS",
"interval": "SECOND",
"intervalNum": 10,
"limit": 10000,
"count": 0
},
{
"rateLimitType": "ORDERS",
"interval": "DAY",
"intervalNum": 1,
"limit": 20000,
"count": 0
}
]
GET /sapi/v1/margin/rateLimit/order
Displays the user's current margin order count usage for all intervals.
Weight(IP): 20
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
isIsolated | STRING | NO | for isolated margin or not, "TRUE", "FALSE",default "FALSE" |
symbol | STRING | NO | isolated symbol, mandatory for isolated margin |
recvWindow | LONG | NO | The value cannot be greater than 60000 |
timestamp | LONG | YES |
Cross margin collateral ratio (MARKET_DATA)
Response:
[
{
"collaterals": [
{
"minUsdValue": "0",
"maxUsdValue": "13000000",
"discountRate": "1"
},
{
"minUsdValue": "13000000",
"maxUsdValue": "20000000",
"discountRate": "0.975"
},
{
"minUsdValue": "20000000",
"discountRate": "0"
}
],
"assetNames": [
"BNX"
]
},
{
"collaterals": [
{
"minUsdValue": "0",
"discountRate": "1"
}
],
"assetNames": [
"BTC",
"BUSD",
"ETH",
"USDT"
]
}
]
GET /sapi/v1/margin/crossMarginCollateralRatio
Weight(IP): 100
Parameters: None
Get Small Liability Exchange Coin List (USER_DATA)
Query the coins which can be small liability exchange
Response:
[
{
"asset": "ETH",
"interest": "0.00083334",
"principal": "0.001",
"liabilityAsset": "USDT",
"liabilityQty": 0.3552
}
]
GET /sapi/v1/margin/exchange-small-liability
Weight(IP): 100
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Small Liability Exchange (MARGIN)
Cross Margin Small Liability Exchange
POST /sapi/v1/margin/exchange-small-liability
Weight(UID): 3000
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
assetNames | ARRAY | YES | The assets list of small liability exchange, Example: assetNames = BTC,ETH |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
- Only convert once within 6 hours
- Only liability valuation less than 10 USDT are supported
- The maximum number of coin is 10
Get Small Liability Exchange History (USER_DATA)
Get Small liability Exchange History
Response:
{
"total": 1,
"rows": [
{
"asset": "ETH",
"amount": "0.00083434",
"targetAsset": "BUSD",
"targetAmount": "1.37576819",
"bizType": "EXCHANGE_SMALL_LIABILITY",
"timestamp": 1672801339253
}
]
}
GET /sapi/v1/margin/exchange-small-liability-history
Weight(UID): 100
Parameters:
Name | Type | Mandatory | Description |
---|---|---|---|
current | INT | YES | Currently querying page. Start from 1. Default:1 |
size | INT | YES | Default:10, Max:100 |
startTime | LONG | NO | Default: 30 days from current timestamp |
endTime | LONG | NO | Default: present timestamp |
recvWindow | LONG | NO | |
timestamp | LONG | YES |
Get a future hourly interest rate (USER_DATA)
GET /sapi/v1/margin/next-hourly-interest-rate
Get user the next hourly estimate interest
Response:
[
{
"asset": "BTC",
"nextHourlyInterestRate": "0.00000571"
},
{
"asset":