Overview
As part of our ongoing work to provide more detailed messaging from our API, we will be updating our responses to contain information regarding how close the caller is to reaching this limit in response headers.
Who will this affect?
This change will only affect users that are likely to exceed the API rate limit by providing them with greater feedback when this may occur.
Details
As described in a previous post, our API will limit the number of calls that a user can make in line with our rate limiting policy.
We will be updating our responses to contain information regarding how close the API caller is to reaching this limit in response headers, for example:
X-Rate-Limit-Remaining: 99 X-Rate-Limit-Reset: 2021-03-16T11:08:08.0232125Z
This message informs you that if you make more than another 99 requests before the specified time, you will be subject to rate-limiting. When the limit is exceeded, requests will then fail with HTTP 429, and there will be a response header letting you know how many seconds to wait until you will again be able to make requests, for example:
Retry-After: 15
Note that these are the standard headers recognised for HTTP rate limiting.