---
title: "Official register, aggregator and LEI APIs compared"
description: "The three kinds of company data API, official register APIs, multi-register aggregator APIs and the GLEIF LEI API, with what each is good for and what to check."
url: https://bestcompanydataapi.com/kinds-of-company-data-apis
---

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

# Official register APIs, aggregator APIs and the LEI API: what each is good for

[API landscape](https://bestcompanydataapi.com/topics/landscape)

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

## 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](https://bestcompanydataapi.com/resources/companies-house-api) (UK) | API key sent with HTTP Basic authentication; 600 requests per five minutes per application |
| [Brønnøysund open data](https://bestcompanydataapi.com/resources/brreg-open-data-api) (Norway) | Open REST API under NLOD 2.0; HAL JSON; page depth capped at 10,000 results; daily download files |
| [PRH open data](https://bestcompanydataapi.com/resources/prh-open-data-api) (Finland) | Free of charge; JSON; updated once a day; CC BY 4.0 |
| [KVK APIs](https://bestcompanydataapi.com/resources/kvk-api) (Netherlands) | Subscription with a monthly amount and a per-query fee; free test environment with fictitious data |
| [SEC EDGAR APIs](https://bestcompanydataapi.com/resources/sec-edgar-apis) (US filings) | No authentication or API key; JSON; filer submissions and XBRL financial data |
| [ARES REST API](https://bestcompanydataapi.com/resources/ares-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](https://bestcompanydataapi.com/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

1. [Companies House API overview](https://developer.company-information.service.gov.uk/) Companies House. Companies House's own description of what its API returns and which companies it covers. Retrieved 17 November 2026.
2. [Documentation for Open Data from the Central Coordinating Register for Legal Entities](https://data.brreg.no/enhetsregisteret/api/dokumentasjon/en/index.html) Brønnøysund Register Centre (Brønnøysundregistrene). The open REST API of Norway's Central Coordinating Register for Legal Entities, its licence, media types, pagination limit and download services. Retrieved 17 November 2026.
3. [PRH open data](https://avoindata.prh.fi/en) Finnish Patent and Registration Office (PRH). The interfaces PRH offers for company details in the Finnish Trade Register and the conditions for using the data. Retrieved 17 November 2026.
4. [KVK Developer Portal](https://developers.kvk.nl/) Netherlands Chamber of Commerce (KVK). How access to the KVK APIs is sold, what documentation they publish and the free test environment. Retrieved 17 November 2026.
5. [EDGAR Application Programming Interfaces](https://www.sec.gov/search-filings/edgar-application-programming-interfaces) U.S. Securities and Exchange Commission (SEC). What the data.sec.gov APIs deliver and that they need no authentication or API key, in the SEC's words. Retrieved 17 November 2026.
6. [OpenCorporates API](https://api.opencorporates.com/) OpenCorporates. OpenCorporates' own description of its API, its data and its licensing options. Retrieved 17 November 2026.
7. [GLEIF API](https://www.gleif.org/en/lei-data/gleif-api) Global Legal Entity Identifier Foundation (GLEIF). GLEIF's own description of what its API searches and the data it is based on. Retrieved 17 November 2026.
8. [GLEIF API documentation](https://api.gleif.org/docs) Global Legal Entity Identifier Foundation (GLEIF). The GLEIF API's request format, page-based pagination, charges and rate limit, as its documentation states them. Retrieved 17 November 2026.
9. [About CompanyRegistryAPI.com](https://companyregistryapi.com/about) Coragrid. Where the product's records come from, what it does not do with them, and the free API terms, including "provided as is". 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

- [API directory](https://bestcompanydataapi.com/directory) (Reference)
- [Best company data API](https://bestcompanydataapi.com/best-company-data-api) (Category guide)
- [From a free API to a keyed platform](https://bestcompanydataapi.com/from-free-api-to-keyed-platform) (Guide)
- [Legal Entity Identifier (LEI)](https://bestcompanydataapi.com/glossary/legal-entity-identifier) (Definition)
- [CompanyRegistryAPI.com free API](https://bestcompanydataapi.com/companyregistryapi-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.

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

## Cite this entry

Best Company Data API. “Official register APIs, aggregator APIs and the LEI API: what each is good for.” Content reviewed 17 November 2026. [https://bestcompanydataapi.com/kinds-of-company-data-apis](https://bestcompanydataapi.com/kinds-of-company-data-apis)

## 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)
