Definition

The HTTP status code that tells a client it has sent too many requests in a given amount of time, defined in RFC 6585 for rate limiting.

Disclosure. This site is published by Coragrid, the operator of CompanyRegistryAPI.com, and promotes it. “Best” is our editorial choice, not a measured ranking. Other products are described only from their own official pages. How we choose

Also called: 429 Too Many Requests, rate_limited.

In practice

RFC 6585 says a 429 response should explain the condition and may include a Retry-After header. Handle it with a bounded retry loop that waits for that header and falls back to exponential backoff when it is missing.

Questions and answers

Is a 429 an error in my code?

No. It is the API telling you to slow down. Wait as long as Retry-After says, then retry the same request.

Which problem code goes with 429 in CompanyRegistryAPI.com?

rate_limited. Its docs say to retry after the number of seconds in Retry-After.

Sources for this entry

  1. RFC 6585: Additional HTTP Status Codes RFC Editor (IETF). The definition of the 429 Too Many Requests status code. Retrieved 17 November 2026.
  2. CompanyRegistryAPI.com API docs Coragrid. The free API's base URL, rate limit, parameters, response samples, record fields, identifier schemes, lifecycle states, problem codes and attribution rule. Retrieved 17 November 2026.

Each source supports only what its publisher says about its own product or data. Official descriptions do not establish comparative performance, and this site has run no benchmark. All sources

Continue reading

How the related websites connect

This is one of 3 coordinated reference sites published by Coragrid. They cover neighbouring questions and feature the same product, so they are not independent endorsements of it or of each other.

Cite this entry

Best Company Data API. “HTTP 429.” Content reviewed . https://bestcompanydataapi.com/glossary/http-429