/v2/company accepted a single catch-all datapoint called companyProfile and onboarding ran on its own /v2/onboarding endpoint. That model hid what you were actually buying (one companyProfile meant different things in different countries) and forced prefill and verification down two separate code paths.
The Data Product Model replaces companyProfile with explicit, named datapoints and folds /v2/onboarding into /v2/company as a mode. You now ask for exactly the sections you need, the billing and response shape match what you requested, and both retrieval modes share the same endpoint.
The companyProfile alias is deprecated and will stop accepting new requests on December 1, 2026 at 00:00 UTC. This guide shows you how to move to explicit datapoints. The legacy /v2/onboarding endpoint has a separate deprecation; its availability is unchanged by this cutoff.
The datapoints
A request toPOST /v2/company takes a dataPoints array. Each entry is one of the values below. Availability varies by country (see each country guide).
company, legalRepresentatives, otherKeyPersons, establishments, and subsidiaries are the datapoints introduced by the Data Product Model. shareholders, ultimateBeneficialOwners, availableDocuments, and graph pre-date it and have always been callable by name.What companyProfile means
Until its December 1 cutoff, companyProfile is a legacy alias for company + legalRepresentatives + otherKeyPersons + establishments, on a best-effort basis.
Best-effort means: each of the four expanded datapoints is included only if the country has a block covering it in the mode you requested. If a datapoint has no compatible block, it is silently dropped from the expansion. You are never billed for datapoints the country cannot deliver.
Concretely:
The same rule applies in prefill mode: the expansion is filtered against the country’s fast block. For Italy this means
companyProfile in prefill mode includes only company: the fast block covers nothing else, so legalRepresentatives, otherKeyPersons and establishments are all dropped.
Billing is one block per resolved bundle. Expansion never adds a separate catalog item.
Replace companyProfile
Swap companyProfile for the datapoints you actually need.
Check availability for each country and mode you use before choosing the replacement list. The alias silently omits unsupported datapoints; an explicit request does not. Keep any separately requested shareholders, ultimateBeneficialOwners, availableDocuments, graph, or document IDs.
companyalone if you only need the registration record.company+legalRepresentativesfor the classic KYB pair.- Add
otherKeyPersonswhen your compliance checks cover auditors or board members without signing authority. - Add
establishmentswhen you need branch offices. - Add
shareholders/ultimateBeneficialOwnersfor ownership checks.
Do not mix legacy and new names
Before the cutoff, you must pick one vocabulary within a request:- Legal:
["companyProfile"],["companyProfile", "shareholders"],["companyProfile", "ultimateBeneficialOwners", "availableDocuments"] - Legal:
["company", "legalRepresentatives"],["company", "shareholders", "ultimateBeneficialOwners"] - Rejected with HTTP 400:
["companyProfile", "company"],["companyProfile", "legalRepresentatives"],["companyProfile", "otherKeyPersons"],["companyProfile", "establishments"],["companyProfile", "subsidiaries"]
companyProfile cannot appear alongside any of the five new names (company, legalRepresentatives, otherKeyPersons, establishments, subsidiaries). Shared datapoints (shareholders, ultimateBeneficialOwners, availableDocuments, graph) can be combined with either vocabulary until the cutoff. From December 1, every new request containing companyProfile is rejected.
The response echoes your vocabulary
dataStatus.dataPoints uses the exact keys you sent. Send companyProfile, get companyProfile back. Send company + legalRepresentatives, get them back separately. The internal best-effort expansion is not visible in dataStatus.
dataStatus.dataPoints.companyProfile. Continue accepting the legacy status key when reading requests created before the cutoff.
The response body itself contains whatever sections the country’s block produced. For a country whose block covers all four company-level datapoints, a companyProfile request returns company, legalRepresentatives, otherKeyPersons, and establishments fields in the body. Request them explicitly (new vocabulary) to make that shape obvious in your code.
Replace /v2/onboarding
/v2/onboarding is deprecated. Use /v2/company with mode: "prefill" instead.
/v2/onboarding requests only company in prefill mode and reports its status under dataStatus.dataPoints.company, so the request above is the like-for-like replacement.
Two wins from the move:
- You pick the datapoints. The old endpoint only returns
company. On/v2/companyyou can addlegalRepresentatives,shareholders,ultimateBeneficialOwners, or anything else and still run in prefill mode. - One codebase, one response shape. Verification and prefill share the endpoint, the DTO, and the
dataStatusformat. Read Verification vs Prefill Mode for the source-selection and deadline behavior.
Prefill mode enforces a hard 10-second deadline per datapoint and only uses fast sources. Datapoints that have no fast source fail with
fast_source_unavailable. See Verification vs Prefill Mode.Compatibility summary
New integrations should start with explicit datapoints and
/v2/company. Existing integrations must replace companyProfile before December 1, 2026 at 00:00 UTC. This cutoff does not change retrieval of existing requests or the availability of /v2/onboarding.
Next steps
Company Data
Full
/v2/company request and response reference.Verification vs Prefill Mode
Source selection, deadlines, and
authoritative flag.KYB Onboarding
End-to-end flow combining search, prefill mode, and verification.
Pricing & Caching
How datapoints map to billable blocks and the 24-hour dedup window.