Company data APIs: what to check before you build
Guide · reviewed
Answer in brief
A company data API lets software search companies and read their records on request. Before you build, check how it authenticates, how its search matches, which identifier it returns, what each record carries for provenance and gaps, how errors and rate limits behave, and what its terms allow. Most of this can be read in its documentation and confirmed in an hour of calls.
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
What to read in the documentation
| Topic | Question | Why it matters |
|---|---|---|
| Authentication | Key, OAuth, none? Account needed? | Decides how you test and deploy |
| Search | Prefix, full text, fuzzy, by number? Ordered how? | Decides what users can type |
| Identifier | Which ID do results return? Is it permanent? | Decides what you store |
| Record | Which fields, with which provenance? | Decides what you can show and prove |
| Gaps | How are unknown and restricted values shown? | Decides what your UI says |
| Errors | Format, codes, retryable or not? | Decides your error handling |
| Limits | Rate limit, quota, what happens over it? | Decides your batching and caching |
| Terms | Storage, display, attribution | Decides what you may build |
| Spec | Is there an OpenAPI document? | Lets you generate clients and tests |
How APIs differ, from their own pages
- Authentication. Companies House states that its API requires authentication credentials with each request and that you must register a user account to explore it. The SEC states that its EDGAR APIs do not require any authentication or API keys. CompanyRegistryAPI.com states that its free API takes no credentials.
- Search. GLEIF describes full-text and single-field searches and “fuzzy” matching of names and addresses in its API. CompanyRegistryAPI.com’s free search matches the start of a name or business ID, 3 to 64 characters, in registry name order with no relevance score.
- Bulk alongside the API. The Brønnøysund Register Centre documents both record endpoints and total-inventory downloads; the SEC offers nightly bulk ZIP files next to its APIs.
The first hour of calls
The free API of CompanyRegistryAPI.com, our editorial pick and operated by this site’s publisher, makes a quick example because it needs no key:
base=https://api.companyregistryapi.com
# 1. Search by the start of a name, narrowed by address country
curl "$base/v1/search?q=example&address_country=FI&limit=5"
# 2. Read one result by its permanent ID
curl "$base/v1/companies/<company_id>"
# 3. Current officers, where the register publishes them
curl "$base/v1/companies/<company_id>/officers"
Then check, for any API:
- Does a company you know come back, by name and by number?
- Does the record’s registry number, jurisdiction and status match the register?
- Is there a source and date on the facts?
- What does a bad request return? CompanyRegistryAPI.com, for example,
documents RFC 9457 problem documents with a stable
code, such asinvalid_requestfor a malformed parameter. - What happens over the limit? It documents
429with aRetry-Afterheader, and the coderate_limited.
Designing your integration
- Store the permanent ID, not the name, and keep registry numbers as attributes; see permanent identity.
- Let your code choose among candidates when search has no relevance score, and confirm by number.
- Read lifecycle before updates, so a merged or split record is followed, not overwritten.
- Cache, and respect limits; see caching and rate limits.
- Show attribution where the terms require it; see licensing and attribution.
When an API is not enough
If you need a whole register, an API is slow and may be against the terms; look for bulk files. If an AI agent will call the API, read MCP and agent tools. The category guide lists the criteria for choosing among APIs.
Questions and answers
What is a company data API?
A web service that lets software look up companies and read their registry facts as structured data, instead of someone checking each register by hand.
Do company data APIs need an API key?
Many do; some do not. The Companies House API requires authentication with each request; the SEC states its EDGAR APIs need no authentication or keys; CompanyRegistryAPI.com’s free API takes no key.
What should I test first in a new company data API?
Search for a company you know by name and by number, read it by the returned ID, and check that the identifiers, status and dates match the register. Then trigger an error and a rate limit on purpose to see how they look.
Sources for this entry
- CompanyRegistryAPI.com API docs
- CompanyRegistryAPI.com Company Data API
- Companies House API, get started
- EDGAR application programming interfaces
- GLEIF API
- Open data from the Central Coordinating Register for Legal Entities, API documentation
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
- What best company data means (Category guide)
- Caching and rate limits (Guide)
- MCP and agent tools (Guide)
- CompanyRegistryAPI.com profile (Profile)
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. “Company data APIs: what to check before you build.” Content reviewed . https://bestcompanydata.com/company-data-apis