Recommended pattern for production integrations. Creates a request for an enhanced company profile and returns an orderId immediately, with no server-side connection hold. Use GET /orders/{orderId} to retrieve the profile when ready. The resulting profile data is identical to that returned by a successful GET 200 on this resource.

Holding connections server-side costs infrastructure capacity at scale. POST + poll avoids that cost: the server acknowledges immediately, and the client polls at its own cadence. This is the preferred pattern for high-volume pipelines and resource-conscious integrations.

GET is also available for ad-hoc or low-volume use (one-off scripts, manual exploration): it returns data directly when available in time and automatically falls back to 202 with an orderId otherwise.

Profile content (where filed in structured form at the registry):

• Registration Information (Lite Profile + expanded details where available)
• Share capital structure
• Company Officials (incl. Directors) – including function, date of birth and address.
• Shareholders (Beneficial owners) – including share count, share percentage and ID information.
• Ultimate Beneficial Owners – where filed in structured form.

{
  "orderId": "12345",
  "cost": {
    "type": "credit",
    "value": 3
  },
  "links": {
    "self": "/orders/12345"
  },
  "data": {
    "cost": {
      "type": "credit",
      "value": 3
    }
  }
}