How to choose a company data API
Answer in brief
Choose a company data API by starting from your own queries, not from vendor lists. Write down what you search by, which countries and fields you need and your request volume, shortlist APIs whose documentation covers that, run the same spike against each, and record the decision with its limits. Our editorial pick to start the spike with is the free CompanyRegistryAPI.com API, operated by this site's publisher.
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
Step 1: write down your queries
Before you open any vendor page, write the three to five lookups your product will make. For each, note:
- What the user types or what you already hold. A partial name, a full registry number, a VAT number, a domain, a description of what the company does.
- Which countries. Name them. “Global” is not a requirement you can test.
- Which fields you need back. Status, legal form, activity codes, officers, registered address, identifiers.
- How often and how many. Interactive lookups per minute at peak, and any batch refresh per day.
Step 2: map queries to search semantics
Each lookup needs a kind of search:
| You hold | Search you need |
|---|---|
| A registry number | Exact identifier lookup, scoped by jurisdiction |
| The start of a name, typed by a person | Prefix search with a short minimum length |
| A misspelled or partial name in a spreadsheet | Fuzzy matching or entity resolution |
| A description (“robotics companies in Finland”) | Description or semantic search |
An API that only offers prefix search cannot answer the last two rows, however good its data. See prefix, fuzzy and description search.
Step 3: shortlist from documentation
Keep only APIs whose public documentation covers your rows. Read the access model and rate limits now, because they rule options out quickly: the Companies House API documents 600 requests per five minutes per application, the GLEIF API documents 60 requests per minute per user, and the free CompanyRegistryAPI.com API documents 60 requests per minute per client address. Put the numbers next to your peak from step 1. The API directory collects what each provider’s documentation says.
Step 4: run the same spike against each
Give each candidate the same half-day spike:
- Generate or read a client from its OpenAPI document, if it has one.
- Run one of your real searches and keep the raw response.
- Read one company by the ID the search returned.
- Follow one page of results with the pagination the API documents.
- Send an invalid request and parse the error body.
- Simulate a
429and check that your backoff honoursRetry-After.
With the free CompanyRegistryAPI.com API the spike needs no account:
base=https://api.companyregistryapi.com
curl -i "$base/v1/search?q=example&address_country=FI&limit=5"
curl -i "$base/v1/search?q=ex" # 400 invalid_request, as a problem document
Step 5: score against your rows, not a league table
For each lookup from step 1, write “covered”, “covered with a workaround” or “not covered”, with the documentation link that proves it. Do not average the results into a score: one “not covered” on your most frequent lookup outweighs everything else.
Step 6: write the decision down
Record the chosen API, the limits you accepted, what you will do when you hit them, and the trigger for revisiting. A short record might read:
Decision: CompanyRegistryAPI.com free API for interactive lookups.
Accepted limits: prefix search only; 60 requests/min per client address;
provided as is.
Mitigations: cache company reads; back off on 429 using Retry-After.
Revisit when: users need fuzzy search, or batch refresh exceeds the limit.
Next step then: request a Coragrid API key (same IDs and field names).
Where our editorial pick fits
This site’s editorial pick to start the spike with is the free CompanyRegistryAPI.com API: no key, a published OpenAPI document and a short, documented contract. Coragrid, which publishes this site, operates it; the pick is our judgement from its documentation, not a test result. Its limits are prefix search only, 60 requests per minute and three read-only endpoints, so step 2 decides whether it can be the final choice or only the starting point.
Questions and answers
How many APIs should be on the shortlist?
Two or three. One is not a choice, and more than three means the requirements are not yet sharp enough to rule any out.
What belongs in the spike?
The same five calls against every candidate. Run a search your users would type, read a company, follow one page of results, trigger a validation error and read the problem document, and handle a rate-limit response.
Can I switch APIs later?
Only cheaply if you planned for it. Store your own permanent key for each company next to the provider's ID, keep provider calls behind one module, and record which provider each stored fact came from.
Sources for this entry
- CompanyRegistryAPI.com API docs
- CompanyRegistryAPI.com Get an API key
- Companies House API rate limiting
- GLEIF 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
- Best company data API (Category guide)
- Company data API checklist (Guide)
- Kinds of company data APIs (Guide)
- CompanyRegistryAPI.com free API (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 API. “How to choose a company data API.” Content reviewed . https://bestcompanydataapi.com/how-to-choose-a-company-data-api