Second Layer Rate Limits Soft Release Now Live

*Please note additional routes are subject to second layer rate limits: POST /api/v1/order/bulk and PUT /api/v1/order/bulk. We have updated our blog and site announcement to reflect the full list of routes. 

Our second layer rate limits have been implemented through a soft release of the new limiter starting from 10 December 2020 at 23:00 UTC. Responses for the affected routes now include the x-ratelimit-remaining-1s header. Requests that exceed the limit will still be successful, but the value of the x-ratelimit-remaining-1s header will be 0. This means that orders will still go through and the status code for valid requests will be a 200, not a 429. 

On 15 December 2020 from 23:00 UTC, requests that breach the limit will be rejected with a 429 status code and a one hour ban will be levied if a large number of requests are rejected in a short period of time.

The new second layer rate limit on the number of requests that can be sent in a single second apply to the following routes:

  • POST /api/v1/order
  • POST /api/v1/order/bulk
  • PUT /api/v1/order
  • PUT /api/v1/order/bulk
  • DELETE /api/v1/order
  • DELETE /api/v1/order/all
  • POST /api/v1/position/isolate
  • POST /api/v1/position/leverage
  • POST /api/v1/position/transferMargin

For more information, please see our updated blog or contact Support with any questions.