12/24/2023 0 Comments Binance spot api![]() TRADE | Endpoint requires sending a valid API-Key and signature. * By default, API-keys can access all secure routes. * API-keys can be configured to only access certain types of secure endpoints.įor example, one API-key could be used for TRADE only, while another API-keyĬan access everything except for TRADE routes. * API-keys and secret-keys **are case sensitive**. * API-keys are passed into the Rest API via the `X-MBX-APIKEY` * If no security type is stated, assume the security type is NONE. This is stated next to the NAME of the endpoint. ![]() * Each endpoint has a security type that determines the how you will * **The order rate limit is counted against each account**. ![]() * Rejected/unsuccessful orders are not guaranteed to have `X-MBX-ORDER-COUNT-**` headers in the response. * Every successful 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. * **The limits on the API are based on the IPs, not the API keys.** * 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. * IP bans are tracked and **scale in duration** for repeat offenders, **from 2 minutes to 3 days**. * **Repeatedly violating rate limits and/or failing to back off after receiving 429s will result in an automated IP ban (HTTP status 418).** * When a 429 is received, it's your obligation as an API to back off and not spam the API. Heavier endpoints and endpoints that do operations on multiple symbols will have a heavier `weight`. * Each route has a `weight` which determines for the number of requests each endpoint counts for. * 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. * A 429 will be returned when either rate limit is violated. These are further defined in the `ENUM definitions` section under `Rate limiters (rateLimitType)`. * The `/api/v3/exchangeInfo` `rateLimits` array contains objects related to the exchange's `RAW_REQUEST`, `REQUEST_WEIGHT`, and `ORDER` rate limits. For example, `intervalNum` 5 with `intervalLetter` M means "Every 5 minutes". * `intervalNum` describes the amount of the interval. * The following `intervalLetter` values for headers: * If a parameter sent in both the `query string` and `request body`, the `query string` and `request body` if you wish to do so. `query string` or in the `request body` with content type * For `POST`, `PUT`, and `DELETE` endpoints, the parameters may be sent as a * For `GET` endpoints, parameters must be sent as a `query string`. * Specific error codes and messages are defined in (./errors.md). **UNKNOWN** and could have been a success. It is important to **NOT** treat this as a failure operation the execution status is * HTTP `5XX` return codes are used for internal errors the issue is on * HTTP `418` return code is used when an IP has been auto-banned for continuing to send requests after receiving `429` codes. * HTTP `429` return code is used when breaking a request rate limit. * HTTP `403` return code is used when the WAF Limit (Web Application Firewall) has been violated. ![]() * HTTP `4XX` return codes are used for malformed requests * All time and timestamp related fields are in **milliseconds**. * Data is returned in **ascending** order. * All endpoints return either a JSON object or array. * If there are performance issues with the endpoint above, these API clusters are also available: (#keepalive-user-data-stream-user_stream) (#cancel-all-open-orders-on-a-symbol-trade) (#example-3-mixed-query-string-and-request-body) (#signed-endpoint-examples-for-post-apiv3order) (#signed-trade-and-user_data-endpoint-security) **Table of Contents** *generated with ()* ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |