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.Documentation Index
Fetch the complete documentation index at: https://developer.kyckr.com/llms.txt
Use this file to discover all available pages before exploring further.
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 an
id field — a unique identifier for that company in Kyckr’s network.Request
{id} with the company identifier returned by the search endpoint.
Optional Parameters
You can include a customer reference for the transaction using the parameterkey
customerreference
Authentication
All requests require a Bearer token in theAuthorization header.
Example request
id format encodes the jurisdiction and a registry-specific identifier. In the example above, GB|MTE2NTUyOTA identifies Kyckr UK Limited on the UK Companies House register.
Response
Example response
Response fields
| Field | Description |
|---|---|
correlationId | Unique identifier for this API request. Useful for support queries and request tracing. |
customerReference | Optional reference value passed in the request. Returned as-is. |
cost.type | Will always be "Lite". |
cost.value | All lite profiles have the same cost. |
timeStamp | UTC timestamp of when the response was generated. |
details | High-level status of the request. A value of "Success" indicates data was retrieved. |
data.activity | Industry activity codes and descriptions as recorded at the registry. Includes a type field where available (e.g. Primary). |
data.address | The company’s registered address. Field availability varies by registry. |
data.companyNumber | The company’s registration number as issued by the registry. |
data.companyName | The company’s registered name as it appears on the registry. |
data.foundationDate.original | The company’s registration or foundation date in the registry’s original format. |
data.legalForm.original | The company’s legal form in the registry’s original terminology (e.g. ltd, plc). |
data.legalStatus.original | The company’s current registration status in the registry’s own terminology. This is always a raw string sourced directly from the registry — it is never normalised or mapped to a controlled vocabulary. Values vary by jurisdiction (e.g. active, dissolved, radierad, liquidation). |
data.registrationAuthority | The name of the company register from which the data was sourced. |
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 | ❌ | ✅ |
| Best for | Fast status checks & onboarding pre-screening | Full KYB and due diligence |
Best practices
Always run a search first
Always run a search first
The Lite Profile endpoint requires a valid
id from the search response. Attempting to construct an id manually is not supported and will produce unreliable results. Always derive the id from a prior search call.Check legalStatus before downstream processing
Check legalStatus before downstream processing
Before passing a company’s details into any downstream workflow, inspect
data.legalStatus.original. Because this value is sourced verbatim from the registry and varies by jurisdiction, do not hardcode checks against a specific string like "active". Instead, build your logic to handle the range of values your target jurisdictions may return, and consider flagging unrecognised values for manual review.Handle missing fields gracefully
Handle missing fields gracefully
Because field availability varies by registry, your integration should treat all
data fields 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 correlationId for support
Use correlationId for support
If you encounter unexpected results or need to raise a support query, include the
correlationId 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.