> ## 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 returned by Filing Search as a document product, ordered with Product Order and retrieved asynchronously. The same structured data now comes back synchronously from Enhanced Profile.

### Key points

* **New route:** `GET /core/company/profile/HK/{companyCode}` now returns the HK Enhanced Profile.
* **No response changes:** The structured data is identical to what the asynchronous product order returns. No changes to your parsing are needed.

## What's changing

| | Before | Now |
| - | - | - |
| Endpoint | `GET /core/filing/search/HK/{companyCode}`, then Product Order | `GET /core/company/profile/HK/{companyCode}` |
| Delivery | Asynchronous product order, polled with Order Status | 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-v1/developer-news/2026-08-async-order-pattern). If the registry can't return the profile in time, the endpoint returns a pending response instead of the profile. Your integration should handle it.

The pending response is also **HTTP `200`**, so check the response body. It carries no profile data, only `transactionIdField`, `responseCodeField` and `responseDetailsField`.

1. Read the `transactionIdField` from the pending response.
2. Poll `GET /core/filing/order-status/{orderedWithin}` with exponential backoff, and find the item whose `productOrderIdField` matches your `transactionIdField`.
3. When `statusField` is `2`, `21` or `3`, retrieve the profile from `urlField` or `structuredDataUrlField`. A status of `5` means the order failed.

> [!NOTE]
>
> Don't re-issue the `GET` request if you lose the `transactionIdField`. This creates a new, separately billed order. Instead, filter the order-status results on your `orderRef`.

## 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 Filing Search and Product Order:

1. Replace those calls with `GET /core/company/profile/HK/{companyCode}`, using the `codeField` from the search results as `companyCode`.
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/company-profile/enhanced-profile.md)
* [Filing Search](https://developer.kyckr.com/api-reference/registry-documents/filing-search.md)
* [Product Order](https://developer.kyckr.com/api-reference/registry-documents/product-order.md)
* [Asynchronous order pattern](https://developer.kyckr.com/company-v1/developer-news/2026-08-async-order-pattern)
* [Hong Kong Company Data – Search, Lite Profile, and Enhanced Profile](https://developer.kyckr.com/company-v1/developer-news/2026-06-hong-kong-update-v1)


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