So we are a couple of days away from the new 100K rate limit per app rule, but I don’t believe I have seen documentation or a question about two aspects:
- What is the response we expect to receive if the rate limit is hit (contrasted with the regular 15 minutes window user-auth limits and app-auth limits)
- Is there a way to read the parameters surrounding this limit (e.g. header, application/rate_limit_status endpoint) to play nicely with the API?
Thanks
1 Like
johnd
#2
Hey @Connexinet,
- If your app exceeds the 100,000 request limit in a 24-hour window, the API will return a
429 Too Many Requests error.
- When this limit goes live tomorrow (6/19), the response headers will not include additional header information for the new 24-hour request limit. This is known by our team and we’re working on a fix, so please stay tuned.
Docs will be updated to reflect the new limit as it goes into effect tomorrow. Thanks for your patience.
1 Like
That would be great, thanks @johnd!
Regarding (1) can we expect the response body with 429 code to be different so we can distinguish it from user-auth limits with 429 response which is normally like this
{“errors”:[{“message”:“Rate limit exceeded”}]}
system
Closed
#4
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.