Skip to main content
Changes to the Companies V1 API contract, newest first. Use the tag filters to narrow the list.
​
2026-06
Enhanced ProfileOrdersPreview
🚧 Preview — in development, not yet available in production.Async order pattern for Enhanced ProfileSlow-running orders (jurisdictions where upstream fulfilment exceeds the ~40s connection-hold window) will have a documented async path on GET /core/company/profile/{countryISO}/{companyCode}.
  • GET /core/company/profile/{countryISO}/{companyCode} will return 202 when the upstream provider does not fulfil the profile within the connection-hold window. The 202 response will include a numeric orderId and a Location header pointing to the order-status endpoint.
  • The orderId in the 202 response body will be the same numeric identifier as productOrderIdField in the order-status list response — match on it to track completion.
  • Poll GET /core/filing/order-status/{orderedWithin} to find the order in the returned array; when statusField indicates completion (2, 21, or 3), retrieve the profile from urlField or structuredDataUrlField.
  • The description of GET /core/filing/order-status/{orderedWithin} is widened to reflect that it will track Enhanced Profile orders in addition to filing documents.
  • Initial preview rollout: GB, IE, LU, EE, LV, CN, JP, HK — alongside V2’s POST Enhanced Profile. Slow fulfilment is observed today primarily for Luxembourg, with Hong Kong also in scope.
See the release note for full integration guidance, including a worked polling example and the lost-orderId recovery pattern.
​
2026-03
Profiles
Typed corporate identifiersCorporate shareholders and directors can now carry multiple typed identifiers — ACN, ABN, ARBN, ARSN, ARFN, and foreign registration numbers — via a new otherIdentifiers array on CoreShareholderDetail and CoreDirectorDetail.
Backwards compatible — reuses the existing Identifier schema. First surfaced for Australian (ASIC) companies.
​
2026-02
Enhanced Profile
Shareholding percentage rangesShareholdings can now express an ownership range when a registry does not report an exact percentage.
  • CoreShareholderDetail.percentageField is now nullable. When a range applies, percentageField is null and percentageIsRangeField, percentageRangeField, percentageLowerLimitField, and percentageUpperLimitField carry the range.
Supports registries such as Estonia (EE) that may report ownership as a range (e.g. “0–100%”).
​
2026-02
UBO Verify
UBO Verify enhancementsUBO Verify gains entity-resolution tracking and richer ownership analysis.
  • Entity resolution and continuation tracking — addressField, entitySelectionMetadataField, selectedCandidatesField, and previousVersionsField provide an audit trail and ownership-tree version history.
  • Richer analysis — a top-level uboAnalysisField with status, metrics, required profiles, and beneficial-owner groups; fuzzy name matching; coverage metrics; and prioritised required-profile recommendations.
Backwards compatible. Supports entity disambiguation with a full audit trail, actionable UBO insights, and detection of potential hidden beneficial ownership.
​
2026-02
Search
Typed identifiers in Search resultsSearch results now include typed identifiers via an otherIdentifiers array with type codes.
Available across all four search endpoints — Company Search by Name, Company Search by Registration Number, Lite Search by Name, and Lite Search by Registration Number.
​
2025-10
Profiles
Company name field consistencyAlternative and previous company names are now handled consistently across V1 response objects.
  • previousNamesField arrays added to CompanyRecord, EnhancedProfile, and Corporation.
  • aliasesField arrays added to EnhancedProfile and Corporation.
  • englishNameField added to LiteProfile.
Provides a consistent structure for trading names, business names, and historical legal names, and aligns LiteProfile with V2 and EnhancedProfile for English-name support.
​
2025-03
Identifiers
Identifier standardisationCompany identifiers move to the typed otherIdentifiers array, replacing several legacy fields.
  • New otherIdentifiers array with type codes.
  • Deprecated legacy identifier fields — fiscalCode, vatNumber, companyID, and secondaryRegistrationNumber.
Use otherIdentifiers (with its type codes) in place of the deprecated fields.