Definition

An HTTP request whose intended effect on the server is the same whether it is sent once or several times, which makes it safe to retry.

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: idempotent method.

In practice

RFC 9110 defines PUT, DELETE and the safe methods, such as GET, as idempotent. Retry them on documented transient errors; for other methods, check the API’s documentation before you retry automatically.

Questions and answers

Are company lookups idempotent?

Yes. Reading a company with GET is a safe method, and RFC 9110 counts safe methods as idempotent. All three free CompanyRegistryAPI.com endpoints are GET.

Why does idempotency matter for retries?

Because a retried idempotent request cannot do something twice. Requests that create or change data need more care before you retry them.

Sources for this entry

  1. RFC 9110: HTTP Semantics RFC Editor (IETF). The Retry-After header field and the definition of idempotent request methods. 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. “Idempotent request.” Content reviewed . https://bestcompanydataapi.com/glossary/idempotent-request