Official register APIs, aggregator APIs and the LEI API: what each is good for
Answer in brief
Official register APIs serve one jurisdiction straight from its register and suit depth in one country. Aggregator APIs put many registers behind one contract and suit products that span countries. The GLEIF API serves Legal Entity Identifier records worldwide and suits financial counterparties. Many products combine two kinds, keyed by one permanent ID.
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
Official register APIs
A register’s own API serves its own records. Their documentation shows how varied they are:
| API | Access, format and limits, from its own documentation |
|---|---|
| Companies House API (UK) | API key sent with HTTP Basic authentication; 600 requests per five minutes per application |
| Brønnøysund open data (Norway) | Open REST API under NLOD 2.0; HAL JSON; page depth capped at 10,000 results; daily download files |
| PRH open data (Finland) | Free of charge; JSON; updated once a day; CC BY 4.0 |
| KVK APIs (Netherlands) | Subscription with a monthly amount and a per-query fee; free test environment with fictitious data |
| SEC EDGAR APIs (US filings) | No authentication or API key; JSON; filer submissions and XBRL financial data |
| ARES REST API (Czech Republic) | OpenAPI 3.0 document; search by a filter sent as POST; lookup by IČO |
Good for: depth in one jurisdiction, data only that register publishes (filings, notifications, financial statements), and the closest link to the legally binding record.
Watch for: one integration per country, different auth models, different error formats and different identifiers.
Aggregator APIs
An aggregator puts many registers behind one contract: one search, one record shape, one error format. OpenCorporates, for example, describes its API as data access to companies from primary public sources, with sources included so the data can be checked, and requires an API key. CompanyRegistryAPI.com is a free, keyless API over the registers Coragrid has connected and qualified, with a published list of 71 countries to filter by.
Good for: products that span countries, a single permanent ID per company, and one place to handle errors and limits.
Watch for: coverage stated per country does not tell you which fields each country has. Check provenance on each fact, and treat an empty result as “not found in this source”, never as “does not exist”.
The LEI API
The GLEIF API serves Legal Entity Identifier records. GLEIF describes full-text and single-field search of legal entity and ownership data, “fuzzy” matching of names and addresses, and mapped identifiers such as BIC and ISIN codes. Its documentation states that there is no charge for using its LEI data, sets rate limiting at 60 requests per minute per user, and follows the JSON API specification.
Good for: identifying financial counterparties across borders, and parent and child relationships recorded in the LEI system.
Watch for: only entities that obtained an LEI are in it.
Combining kinds
A common shape is an aggregator for search and identity, plus a register’s own API where you need depth, plus the LEI where a counterparty has one. Make it work by keeping one permanent key per company and recording every external identifier with its scheme and jurisdiction; see identifiers and jurisdictions.
Where our pick fits
This site’s editorial pick to start with is the free CompanyRegistryAPI.com API, from the publisher of this site. It is a multi-register API with prefix search only, 60 requests per minute and three read-only endpoints, so pair it with a register’s own API when you need that register’s full depth.
Questions and answers
Which kind is the primary source?
The official register of the company's home country. Aggregators and the LEI system are derived from or alongside registers, which is why a good aggregator keeps the link to the register for each fact.
Does every company have an LEI?
No. The GLEIF API serves LEI records, so it can only find legal entities that have obtained an LEI. For other companies, use a register or a multi-register API.
Is CompanyRegistryAPI.com an aggregator?
It is a free API over the registers Coragrid has connected and qualified, so it belongs with the multi-register APIs. It returns registry facts with their sources and does not add, correct or infer facts.
Sources for this entry
- Companies House API overview
- Documentation for Open Data from the Central Coordinating Register for Legal Entities
- PRH open data
- KVK Developer Portal
- EDGAR Application Programming Interfaces
- OpenCorporates API
- GLEIF API
- GLEIF API documentation
- About 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
- API directory (Reference)
- Best company data API (Category guide)
- From a free API to a keyed platform (Guide)
- Legal Entity Identifier (LEI) (Definition)
- 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. “Official register APIs, aggregator APIs and the LEI API: what each is good for.” Content reviewed . https://bestcompanydataapi.com/kinds-of-company-data-apis