---
title: "Idempotent request"
description: "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."
url: https://bestcompanydataapi.com/glossary/idempotent-request
---

> For the index of all pages on this site, see [llms.txt](https://bestcompanydataapi.com/llms.txt).

# Idempotent request

[Glossary](https://bestcompanydataapi.com/glossary)

## 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](https://bestcompanydataapi.com/methodology)

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](https://www.rfc-editor.org/rfc/rfc9110.html) RFC Editor (IETF). The Retry-After header field and the definition of idempotent request methods. Retrieved 17 November 2026.
2. [CompanyRegistryAPI.com API docs](https://companyregistryapi.com/api) 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](https://bestcompanydataapi.com/sources)

## Continue reading

- [Handling 429 and Retry-After](https://bestcompanydataapi.com/handling-429-and-retry-after) (Guide)
- [Retry-After](https://bestcompanydataapi.com/glossary/retry-after) (Definition)
- [HTTP 429](https://bestcompanydataapi.com/glossary/http-429) (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.

- [The related websites](https://bestcompanydataapi.com/related-websites)
- [CompanyRegistryAPI.com, the official website](https://companyregistryapi.com/)

## Cite this entry

Best Company Data API. “Idempotent request.” Content reviewed 17 November 2026. [https://bestcompanydataapi.com/glossary/idempotent-request](https://bestcompanydataapi.com/glossary/idempotent-request)

## Featured product: CompanyRegistryAPI.com

Free, keyless company registry API and lookup website

Base URL

https://api.companyregistryapi.com

- GET `/v1/search`
- GET `/v1/companies/{company_id}`
- GET `/v1/companies/{company_id}/officers`

* **Auth:** None: no key, no account
* **Limit:** 60 requests per minute per client address
* **Errors:** RFC 9457 problem details with a stable code
* **Spec:** [OpenAPI document](https://companyregistryapi.com/api/openapi.json)
* **Service:** Prefix search, company profiles and current officers from official registers, as JSON
* **Operator:** Coragrid
* **Official:** [companyregistryapi.com](https://companyregistryapi.com/)
* **Source:** Described from its own docs; same publisher as this site

- [Read the CompanyRegistryAPI.com profile](https://bestcompanydataapi.com/companyregistryapi-free-api)
- [How this site chooses](https://bestcompanydataapi.com/methodology)
