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

# Hong Kong Company Data: Enhanced Profile via Enhanced Profile endpoint

> The Hong Kong Enhanced Profile is now available synchronously from the Enhanced Profile endpoint.

## Overview

The Hong Kong (HK) Enhanced Profile is now available directly from the Enhanced Profile endpoint, in the same way as other jurisdictions.

Until now, the HK Enhanced Profile was listed by the Documents endpoint, ordered with Create Order and retrieved asynchronously. The same structured data now comes back synchronously from Enhanced Profile.

### Key points

* **New route:** `GET /v2/companies/{kyckrId}/enhanced` now returns the HK Enhanced Profile.
* **No response changes:** The structured data is identical to what the asynchronous order returns. No changes to your parsing are needed.

## What's changing

| | Before | Now |
| - | - | - |
| Endpoint | `GET /v2/companies/{kyckrId}/documents`, then `POST /v2/orders` | `GET /v2/companies/{kyckrId}/enhanced` |
| Delivery | Asynchronous order, polled for the result | Synchronous, with an asynchronous fallback |
| Response data | HK Enhanced Profile | Same HK Enhanced Profile, no changes |

## If the registry responds slowly

The HK Enhanced Profile uses the [asynchronous order pattern](https://developer.kyckr.com/company-v2/developer-news/2026-08-async-order-pattern). If the registry hasn't returned the profile after about 40 seconds, the endpoint returns **HTTP `202`** with an `orderId` instead of the profile. Your integration should handle it:

```json theme={null}
{
  "correlationId": "...",
  "timeStamp": "...",
  "data": {
    "status": "Pending",
    "orderId": 12345,
    "cost": { "type": "credit", "value": 1 }
  }
}
```

1. Read `data.orderId` from the `202` response.
2. Poll `GET /v2/orders/{orderId}` with exponential backoff until `data.status` is `Success`. A status of `Failed` means fulfilment failed.
3. Retrieve the profile from the order result.

If you prefer not to hold a connection open, you can still use `POST /v2/companies/{kyckrId}/enhanced`. It returns a `202` with an `orderId` immediately, and you poll the same way.

> [!NOTE]
>
> Don't re-issue the `GET` request if you lose the `orderId`. This creates a new, separately billed order. Instead, call `GET /v2/orders` and filter on your `customerReference`.

## Timeline

| Date | Change |
| - | - |
| 21 October 2026 | HK Enhanced Profile available from the Enhanced Profile endpoint |

## What you need to do

If you order the HK Enhanced Profile through Documents and Create Order:

1. Replace those calls with `GET /v2/companies/{kyckrId}/enhanced` for HK companies.
2. Test the change.

You don't need to do anything if you already use the Enhanced Profile endpoint for HK, or if you don't order the HK Enhanced Profile.

## Additional resources

* [Enhanced Profile](https://developer.kyckr.com/api-reference/companies/enhanced-profile.md)
* [Documents](https://developer.kyckr.com/api-reference/companies/documents.md)
* [Asynchronous order pattern](https://developer.kyckr.com/company-v2/developer-news/2026-08-async-order-pattern)
* [Hong Kong Company Data – Search, Lite Profile, and Enhanced Profile](https://developer.kyckr.com/company-v2/developer-news/2026-06-hong-kong-update-v2)
* [Company V2 API overview](https://developer.kyckr.com/company-v2/api-reference/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.