Search Results
  1. HTTP (Hypertext Transfer Protocol)
  1. HTTP Status Codes
  1. 429 Too Many Requests
    1. Writing responses (origin servers)
    2. Reading responses (user agents)
    3. Overview table
    4. Example

429 Too Many Requests

The 429 Too Many Requests HTTP status code indicates request was not filled and that the client exceeded request limits, and should retry its request at a later time.

Writing responses (origin servers)

Servers may respond with 429 Too Many Requests at any time during handling. For performance, this may be tested as early as possible, as soon as the user is authenticated.

Reading responses (user agents)

The client has been making too many requests recently. This might be calculated based on the authenticated user, IP address, or some other mechanism. It does not imply the existence of the resource, but the error might not apply to another resource. However, the error is typically applied to all requests to that authority.

This request may be re-tried after a period of time; increase the duration between re-requests if the Too Many Requests error persists. Consider techniques like using a shared cache, observing caching headers, and exponential backoff.

A specific wait time may be listed in the Retry-After response header.

Overview table

Name
429
Message
429 Too Many Requests
Description
The client has exceeded request limits
Specification
RFC 6585: Additional HTTP Status Codes ยง3. 429 Too Many Requests

Example

HTTP/1.1 429 Too Many Requests
Retry-After: 2829
Content-Type: text/plain

Clients on the free plan are limited to 2000 requests per hour.
Try again next hour.