Officers data and its sources in company APIs
Answer in brief
Officers data lists the people and entities a register names in roles such as board member or managing director. A good company data API returns only what the register publishes, with each officer's source system and observation time. Officers are personal data from public records, so fetch them only when needed, show their source and keep them no longer than you need.
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 the endpoint returns
GET /v1/companies/{company_id}/officers
The free CompanyRegistryAPI.com API returns current officers where the register publishes them, up to 100 per call. The docs and the OpenAPI document describe the response like this:
| Field | Meaning |
|---|---|
object |
company_officer_list |
requested_company_id |
The ID in the request, kept when it redirects |
company_id |
The canonical company whose officers these are |
data[].name |
The officer as the register names them |
data[].roles |
Role titles as the register states them; absent when it states none |
data[].appointed_on |
Where the register states it |
data[].source.system |
The publishing system (always present) |
data[].source.url |
Its URL, when known |
data[].source.observed_at |
When it was observed, when known |
has_more |
Whether the register lists more current officers |
attribution |
“Powered by Coragrid” |
Read it with the source
import requests
BASE = "https://api.companyregistryapi.com"
def current_officers(company_id):
url = f"{BASE}/v1/companies/{company_id}/officers"
page = requests.get(url, timeout=10).json()
rows = []
for officer in page["data"]:
source = officer["source"]
rows.append({
"roles": officer.get("roles", []),
"appointed_on": officer.get("appointed_on"),
"source_system": source["system"],
"source_url": source.get("url"),
"observed_at": source.get("observed_at"),
})
return page["company_id"], rows, page["has_more"]
Return the canonical company_id with the rows: if the ID you passed was
redirected, the officers belong to the canonical record.
Roles are the register’s words
Role titles differ by register and language. Show them as published and do not map them to one vocabulary unless your product needs it. If it does, keep the original title next to your mapped role.
Officers are personal data
Officer names identify people. CompanyRegistryAPI.com’s privacy policy notes that personal data from public records, such as the names and roles of a company’s officers, is available to anyone who looks up the company. In your own product:
- Fetch officers only on the screens that need them.
- Show the source and observation time next to each.
- Do not keep them longer than your purpose needs, and refresh before showing them as current.
- Do not combine them into profiles of people.
Some registers restrict personal identifiers further. The Brønnøysund Register Centre’s open data API, for example, protects the role endpoints that include personal identification numbers with Maskinporten authentication.
When the list is incomplete
has_more: true means the register lists more current officers than the call
returned. Tell the user the list is partial, and link to the register for the
full record.
Questions and answers
Why are some companies returned without officers?
Because not every register publishes officers, and the API returns them only where the register does. An empty list means none were published in that source, not that the company has no officers.
How many officers does one call return?
Up to 100 in CompanyRegistryAPI.com's free API. has_more says when the register lists more current officers than returned.
Does the website show officers too?
CompanyRegistryAPI.com's llms.txt says its website's company pages do not list officers; current officers come from the API.
Sources for this entry
- CompanyRegistryAPI.com API docs
- CompanyRegistryAPI.com OpenAPI document
- CompanyRegistryAPI.com llms.txt
- CompanyRegistryAPI.com Privacy Policy
- Documentation for Open Data from the Central Coordinating Register for Legal Entities
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
- The first three requests (Guide)
- Provenance and observation times (Guide)
- Status and lifecycle (Guide)
- Caching company data (Guide)
- Best company data API (Category 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. “Officers data and its sources in company APIs.” Content reviewed . https://bestcompanydataapi.com/officers-and-their-sources