Skip to content

Too many requests

HTTP 429rate_limited

When the API answers 429 rate_limited, and how to fix it.

Version v1.1, updated

The type field of every rate_limited response links to this page.

On this page

More requests arrived than a limit allows. limit_scope names the limit reached, and Retry-After gives the seconds to wait.

At a glance

  • Status: 429 Too Many Requests

  • Code: rate_limited

  • Retry: Yes, after the Retry-After seconds.

Causes and fixes

Likely cause

How to fix it

limit_scope is key: this key sent too many requests.

Wait the Retry-After seconds, then send fewer requests per minute.

limit_scope is company: all the keys of the company together sent too many.

Spread the work of your systems over time. More keys do not raise the company limit.

limit_scope is ip: too many requests came from one network address.

Wait the Retry-After seconds and slow down.

Example

429 rate_limitedJSON
{
  "code": "rate_limited",
  "detail": "The rate limit has been reached. Retry after the number of seconds in Retry-After.",
  "instance": "/v1/categories",
  "limit_scope": "key",
  "request_id": "a1b2c3d4-0000-4000-8000-0000000000ee",
  "status": 429,
  "title": "Too many requests",
  "type": "https://birp.io/developers/errors/rate_limited"
}

Related

  • rate-limits
  • handling-errors
  • pagination-and-filtering