Status 429
Too many requests
too_many_requests
When it happens
The rate limit is exhausted; policy names the bucket — app, store or rejected — and Retry-After says how long to wait. rejected means too many requests from your address were rejected on entry: a missing, invalid, revoked or expired token, an address that is not allowed, a plan without the API.
What to do
Wait for Retry-After seconds. Spread requests evenly and use bulk operations for large volumes; the RateLimit header shows what is left. For rejected, fix the cause the earlier 401 or 403 named instead of repeating the request.
Can’t find the answer, or the error keeps coming back? Write to us and quote the X-Request-Id from the response so we can find the request. Contact us
Endpoints that return it
A common error: it is not tied to particular endpoints, and almost any call can return it.
Response body
application/problem+json · RateLimitProblem
typestringrequiredMachine type of the problem: a stable code to branch on, such as insufficient_scope. Every type has a page in the error catalog.
titlestringrequiredShort summary of the problem in the language of the request.
statusintegerrequiredHTTP status of the response.
detailstringExplanation of this occurrence in the language of the request.
policystringrequiredWhich bucket ran out: app — of the app; store — of the store, shared by all its apps; rejected — of requests from one address that were rejected on entry.
- Values:
appstorerejected