> ## 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.
# Verify Basic Details
> Retrieve verified basic company details sourced live from the registry.
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
Confirm a company's name, registration number, and legal status before proceeding with a full due diligence workflow.
Retrieve the company's registered address for identity confirmation or document delivery.
Quickly confirm whether a company is active, dissolved, or otherwise no longer trading.
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:
Use the [Company Search](/api-reference/companies/search-for-companies) 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.
Pass the `id `from the search response as the resource identifier in the Lite Profile request. Kyckr retrieves the current data from the registry and returns it in the response.
***
## Request
```bash theme={null}
GET /v2/lite/profile/{id}/lite
```
Replace `{id}` with the company identifier returned by the search endpoint.
### Optional Parameters
You can include a customer reference for the transaction using the parameter\
key `customerreference`
### Authentication
All requests require a Bearer token in the `Authorization` header.
### Example request
```bash theme={null}
curl --location 'https://api.kyckr.com/v2/lite/profile/GB|MTE2NTUyOTA/lite' \
--header 'Authorization: Bearer {{apiKey}}'
```
The `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
```json theme={null}
{
"correlationId": "019cddaa-227e-719c-b9fd-914971d5af98",
"customerReference": "",
"cost": {
"type": "lite",
"value": 1
},
"timeStamp": "2026-03-11T16:10:40.8765946Z",
"details": "Success",
"data": {
"activity": [
{
"code": "63120",
"description": "Web portals",
"classificationScheme": "SIC07",
"type": "Primary"
}
],
"address": {
"fullAddress": "78 York Street, London, England, W1H 1DP",
"buildingName": "78 York Street",
"city": "London",
"postcode": "W1H 1DP",
"country": "England"
},
"companyNumber": "11655290",
"companyName": "KYCKR UK LIMITED",
"foundationDate": {
"original": "2018-11-01",
"normalized": "2018-11-01"
},
"registrationDate": {
"original": "2018-11-01",
"normalized": "2018-11-01"
},
"legalForm": {
"original": "Private limited company"
},
"legalStatus": {
"original": "Active",
"normalized": "Active"
},
"registrationAuthority": "Companies House, United Kingdom"
}
}
```
### 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. |
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.
`data.legalStatus.original` 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](/api-reference/companies/enhanced-profile) when your workflow requires ownership structure, representatives, or filings.
***
## Best practices
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.
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.
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.
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
Retrieve directors, shareholders, and full ownership structure for a company.
Order official registry documents and historical filings.
Browse the full list of countries and registries covered by Kyckr.
Full endpoint specification with all parameters and response schemas.