Request Enhanced Profile

curl --request POST \
  --url https://api.kyckr.com/v2/companies/{kyckrId}/enhanced \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "customerReference": "<string>",
  "contactEmail": "jsmith@example.com"
}
'

"<unknown>"

Companies

Request Enhanced Profile

🚧 COMING SOON

Recommended pattern for production integrations. Creates a request for an enhanced company profile and returns an orderId immediately — no server-side connection hold. Use GET /orders/ to retrieve the profile when ready. The resulting profile data is identical to that returned by a successful GET 200 on this resource.

Holding connections server-side costs infrastructure capacity at scale. POST + poll avoids that cost: the server acknowledges immediately, and the client polls at its own cadence. This is the preferred pattern for high-volume pipelines and resource-conscious integrations.

For ad-hoc or low-volume use (one-off scripts, manual exploration), GET is available as a convenience: it returns data directly when available within ~40s and automatically falls back to 202 with an orderId otherwise.

Profile content (where filed in structured form at the registry):

Registration Information (Lite Profile + expanded details where available)
Share capital structure
Company Officials (incl. Directors) – including function, date of birth and address.
Shareholders (Beneficial owners) – including share count, share percentage and ID information.
Ultimate Beneficial Owners – where filed in structured form.

POST

companies

{kyckrId}

enhanced

Request Enhanced Profile

curl --request POST \
  --url https://api.kyckr.com/v2/companies/{kyckrId}/enhanced \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "customerReference": "<string>",
  "contactEmail": "jsmith@example.com"
}
'

"<unknown>"

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

kyckrId

string

required

Kyckr company reference, a shared format, usable across our V2 APIs

Body

application/json

customerReference

string

Optional client reference

contactEmail

string<email>

An email address that can be contacted in case of issues with the order

Response

Created

The response is of type any.

Enhanced Profile Documents

⌘I