All Enhanced Profile data is sourced live from the registry at the time of the request. There is no cached layer: what you receive reflects the current state of the register.
When to use an Enhanced Profile
KYB due diligence
Retrieve directors, officers, and shareholders as part of a full Know Your Business workflow.
Ownership verification
Confirm shareholders, share counts, and ultimate holding companies where filed in structured form at the registry.
Representative checks
Identify company officials, their appointed roles, nationalities, and addresses as recorded at the register.
Capital structure
Retrieve share capital details including share class, quantity, currency, and total value where filed at the registry.
How it works
Ordering an Enhanced Profile is a two-step process:1
Search for the company
Use the Company Search endpoint to locate the company and confirm it exists in the registry. The search response returns a
codeField: a unique identifier for that company on the register. If a registrationAuthorityCodeField is present in the search response, note this value; it will be required in the next step.2
Order the Enhanced Profile
Pass the
codeField and the two-digit ISO country code as path parameters in the Enhanced Profile request. If the search response included a registrationAuthorityCodeField, this must also be supplied as the RegAuth query parameter. Kyckr retrieves the current data from the registry and returns it in the response.Asynchronous fulfilment
For most jurisdictions,GET /core/company/profile/{countryISO}/{companyCode} returns the profile synchronously. Where fulfilment takes too long, the endpoint returns 200 with a pending-response body instead: this fallback is enabled today for Luxembourg. There’s no separate status code for the pending case: check the body for a transactionIdField and a processing message rather than a profile payload.
Poll GET /core/filing/order-status/{orderedWithin} (for example orderedWithin=1 for the last 24 hours) and match productOrderIdField in each returned item against the transactionIdField. When the matching item’s statusField is 2, 21, or 3, retrieve the profile from urlField or structuredDataUrlField.
See the async order pattern release note for full integration guidance.
Request
Authentication
All requests require an API key in theAuthorization header.
Example request
Response
Example response
Registration fields
Capital fields
Directors fields
Shareholders fields
Enhanced Profile vs. Lite Profile
Next steps
Lite Profile
Retrieve core company details without the overhead of a full Enhanced Profile.
Filing Search
Order official registry documents and historical filings.
Supported Jurisdictions
Browse the full list of countries and registries covered by Kyckr.
API Reference
Full endpoint specification with all parameters and response schemas.