Company records and fields a register may not publish
Answer in brief
A company record holds what the source register publishes, and registers publish different things. In a well-designed company data API a field the register does not publish is absent, not estimated. Your code should treat almost every field as optional, tell absent from unknown, and never fill a gap with a guess.
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 a record contains
The free CompanyRegistryAPI.com API returns a company in data. Only id,
object and lifecycle are required; every other field appears when
available. Its docs describe these fields:
| Field | What it holds |
|---|---|
id |
The permanent company ID |
lifecycle |
Whether this record is current |
name |
The name as the register publishes it |
country_code |
The address country, ISO 3166-1 alpha-2 |
company_status |
A category (active, inactive, unknown) and the register’s own wording |
company_type |
The register’s own type code or label |
legal_form |
The legal form as the register publishes it, in its own language |
branch |
true or false as the register classifies the record; absent when it does not |
as_of_date |
When the register was last observed, where known |
identifiers |
Registry identifiers the sources list |
classifications |
Current activity codes in their source scheme, codes kept verbatim |
register_check |
The check of this record with its register |
Why fields differ
Each register decides what it publishes. A register may leave out legal form, branches or activity codes, and some data is withheld by law or policy. The Finnish PRH’s open data, for example, says its company interface does not include private traders or companies’ email addresses and phone numbers.
An API that combines registers has two honest choices for a missing value: leave the field out, or mark it as unknown or restricted. CompanyRegistryAPI.com says it does not add, correct or infer facts: values are what the register published, or explicitly unknown, restricted or no longer current.
Model optional fields explicitly
In TypeScript, let the type say which fields can be missing:
type Company = {
id: string;
object: "company";
lifecycle: { status: string; canonical_id?: string; successor_ids?: string[] };
name?: string;
country_code?: string;
// An object; the OpenAPI document still allows the older plain string.
company_status?:
| { category: "active" | "inactive" | "unknown"; local_name?: string }
| string;
company_type?: string;
legal_form?: string;
branch?: boolean;
as_of_date?: string;
};
In Python, read with .get() and keep the absence visible:
legal_form = company.get("legal_form") # None means: not published
label = legal_form if legal_form is not None else "Not published by the register"
Do not fill gaps
Filling gaps creates facts nobody published:
- Do not translate
legal_forminto another country’s forms. - Do not map activity codes to another scheme unless the source does; the product keeps codes verbatim with no inferred crosswalk.
- Do not default
branchtofalse. Absent means the register does not classify the form. - Do not show an empty status as “active”.
Show the gap in the interface
Write “Not published by the register” rather than a dash, so users know the
gap is in the source, not in your software. Next to it, show the record’s
as_of_date and the attribution line.
Read the record with its date
A record is a snapshot of what the register said when it was last observed. The provenance and observation times guide covers how to keep that date with every fact you store.
Questions and answers
Why is legal_form missing for some companies?
Because the register behind that record does not publish it, or the API has no value for it. A field the register does not publish is absent, never estimated, in CompanyRegistryAPI.com's docs.
Should I store absent fields as null?
Store them as absent or null, but keep the meaning "not published" separate from "published as empty". Never replace them with a default such as "Ltd" or "active".
Is company_type the same across countries?
No. CompanyRegistryAPI.com describes company_type as the register's own type code or label, so values differ between registers. Compare types only within one register.
Sources for this entry
- CompanyRegistryAPI.com API docs
- CompanyRegistryAPI.com OpenAPI document
- About CompanyRegistryAPI.com
- CompanyRegistryAPI.com Company Data API
- About the PRH open data service
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
- Provenance and observation times (Guide)
- Status and lifecycle (Guide)
- Identifiers and jurisdictions (Guide)
- Store permanent IDs (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. “Company records and fields a register may not publish.” Content reviewed . https://bestcompanydataapi.com/company-records-and-missing-fields