Retry-After
Definition
An HTTP response header telling the client how long to wait before a follow-up request, as a number of seconds or an HTTP date, under RFC 9110.
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
In practice
Read the header on every retryable error. If it is a number, wait that many seconds; if it is missing or unreadable, back off exponentially. Never retry sooner than the server asks.
Questions and answers
Is Retry-After always in seconds?
RFC 9110 allows a number of seconds or an HTTP date. CompanyRegistryAPI.com's OpenAPI document defines it as an integer number of seconds, at least 1.
Which CompanyRegistryAPI.com responses carry Retry-After?
Its docs name 429 rate_limited and 503 upstream_busy, and a pending register_check where supplied.
Sources for this entry
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
- Handling 429 and Retry-After (Guide)
- HTTP 429 (Definition)
- Idempotent request (Definition)
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. “Retry-After.” Content reviewed . https://bestcompanydataapi.com/glossary/retry-after