REST API Rate limits

• The /api/v1/exchangeInfo rateLimits array contains object related to the exchange's REQUEST_WEIGHT rate limits.

• A 429 will be returned when rate limit is violate

• 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 ban (HTTP status 418).

Limits are enforced by IP Address for public endpoints, and by both IP Address and Account for private endpoints. Please take note of the RateLimit-Remaining header to track points usage.

Response Headers

Field	Description
RateLimit-Remaining	Points remaining in the time window.
RateLimit-Reset	Timestamp that the time window ends, in Epoch milliseconds.
Retry-After	Milliseconds until the next time window. Header included only when the limit has been reached.
RateLimit-Limit	The maximum amount of points allowed per time window.

It is strongly recommended to use WebSocket stream for getting data as much as possible, which can not only ensure the timeliness of the message, but also reduce the access restriction pressure caused by the request.