Verify Basic Details

A Lite Profile gives you the core verified details for any company in Kyckr’s network — name, registration number, address, legal status, and more — sourced directly from the company register at the point of request. Use a Lite Profile when you need fast, reliable company verification without the overhead of a full Enhanced Profile.

All Lite 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 a Lite Profile

KYB onboarding

Confirm a company’s name, registration number, and legal status before proceeding with a full due diligence workflow.

Address verification

Retrieve the company’s registered address for identity confirmation or document delivery.

Status checks

Quickly confirm whether a company is active, dissolved, or otherwise no longer trading.

Pre-screening

Validate a company’s existence and basic details before committing to a more detailed — and more expensive — Enhanced Profile order.

How it works

Ordering a Lite Profile is a two-step process:

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.

Order the Lite Profile

Pass the codeField and the two-digit ISO country code as path parameters in the Lite Profile request. If the search response included a registrationAuthorityCodeField, this must also be supplied. Kyckr retrieves the current data from the registry and returns it in the response.

Request

GET /lite/profile/{isocode}/{codeField}

Parameter	Type	Required	Description
`isocode`	path	Yes	Two-digit ISO 3166-1 alpha-2 country code (e.g. `GB`, `DE`).
`codeField`	path	Yes	The unique company identifier returned by the search endpoint.
`RegAuth`	query	Conditional	Required for Germany and Canada if `registrationAuthorityCodeField` was present in the search response.

Authentication

All requests require an API key in the Authorization header.

Example request

curl --location 'https://rest.kyckr.com/lite/profile/GB/11655290' \
--header 'Authorization: {{apiKey}}'

Response

Example response

{
  "companyProfileField": {
    "activityField": [
      {
        "codeField": "63120",
        "descriptionField": "Web portals"
      }
    ],
    "addressesField": [
      {
        "countryField": "United Kingdom",
        "addressInOneLineField": "Kemp House, 160 City Road, EC1V 2NX, London",
        "addressLine1Field": "Kemp House",
        "addressLine2Field": "160 City Road",
        "cityTownField": "London",
        "postcodeField": "EC1V 2NX"
      }
    ],
    "codeField": "11655290",
    "dateField": "2023-02-20T17:06:26.2028259Z",
    "foundationDateField": "2018-11-01",
    "legalFormField": "ltd",
    "legalStatusField": "active",
    "nameField": "KYCKR UK LIMITED",
    "registrationAuthorityField": "Companies House, United Kingdom"
  },
  "transactionIdField": "9030922",
  "retrievalLocationField": "",
  "responseCodeField": "100"
}

Response fields

Field	Description
`companyProfileField.nameField`	The company’s registered name as it appears on the registry.
`companyProfileField.codeField`	The company’s registration number as issued by the registry.
`companyProfileField.legalStatusField`	The company’s current registration status in the registry’s own terminology. Values vary by jurisdiction — do not rely on a fixed set of values.
`companyProfileField.legalFormField`	The company’s legal form in the registry’s original terminology (e.g. `ltd`, `plc`).
`companyProfileField.foundationDateField`	The company’s registration or foundation date.
`companyProfileField.addressesField`	The company’s registered address. Field availability varies by registry.
`companyProfileField.activityField`	Industry activity codes and descriptions as recorded at the registry.
`companyProfileField.registrationAuthorityField`	The name of the company register from which the data was sourced.
`transactionIdField`	Unique identifier for this transaction. Useful for support queries and request tracing.
`responseCodeField`	Indicates the outcome of the request. A value of `100` indicates success. See Response Codes for the full list.

Field availability varies by registry. Not all registries publish every field. Where a data point is absent from the source registry, the corresponding field will be omitted from the response rather than returned as null.

legalStatusField is always a raw string returned verbatim from the source registry. Kyckr does not normalise or standardise this value. The exact string varies by jurisdiction — do not rely on a fixed set of values when building conditional logic around company status.

Lite Profile vs. Enhanced Profile

	Lite Profile	Enhanced Profile
Company name & number	✅	✅
Legal status	✅	✅
Registered address	✅	✅
Foundation date	✅	✅
Legal form	✅	✅
Activity codes	✅	✅
Directors & officers	❌	✅
Shareholders & UBOs	❌	✅
Filing history	❌	✅
Fulfilment	Synchronous	Sometimes asynchronous — see Enhanced Profile
Best for	Fast status checks & onboarding pre-screening	Full KYB and due diligence

Use the Lite Profile when you need to confirm existence and status. Use the Enhanced Profile when your workflow requires ownership structure, representatives, or filings.

Best practices

Always run a search first

The Lite Profile endpoint requires a valid codeField from the search response. Always derive this value from a prior search call — do not attempt to construct or guess the identifier manually.

Check for registrationAuthorityCodeField before ordering

For companies in Germany and Canada, the search response may include a registrationAuthorityCodeField. If present, this value must be passed as the RegAuth query parameter when ordering the Lite Profile. Omitting it will result in an unsuccessful request.

Check legalStatusField before downstream processing

Before passing a company’s details into any downstream workflow, inspect legalStatusField. Because this value is sourced verbatim from the registry and varies by jurisdiction, do not hardcode checks against a specific string like "active". Build your logic to handle the range of values your target jurisdictions may return, and flag unrecognised values for manual review.

Handle missing fields gracefully

Field availability varies by registry. Your integration should treat all fields within companyProfileField as optional and handle their absence without throwing errors. Do not assume that a field present in one jurisdiction will be present in another.

Use transactionIdField for support

If you encounter unexpected results or need to raise a support query, include the transactionIdField from the response. This allows Kyckr’s support team to trace the exact registry interaction.

Next steps

Enhanced Profile

Retrieve directors, shareholders, and full ownership structure for a company.

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.

Getting Started

Useful Information

Features

Platform Details

When to use a Lite Profile

KYB onboarding

Address verification

Status checks

Pre-screening

How it works

Request

Authentication

Example request

Response

Example response

Response fields

Lite Profile vs. Enhanced Profile

Best practices

Next steps

Enhanced Profile

Filing Search

Supported Jurisdictions

API Reference

​When to use a Lite Profile

KYB onboarding

Address verification

Status checks

Pre-screening

​How it works

​Request

​Authentication

​Example request

​Response

​Example response

​Response fields

​Lite Profile vs. Enhanced Profile

​Best practices

​Next steps

Enhanced Profile

Filing Search

Supported Jurisdictions

API Reference

When to use a Lite Profile

How it works

Request

Authentication

Example request

Response

Example response

Response fields

Lite Profile vs. Enhanced Profile

Best practices

Next steps