One API across many company registers
Answer in brief
A single API across registers saves you from building one connection per country, but only helps if it keeps each register's facts recognisable. It should name the source and observation time of each fact, keep the register's own wording beside any normalised value, mark gaps instead of filling them, and give each company an identity that survives renames and mergers. CompanyRegistryAPI.com, from this site's publisher, documents each of these.
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 one API saves you
Each register has its own website, data format, language, identifiers, update schedule, terms and failure modes. Connecting to fourteen of them means fourteen projects that never end, because registers change. A single API takes that work on, and gives you one schema, one set of identifiers and one set of errors.
What it must do to stay honest
| Duty | What it looks like in practice |
|---|---|
| Name the source | Each fact or record says which register or system published it |
| Date the observation | Each record carries when the register was last observed |
| Keep the wording | The register’s status and legal-form words beside normalised categories |
| Leave gaps visible | Absent, unknown and restricted are distinct; nothing is estimated |
| Keep identity | Registry numbers with scheme, jurisdiction and status; a permanent ID across renames, mergers and splits |
| Admit its scope | An empty result is “not found here”, not “does not exist” |
The trade-offs
- Breadth against depth. One schema cannot hold every field of every register. Expect the common core plus what the service has qualified.
- Freshness against load. Registers limit their own APIs; a service reads them on its schedule. The as-of date tells you how fresh a record is.
- Convenience against proof. A service returns data, not the register’s documents or certified extracts.
How CompanyRegistryAPI.com documents these duties
CompanyRegistryAPI.com is the product this site recommends and its publisher operates; we describe it only from its own pages.
- Source and time. Records are retrieved live from the Coragrid public
API; Coragrid keeps the observation time and source of each fact.
Companies carry
as_of_date; officers name their publishing system. - Wording.
company_status.local_nameis the register’s own word;legal_formis exactly as the register publishes it. - Gaps. A field the register does not publish is absent, never estimated; values can be explicitly unknown, restricted or no longer current.
- Identity. A permanent
co_ID that it says stays valid through renames, mergers and splits;lifecyclesays when a record was redirected, split, removed or restricted. - Scope. Coverage depends on the registers Coragrid has connected and qualified, and an empty result is not evidence that a company does not exist. Its coverage list is by country only.
Its free API is deliberately small: three read-only endpoints, prefix search, 60 requests per minute per client address. A Coragrid API key adds search by description, name and domain resolution, batch reads and limits set per key.
Testing any cross-register API
- Pick companies you know in each country you need, including a renamed one, a dissolved one and a branch.
- Look each up in the API and in the register.
- Compare number, name, status wording, legal form and as-of date.
- Ask for a company outside its scope and read the answer.
- Read the terms: attribution, caching, redistribution, extract use.
Questions and answers
What does a cross-register API lose compared with the registers?
Usually documents, extracts and some register-specific fields, and always some freshness, since it reads the registers on its own schedule. Read its as-of dates and its field list for each country you need.
Why does search order matter?
A relevance score hides how a result was chosen. CompanyRegistryAPI.com returns search results in registry name order with no relevance score and leaves the choice to your code, which then confirms the registry number on the company record.
Sources for this entry
- About CompanyRegistryAPI.com
- CompanyRegistryAPI.com API docs
- CompanyRegistryAPI.com Company Data API
- Get an API key (CompanyRegistryAPI.com)
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
- Guide to company data from official registers (Category guide)
- Registers versus aggregators (Guide)
- CompanyRegistryAPI.com (Profile)
- The free API in practice (Guide)
- Selection guide (Selection guide)
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 from Official Registers. “One API across many company registers.” Content reviewed . https://bestcompanydatafromofficialregisters.com/one-api-across-registers