> ## 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.

<Info>
  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.
</Info>

***

## When to use a Lite Profile

<CardGroup cols={2}>
  <Card title="KYB onboarding" icon="building">
    Confirm a company's name, registration number, and legal status before proceeding with a full due diligence workflow.
  </Card>

  <Card title="Address verification" icon="location-dot">
    Retrieve the company's registered address for identity confirmation or document delivery.
  </Card>

  <Card title="Status checks" icon="circle-check">
    Quickly confirm whether a company is active, dissolved, or otherwise no longer trading.
  </Card>

  <Card title="Pre-screening" icon="filter">
    Validate a company's existence and basic details before committing to a more detailed — and more expensive — Enhanced Profile order.
  </Card>
</CardGroup>

***

## How it works

Ordering a Lite Profile is a two-step process:

<Steps>
  <Step title="Search for the company">
    Use the [Company Search](/api-reference/company-search/search-by-name) 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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

***

## Request

```bash theme={null}
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

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

***

## Response

### Example response

```json theme={null}
{
  "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](/company-v1/guides/response-codes) for the full list. |

<Warning>
  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.
</Warning>

<Warning>
  `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.
</Warning>

***

## 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/company-profile/enhanced-profile) when your workflow requires ownership structure, representatives, or filings.

***

## Best practices

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

***

## Next steps

<CardGroup cols={2}>
  <Card title="Enhanced Profile" icon="building-columns" href="/documentation/features/perform-a-kyb-check-v1">
    Retrieve directors, shareholders, and full ownership structure for a company.
  </Card>

  <Card title="Filing Search" icon="file-magnifying-glass" href="/documentation/features/retrieve-a-document-v1">
    Order official registry documents and historical filings.
  </Card>

  <Card title="Supported Jurisdictions" icon="globe" href="/company-v1/guides/jurisdictions">
    Browse the full list of countries and registries covered by Kyckr.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/lite/lite-profile">
    Full endpoint specification with all parameters and response schemas.
  </Card>
</CardGroup>