Following DAPI endpoints will use new weight rule based on the parameter "LIMIT" in the request:
GET /dapi/v1/klines GET /dapi/v1/continuousKlines GET /dapi/v1/indexPriceKlines GET /dapi/v1/markPriceKlines.
Following DAPI endpoints' weights will be updated to 20:
GET /dapi/v1/historicalTrades GET /dapi/v1/allForceOrders GET /dapi/v1/forceOrders GET /dapi/v1/aggTrades.
New endpoint GET /dapi/v1/commissionRate to get user commission rate.
Websocket Request for user data: <listenKey>@account request for binance cryptocurrency exchange
cómo vender por dinero en efectivo user's account information <listenKey>@balance request for user's account balance <listenKey>@balance request for user's position information.
New endpoint GET /dapi/v1/adlQuantile to get the positions' ADL quantile estimation values.
New endpoint GET /dapi/v1/forceOrders to get the user's force orderes.
COIN MARGINED PERPETUAL FUTURES.
New contract type ("contractType") PERPETUAL for coin margined perpetual futures countract.
New fields in the reponse to endpoint GET /dapi/v1/premiumIndex :
lastFundingRate for når binance gif the lasted funding rate of the perpetual futures contract nextFundingTime for the next funding time of the perpetual futures contract.
New endpoint GET /dapi/v1/fundingRate to get funding rate history of perpetual futures.
New fields in the payload of WSS <symbol>@markPrice , <symbol>@[email protected]
, <pair>@markPrice , and <pair>@[email protected]
r for استعراض العام binance the lasted funding rate of the perpetual futures contract T for the next funding time of the perpetual futures contract.
New endpoints of coin margined futures trading data: GET /futures/data/openInterestHist GET /futures/data/topLongShortAccountRatio GET /futures/data/topLongShortPositionRatio GET /futures/data/globalLongShortAccountRatio GET /futures/data/takerBuySellVol GET /futures/data/basis.
Weights of endpoint GET /dapi/v1/income has been changed as 20.
Most of the endpoints can be also used in the testnet platform. The REST baseurl for testnet is "https://testnet.binancefuture.com" The Websocket baseurl for testnet is "wss://dstream.binancefuture.com"
General API Information.
The base endpoint is: https://dapi.binance cryptocurrency exchange
.com 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. All data types adopt definition in JAVA.
HTTP Return Codes.
HTTP 4XX return codes are used for 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 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 receiving 429 codes. HTTP 5XX return codes are used for internal errors; the issue is on binance cryptocurrency exchange
's side. HTTP 503 return code is used when: If there is an error message "Unknown error, please check your request or try again later." returned in the response, the API successfully sent the request but not get a response within the timeout period. It is important to NOT treat this as a failure operation; the execution status is UNKNOWN and could have been a success; If there is an error message "Service Unavailable." returned in the response, it means this is a failure API operation and the service might be unavailable at the moment, you need to retry later. If there is an error message "Internal error; unable to process your request. Please try again." returned in the response, it means this is a failure API operation and you can resend your request if you need.
Error Codes and Messages.
Any endpoint can return an ERROR.
The error payload is as follows:
Specific error codes and messages defined in Error Codes.
General Information on Endpoints.
For GET endpoints, parameters must be sent as a query string . For POST , PUT , and DELETE endpoints, the parameters may be sent as a query string or in the request body with content type application/x-www-form-urlencoded . You may mix parameters between both the query string and request body if you wish to do so. Parameters may be sent in any order. If a parameter sent in both the query string and request body , the query string parameter will be used.
The /dapi/v1/exchangeInfo rateLimits array contains objects related to the exchange's RAW_REQUEST , REQUEST_WEIGHT , and ORDER rate limits. These are further defined in the ENUM definitions section under Rate limiters (rateLimitType) . A 429 will be returned when either rate limit is violated.
Every request will contain X-MBX-USED-WEIGHT-(intervalNum)(intervalLetter) in the response headers which has the current used weight for binance-støtte
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 heavier weight . 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 . The limits on the API are based on the IPs, not the API keys.
Order Rate Limits.
Every order response will contain a X-MBX-ORDER-COUNT-(intervalNum)(intervalLetter) header which has the current order count for the account for all order rate limiters defined. Rejected/unsuccessful orders are not guaranteed to have X-MBX-ORDER-COUNT-** headers in the response. The order rate limit is counted against each account .
Endpoint Security Type.
Each endpoint has a security type that determines the how you will interact with it. 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. TRADE and USER_DATA endpoints are SIGNED endpoints.
SIGNED (TRADE and USER_DATA) Endpoint Security.
SIGNED endpoints require an additional parameter, signature , to be sent in the query string or request body . Endpoints use HMAC SHA256 signatures. The HMAC SHA256 signature is a keyed HMAC SHA256 operation. Use your secretKey as the key and totalParams as the value for the HMAC operation. The signature is not case sensitive . Please make sure the signature is the end part of your query string or request body . totalParams is defined as the query string concatenated with the request body .
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 after timestamp the request is valid for. If recvWindow is not sent, it defaults to 5000 . If the server determines that the timestamp sent by the client is more than one second in the future of the server time, the request will also be rejected.
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.