# Introduction Source: https://developer.kyckr.com/Introduction The Kyckr API provides programmatic access to legally authoritative company data and original registry documents through a single integration, connected to a live network of over 300 corporate registries across 120 countries. Data is retrieved at the point of request, sourced directly from official government registries — synchronously for most jurisdictions, on a request-and-retrieve basis for others. Both machine-readable data (JSON or XML, normalised) and original registry documents (PDF, covering over 1,000 document types) are available through the same connection. Building direct relationships with government registries is slow, contract-heavy, and operationally expensive to maintain. The Kyckr API removes that burden entirely. One integration replaces dozens of fragmented connections, eliminating the authentication procedures, API maintenance, and ongoing contracting conversations that would otherwise consume significant engineering and compliance resource. With over 15 years spent building and expanding this network, Kyckr operates as a specialist data infrastructure layer trusted by organisations that require reliable, primary-source company data at scale. *** ## What you can retrieve * Structured company data (JSON/XML, normalised) * Director, officer, and shareholder information * Original documents from company registers (PDF) * Official filing records *** ## Why Kyckr Every company registry has its own authentication model, technical interface, access restrictions, and data format. Building direct connections is expensive to establish and operationally demanding to maintain — and scaling them internationally is a significant engineering commitment. Kyckr provides a single API layer that abstracts this complexity entirely. Instead of managing multiple registry integrations, you connect once and access a global registry network that has been built and maintained for over 20 years. *** ## What makes Kyckr different All data is retrieved from official company registers at the point of request — synchronously where the registry supports it, or via a request-and-retrieve pattern where fulfilment takes longer. No third-party aggregation, no stale data passed off as live. The API returns machine-readable company data in a normalised structure (JSON/XML) alongside original register documents (PDF) — supporting both automated workflows and documentary audit trails. A single API connection gives you access to 300+ company registries across 100+ countries — built and maintained by Kyckr over more than 20 years. *** ## Use cases **Know Your Business (KYB)** Kyckr is commonly integrated into KYB workflows to support company identification, verification of registration details, confirmation of directors and shareholders, and retrieval of official register documents. It is used within proprietary onboarding systems, third-party KYC orchestration platforms, and customer lifecycle management (CLM) systems. **Entity verification during onboarding** Kyckr is also used as a first-line compliance check at the point of onboarding. A typical workflow queries the `search` endpoint to locate an entity, then the `lite profile` endpoint to retrieve registered details — comparing returned data against customer-supplied information programmatically, and flagging or rejecting the application if there is a mismatch. *** ## How a typical integration works Kyckr is designed to support the full KYB journey — from initial company identification through to document retrieval and ownership verification. Query by company name or registration number. The API returns a list of matched entities from the relevant company registry. Once a company is identified, retrieve a profile. Two levels are available: * **Lite profile** — core company details for fast onboarding checks and pre-fill. Live data, sourced directly from the company register at the point of request. * **Enhanced profile** — full structured data including directors, officers, and shareholders (where registered), also sourced live from the company register. If entities appear above your ownership threshold, Kyckr's UBO Verify capability can unwrap the corporate structure and auto-calculate ultimate beneficial owners (UBOs). If all UBOs are identified from the initial profile, this step is not required. For registries where structured data is limited, or where documentary evidence is required, original extract PDFs can be ordered directly from the company register. Additional document types — annual accounts, articles of association, change notifications — are also available. Data availability and response times vary by jurisdiction. Some registries return data in real time; others operate on a request-and-retrieve basis. See the [Country Coverage guide](/documentation/useful-information/country-coverage) for details. *** ## Get started [Request access via the Kyckr website](https://www.kyckr.com/book-a-demo) to receive your credentials. Follow the [Quickstart](/api-reference) to run a company search and retrieve a profile in minutes. Follow the [Quickstart](/company-v2/api-reference/overview) to run a company search and retrieve a profile in minutes. Browse the [API Reference](/api-reference) for full endpoint documentation, parameters, and response schemas. Browse the [API Reference](/company-v2/api-reference/overview) for full endpoint documentation, parameters, and response schemas. # Documents Source: https://developer.kyckr.com/api-reference/companies/documents /openapi/company_v2.yaml get /companies/{kyckrId}/documents Retrieve a list of available documents for a company. After finding a document of interest, use the Create Order API to order a copy of the document. # Enhanced Profile Source: https://developer.kyckr.com/api-reference/companies/enhanced-profile /openapi/company_v2.yaml get /companies/{kyckrId}/enhanced Retrieve an enhanced company profile. The server holds the connection open while the registry fulfils the request. If the profile is ready in time, it is returned with HTTP 200. If not, HTTP 202 is returned with an orderId in the response body; poll GET /orders/{orderId} to retrieve the profile when complete. For production and high-volume integrations, POST is preferred: it returns an orderId immediately with no server-side connection hold, avoiding infrastructure cost at scale. The profile includes (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. # Lite Profile Source: https://developer.kyckr.com/api-reference/companies/lite-profile /openapi/company_v2.yaml get /companies/{kyckrId}/lite Basic company details are verified by ordering a Lite Profile. The Lite Profile includes (where present at the registry): - Company Name - Company Number - Registered Address - Registration or Foundation Date - Registration Status - Legal Form - Company Activity - Registration Authority # Request Enhanced Profile Source: https://developer.kyckr.com/api-reference/companies/request-enhanced-profile /openapi/company_v2.yaml post /companies/{kyckrId}/enhanced **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. # Search for companies Source: https://developer.kyckr.com/api-reference/companies/search-for-companies /openapi/company_v2.yaml get /companies Search companies using company name or registration number. You must provide one of `name` or `companyNumber`. With an `isoCode`, a search will be performed directly at the registry for that jurisdiction. Without an `isoCode`, Kyckr will perform a global search across all jurisdictions. It is important to remember that the Global Search uses stored data. Once you have found the correct jurisdiction, you should then use Kyckr's search by Name or Number API with the specific jurisdiction to confirm that the entity is still active on the register. # Create Order Source: https://developer.kyckr.com/api-reference/orders/create-order /openapi/company_v2.yaml post /orders Create an Order # Download Order Payload Source: https://developer.kyckr.com/api-reference/orders/download-order-payload /openapi/company_v2.yaml get /orders/{orderId}/download Retrieve the order result as either a structured JSON payload or a PDF document. The JSON schema shown is the Enhanced Profile (the Company V2 company payload). # Get List of Orders Source: https://developer.kyckr.com/api-reference/orders/get-list-of-orders /openapi/company_v2.yaml get /orders List all orders # Get Single Order Source: https://developer.kyckr.com/api-reference/orders/get-single-order /openapi/company_v2.yaml get /orders/{orderId} Retrieve a single order and retrieval details # Changelog Source: https://developer.kyckr.com/company-v2/api-reference/changelog Version history and changes to the Kyckr Companies V2 API. Changes to the Companies V2 API contract, newest first. Use the tag filters to narrow the list. **Async order pattern for Enhanced Profile** `POST /companies/{kyckrId}/enhanced` is the recommended production pattern: it returns an `orderId` immediately with no connection hold; poll `GET /orders/{orderId}` for the profile. `GET` gains a `202` fallback carrying the `orderId` in the response body, enabled per jurisdiction: Luxembourg today. See the [release note](/company-v2/developer-news/2026-08-async-order-pattern) for integration guidance. **Download endpoint now documented** `GET /v2/orders/{orderId}/download` is now documented in the API reference. The endpoint takes a `format=json` or `format=pdf` query parameter and returns the order result in the requested format. No change to the API: this endpoint is already available and its behaviour is unchanged; this entry only documents it. **Profile extensions and address geocoding** Enhanced Profile now supports opt-in, per-account extensions that enrich the response with extra data. The first extension, `geocoding`, returns parsed and geocoded address information. * Request extensions with the new `extend` query parameter (a comma-separated list) on `GET` Enhanced Profile. * `geocoding` adds parsed and geocoded address data via the `additionalInformation` response object. * Each `Address` now carries a stable `identifier` that links it to its geocoded entry in `additionalInformation.addressInformation`. * New schemas: `AdditionalInformation`, `AddressAdditionalInformation`, `InformationSource`. * The mechanism is extensible: further extension types (e.g. firmographics, activity codes) will follow. * Unrecognised or unauthorised `extend` values are ignored silently. Opt-in and entitled per account; each extension type carries an additional cost. **Typed corporate identifiers** Corporate representatives and shareholders can now carry multiple typed identifiers: ACN, ABN, ARBN, ARSN, ARFN, and foreign registration numbers, via a new `otherIdentifiers` array on `CorporationDetails`. Backwards compatible: reuses the existing `Identifier` schema. First surfaced for Australian (ASIC) companies. **Shareholding percentage ranges** Shareholdings can now express an ownership *range* when a registry does not report an exact percentage. * `Shareholding.percentage` is now nullable. When a range applies, `percentage` is null and `percentageIsRange`, `percentageRange`, `percentageLowerLimit`, and `percentageUpperLimit` carry the range. Supports registries such as Estonia (EE) that may report ownership as a range (e.g. "0–100%"). **Company relationships and registration type** Enhanced Profile can now carry company-relationship data and source-registry registration classification. * New `companyRelationships` array for relational extract data: subsidiaries, and company evolution (merged, demerged, acquired). Parent / ultimate parent / immediate parent remain in roles and corporate representatives; branches and establishments use a separate establishments model. * New `registrationType` and `registrationTypeDetails` capture the foreign registered body and its details at the source registry, where available. `companyRelationships` is in place now for forthcoming relational extract data: do not expect it populated for every entity yet. **POST Enhanced Profile** You can now request an Enhanced Profile with `POST /companies/{kyckrId}/enhanced`: the same resource as `GET`, but it creates an order without holding the connection open. See the [2026-08 entry](/company-v2/developer-news/2026-08-async-order-pattern) for the full async semantics: POST + poll for Enhanced Profile, and a `202` fallback on `GET` with `orderId` in the response body. **Typed identifiers in Search results** Search results now include typed identifiers via an `otherIdentifiers` array with type codes. Available on the single V2 search endpoint. Enables jurisdiction-specific identifier types. **Field consistency across profiles** Profile responses are now more consistent across the V2 API, with shared name components and additional `LiteProfile` and `BasicProfile` fields. * New reusable `AlternativeNames` and `PreviousNames` schema components. * `previousNames` now uses a standardised structure with proper schema references. * `LiteProfile` gains `registrationDate` and `lastAnnualAccountDate`. * `BasicProfile` gains `registeredAgentName` and `registeredAgentAddress`. Aligns `LiteProfile` date fields and registered-agent information with V1 and `EnhancedProfile`. **Order response documentation fix** Corrected the `Get Order` API response documentation, and documented additional response properties. Planned: previous names on `SearchResults`; Enhanced Profile additions: UBO kind, last annual account date, and registry-sourced voting-rights descriptions. **Capital and shareholding simplification** Capital and shareholding structures are simplified, and corporate identifiers move to the typed `otherIdentifiers` array. * Simplified capital and shareholding structures. * `tradingName` is deprecated: use `alias` instead. * New `otherIdentifiers` with jurisdiction-specific type codes. `otherIdentifiers` will gain further type codes per jurisdiction over time. **Beneficially-held shareholdings** Enhanced Profile can now flag beneficially-held shareholdings and classify ambiguous entities. * New `capital[].shareholdings[].beneficiallyHeld` field on Enhanced Profile. * New "Other" category in the corporations and individuals arrays for entities the registry cannot definitively classify. Introduced ahead of an Australian registry update. **Documentation corrections** Clarified the `ultimateBeneficialOwners` field descriptions on Enhanced Profile. **Documentation corrections** Corrected the Enhanced Profile `ultimateBeneficialOwners` documentation. # Overview Source: https://developer.kyckr.com/company-v2/api-reference/overview Base URLs, authentication, and the shared response envelope used by every Kyckr V2 API. Everything on this page applies to every Kyckr V2 API. Each product is listed separately below, with its own endpoints and changelog. New to the API? Start with the [Getting Started guide](/company-v2/guides/getting-started). ## Base URL | Environment | Base URL | | ----------- | ------------------------------- | | Production | `https://api.kyckr.com/v2` | | Test | `https://test-api.kyckr.com/v2` | Every V2 product is served from these base URLs — there is no per-product host. ## Authentication Every request requires your API key, sent in the `Authorization` header. The same key works across all V2 products; see [Getting Started](/company-v2/guides/getting-started) for how to obtain and send it. ## Response format Responses share a common envelope: * `correlationId` — a unique ID for the request; quote it in support enquiries. * `timeStamp` — when the response was generated. * `details` — a human-readable status message. * `data` — the response payload, which varies by endpoint. Asynchronous operations (orders) also return an `orderId` you can poll for the result. ## Orders Products that cannot answer in real time are ordered rather than fetched. Ordering is shared infrastructure: whichever product you order, you place the order on that product's endpoint and retrieve the result from `GET /orders/{orderId}`. ## Finding your way around * **[Getting Started](/company-v2/guides/getting-started)** and the other guides — task-based walkthroughs for search, profiles, documents, and orders. * **API Reference** (this section) — each product's endpoints and its changelog, grouped by product. # Developer News Source: https://developer.kyckr.com/company-v2/developer-news Product updates and announcements for the Company V2 API. ### [Denmark Company Data – Lite Profile and Enhanced Profile Updates](/company-v2/developer-news/2026-07-denmark-update) **Status: Preview** | September 9, 2026 | API Changes Denmark (DK) Lite Profile and Enhanced Profile responses updated with a redesigned address structure, English-normalized vocabulary, share-class capital detail, individual shareholders, and range-based ownership percentages. ### [Async Order Pattern for Enhanced Profile: POST + Poll Recommended](/company-v2/developer-news/2026-08-async-order-pattern) **Status: Released** | August 26, 2026 | API Changes The V2 async order pattern: order Enhanced Profile with `POST /v2/companies/{kyckrId}/enhanced` and poll for the result. `GET` gains a `202` fallback for slow orders. ### [China Company Data – Search, Lite Profile, Enhanced Profile](/company-v2/developer-news/2026-06-china-update-v2) **Status: Released** | July 30, 2026 | API Changes China Search, Lite Profile, and Enhanced Profile responses updated with improved data quality and additional fields ### [Japan Company Data – Search, Lite Profile, Enhanced Profile](/company-v2/developer-news/2026-06-japan-update-v2) **Status: Released** | July 30, 2026 | API Changes Japan Search, Lite Profile, and Enhanced Profile responses updated with improved data quality and additional fields ### [Hong Kong Company Data – Search, Lite Profile, Enhanced Profile](/company-v2/developer-news/2026-06-hong-kong-update-v2) **Status: Released** | July 30, 2026 | API Changes Hong Kong Search, Lite Profile, and Enhanced Profile responses updated with improved data quality and additional fields ### [Ireland Company Data – Search, Lite Profile, Enhanced Profile, and Business Name Support](/company-v2/developer-news/2026-04-ireland-update) **Status: Released** | April 10, 2026 | API Changes Ireland Search, Lite Profile, and Enhanced Profile responses updated with improved data quality, additional fields, and new Business Name entity support. ### [British Virgin Islands (BVI) – Search and Lite Profile Rollback](/company-v2/developer-news/2026-04-bvi-rollback) **Status: Released** | April 2, 2026 | API Changes — Service rolled back Rollback of the February 2026 BVI release. **Search and Lite Profile are no longer available** for British Virgin Islands companies due to changes at the BVI registry. ### [Finland Company Data – Search, Lite Profile, Enhanced Profile, and Filing Updates](/company-v2/developer-news/2026-03-finland-update) **Status: Released** | March 18, 2026 | API Changes Finland Search, Lite Profile, Enhanced Profile, and Filing responses updated following migration from EBR to PRH (Finnish Patent and Registration Office). Company number search is now supported. ### [Gibraltar Company Data – Search and Lite Profile Updates](/company-v2/developer-news/2026-03-gibraltar-update) **Status: Released** | March 6, 2026 | API Changes — Enhanced Profile discontinued Gibraltar Search and Lite Profile responses updated following migration from EBR to Companies House Gibraltar. **The Enhanced Profile product is being discontinued** — transition to Lite Profile or the Company Profile PDF document. ### [Jersey Company Data – Search and Lite Profile Updates](/company-v2/developer-news/2026-03-jersey-update) **Status: Released** | March 6, 2026 | API Changes — Enhanced Profile temporarily discontinued Jersey Search and Lite Profile responses updated following migration from EBR to the JFSC Companies Registry. **Enhanced Profile is temporarily discontinued** while an alternative solution is built. ### [Slovenia Company Data – Search, Lite Profile, and Filing List Updates](/company-v2/developer-news/2026-03-slovenia-update) **Status: Released** | March 6, 2026 | API Changes — Enhanced Profile discontinued Slovenia Search and Lite Profile responses updated following migration from EBR to AJPES. **The Enhanced Profile product is being discontinued** — transition to Lite Profile or the registry extract PDF available from the filing list. ### [Luxembourg Enhanced Profile – Shareholder Data Improvements](/company-v2/developer-news/2026-02-luxembourg-enhanced-shareholder-data) **Status: Released** | March 31, 2026 | API Changes Luxembourg Enhanced Profiles now include richer shareholder data with direct LBR integration, structured capital arrays, and activity data in V2 format. We've moved from the EBR network to a direct integration with the Luxembourg Business Register. ### [British Virgin Islands (BVI) Company Data Now Available](/company-v2/developer-news/2026-02-bvi-company-data) **Status: Preview** | February 4, 2026 | New Data Search for BVI companies, retrieve Lite Profiles, and access filing lists through the BVI Financial Services Commission data integration with V2 API. ### [Latvia Company Data – Search, Lite Profile, and Enhanced Profile Updates](/company-v2/developer-news/2026-02-latvia-update) **Status: Released** | February 27, 2026 | API Changes Latvia V2 Search, Lite Profile, and Enhanced Profile responses updated with improved data quality and additional fields following the migration from EBR to a new provider. Enhanced Profiles remain available. ### [Estonia Company Data – Search, Lite Profile, and Enhanced Profile Updates](/company-v2/developer-news/2026-01-estonia-update) **Status: Preview** | January 27, 2026 | API Changes Estonia V2 Search, Lite Profile, and Enhanced Profile responses updated with improved data quality and additional fields following the migration from EBR to a new provider. ### [Lithuania Company Data – Enhanced Profiles Removed, Search and Lite Profile Updates](/company-v2/developer-news/2026-01-lithuania-update) **Status: Released** | January 20, 2026 | API Changes — Enhanced Profiles removed Lithuania company data migrated to a new provider. **Enhanced Profiles are no longer available.** Search and Lite Profile responses updated with improved V2 structure. ### [Enhanced UK Company Data – Director Information Improvements](/company-v2/developer-news/2025-12-uk-enhanced-director-data) **Status: Released** | December 8, 2025 | API Changes UK company director information now sourced directly from Companies House with improved V2 data quality, directorships lookup, and privacy-compliant birthdate handling (month and year only). ### [New Canada Integration for Search, Lite Profile and Company Profile Documents](/company-v2/developer-news/2025-10-canada-integration) **Status: Released** | November 19, 2025 | API Changes Comprehensive Canada integration for V2 API across all 14 jurisdictions with improved data quality, extra-provincial registration tracking, and Company Profile PDF documents. ### [Italian Company Identifier Changed from Codice Fiscale to REA](/company-v2/developer-news/2025-03-italy-update) **Status: Released** | March 18, 2025 | API Changes Italian company identifiers in V2 API now use REA (provincial registry numbers) instead of Codice Fiscale for unique company identification. Systems using search response data for subsequent calls require no changes. # FAQs Source: https://developer.kyckr.com/company-v2/guides/faqs Frequently asked questions about the V2 API. ### How do I know what information is available at different registries? When integrating with Kyckr, a matrix is provided detailing which fields in the Lite and Enhanced profiles are populated for each jurisdiction. High-level information can also be found using the [Coverage Portal](https://coverage.kyckr.com/). ### I know the company exists, but I cant find it when using Search? If the company exists at the registry but does not appear in search, altering search terms may help. Simplify by removing suffixes (such as LTD, GmbH, Corp, etc) and double check the correct jurisdiction is being searched. ### Does Kyckr format any data in responses? Kyckr returns **standard values** for several key fields alongside the original registry data, so you can route logic consistently across jurisdictions. Currently standardised on V2: * **`legalStatus.normalized`** — entity state: `Active`, `Inactive`, `Distressed` * **`legalForm.normalized`** — entity type, 15 values such as `Private Limited Company`, `Public Limited Company`, `Limited Partnership`, `Branch`, `Foreign Registered Body`, `Trust`, `Foundation`, `Cooperative`, and more * **`totalCapital.type`** — capital structure: `Fixed`, `Variable`, `Registered` * Activity / industry codes — `normalized` codes and descriptions on activity entries, where the registry provides them The raw registry string is always available in the corresponding `*.original` field, so finer detail is never lost. For the full list of values and definitions, see the [Normalised values guide](/documentation/useful-information/normalised-values). The same values are also declared on the relevant schemas in the [API Reference](/company-v2/api-reference/overview). Additional normalised fields will be introduced over time. ### I don't know the country I need to search in, is there a global search? Yes, Kyckr has an endpoint that searches across a cached dataset of companies. Whilst this dataset is not updated in real-time, this type of search can help to find the jurisdiction for an entity. A real-time search on the specific jurisdiction can then be performed using Kyckr's search API. [Cache search guide](global-search) ### A registry that I need isn't available in Test, what can I do? With some registries, it is not possible for us to offer a Test service that matches the production capability of that registry. Need to see an example response for a particular registry? Want to be 100% certain that it works in Production? Don't hesitate to reach out to us. # Supported Jurisdictions Source: https://developer.kyckr.com/company-v2/guides/jurisdictions ISO country codes, regional codes for US and Canada, and jurisdiction availability information. ## ISO country codes To search for a company on the Kyckr network, provide a country parameter as the identifier for the destination country. The API accepts a two-letter ISO Code for the country parameter. For example, to search for information in Ireland, use the ISO code `IE`. A full list of ISO codes can be obtained from [iso.org](https://www.iso.org/iso-3166-country-codes.html) ## Fully manual registries Due to technical limitations, some registries in Kyckr's network are currently only available via the portal. We plan to provide access to these registries via API in the future. * Arkansas (US) * Bonaire, (BN) * British Virgin Islands * Bulgaria * California (US) * Colorado (US) * Georgia (US) * Jersey * Maryland (US) * Mississippi (US) * Missouri (US) * Montana (US) * Myanmar * Nepal * Nevada (US) * North Carolina (US) * Ohio (US) * Oklahoma (US) * Saba, (AB) * Sint Eustatius, (SU) * South Carolina (US) * Utah (US) * Vermont (US) * Virginia (US) * Washington (US) ## United States and Canada Kyckr services for United States and Canada require breaking down the Country ISO code into a combination of Country and territory/state. ### US state codes For the US registry access we have continued to use the country ISO Code field but we need to know the specific state. So for example when calling Company Search for Texas the country ISO Code field should have the following value "US-TX". All of these values can be found by calling the Administration function Network Info. | Code | State | Code | State | | ----- | -------------------- | ----- | -------------- | | US-AL | Alabama | US-AK | Alaska | | US-AZ | Arizona | US-AR | Arkansas | | US-CA | California | US-CO | Colorado | | US-CT | Connecticut | US-DE | Delaware | | US-FL | Florida | US-GA | Georgia | | US-HI | Hawaii | US-ID | Idaho | | US-IL | Illinois | US-IN | Indiana | | US-IA | Iowa | US-KS | Kansas | | US-KY | Kentucky | US-LA | Louisiana | | US-ME | Maine | US-MD | Maryland | | US-MA | Massachusetts | US-MI | Michigan | | US-MN | Minnesota | US-MS | Mississippi | | US-MO | Missouri | US-MT | Montana | | US-NE | Nebraska | US-NV | Nevada | | US-NH | New Hampshire | US-NJ | New Jersey | | US-NM | New Mexico | US-NY | New York | | US-NC | North Carolina | US-ND | North Dakota | | US-OH | Ohio | US-OK | Oklahoma | | US-OR | Oregon | US-PA | Pennsylvania | | US-RI | Rhode Island | US-SC | South Carolina | | US-SD | South Dakota | US-TN | Tennessee | | US-TX | Texas | US-UT | Utah | | US-VT | Vermont | US-VA | Virginia | | US-WA | Washington | US-WV | West Virginia | | US-WI | Wisconsin | US-WY | Wyoming | | US-DC | District of Columbia | US-AS | American Samoa | ### Canadian territory codes | Code | Territory | | ------ | ----------------------------------- | | CA-AB | Alberta | | CA-BC | British Columbia | | CA-MB | Manitoba | | CA-NB | New Brunswick | | CA-NL | Newfoundland and Labrador | | CA-NS | Nova Scotia | | CA-ON | Ontario | | CA-PE | Prince Edward Island | | CA-QC | Quebec | | CA-SK | Saskatchewan | | CA-NT | Northwest Territories | | CA-NU | Nunavut | | CA-YU | Yukon | | CA-FE | Federal | | CA-ALL | All (Significantly less performant) | ## Countries where search by number is unavailable Below are the countries where company search by number is not available in both production and test API. * Bangladesh, BD * Brazil, BR * Cayman Islands, KY * Illinois (US), US-IL * Indonesia, ID * Morocco, MA * New York (US), US-NY * Nicaragua, NI * Oman, OM * Philippines, PH * South Carolina (US), US-SC * Trinidad and Tobago, TT # Response Codes Source: https://developer.kyckr.com/company-v2/guides/response-codes ## API Error Responses Any request that returns a 400 or 500 HTTP status will also include a`statas code` or `type`, `Title` and `Detail`. | Status Code | Title | Detail | When | | ----------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | | 400 | Bad Request | Too many results. Narrow search term | Search returned too many results | | 400 | Bad Request | Invalid company code | Company code or number was not valid | | 400 | Bad Request | Invalid parameter | A required parameter was missing or invalid | | 401 | Unauthorized | Request is not authorized | Authorization header missing, invalid, or token not recognised | | 402 | Payment Required | Insufficient credits | Account does not have enough credits to complete the request | | 403 | Forbidden | This feature is not available on this account | The account does not have access to this feature | | 404 | Not Found | Company not found | No company matched the provided identifier | | 404 | Not Found | ISO Code not found | The provided ISO country code was not recognised | | 404 | Registry Unavailable | This registry is not supported | The requested registry is not available on this platform | | 422 | Unprocessable Entity | name searched goes against our validation rules | Try again with a simpler name | | 429 | Too Many Requests | This service rate limit has been reached | The request rate limit for this service has been exceeded | | 500 | Unhandled Error | Please contact Kyckr Support. | An unexpected error occurred | | 503 | Service Unavailable | This registry is currently unavailable, please try again later and check [https://status.kyckr.com](https://status.kyckr.com) for outages | The registry is temporarily down | # About Testing Source: https://developer.kyckr.com/company-v2/guides/test-environment Information about the Kyckr V2 test environment for API development and testing. The Kyckr Test API provides JSON responses for all calls, enabling easy building, testing, and verification of projects without incurring costs. The same functions available in production are also available in the test environment. The new test environment only covers V2 of our REST API. ## Important differences between test and production environments * The main function of our test environment is to allow developers to test the end-to-end process from searching a company to then ordering profiles and filings. * The performance in Test is not indicative of the performance in Production. * Name search will retrieve all available companies in the test environment for the selected country, regardless of the search term. ## Lite and Enhanced Profiles The following jurisdictions have example **Lite and Enhanced profiles available** in the test environment: * United Kingdom (GB) * Ireland (IE) * Netherlands (NL) * Italy (IT) * Australia (AU) * Luxembourg (LU) * Singapore (SG) * France (FR) * Germany (DE) * Belgium (BE) * Estonia (EE) * Spain (ES) * United States - New York (US-NY) * United States - Florida (US-FL) * Denmark (DK) * United Arab Emirates (AE) * India (IN) * China (CN) * New Zealand (NZ) * Austria (AT) The following jurisdictions have **Lite Profile only**: * Switzerland (CH) * Canada - (CA-ALL) * Canada - Quebec - (CA-QC) * Canada - Ontario - (CA-ON) ## Registry documents A list of available filings for any company in the sandbox can be retrieved using the /companies//documents endpoint. The PDF returned will be a blank PDF. Integrators are able to test the end to end function of ordering and retrieving filings. In the test environment, the orders retrieved from the `/orders` endpoint will always return the same list, and searching for a specific order ID is not possible. ## Video tutorial - V2 test environment walkthrough [Watch: V2 test environment walkthrough](https://www.youtube.com/watch?v=BWDIH5kYFHA) # Australia (AU) Source: https://developer.kyckr.com/country-guides/australia Country guide for Australian company data including registry information, entity types, identifiers, and data availability. ## Overview **Australian Securities and Investments Commission (ASIC)** Australia's corporate regulator and company registry ASIC registers various types of legal entities under the Corporations Act, ranging from companies to registered schemes and business names. How much company data a lookup returns depends heavily on the entity type involved, which is why entity type is covered before identifiers, search, and share data below. ASIC itself runs more than one register. Its companies register covers the proprietary companies, public companies, foreign companies, registered bodies, and registered schemes that make up the rest of this guide. A second, separate government body sits alongside ASIC: the Australian Business Register (ABR), operated by the Australian Taxation Office, not ASIC. The ABR issues Australian Business Numbers (ABNs) across a far wider range of entity types than ASIC's companies register, see Entity Types below. Many companies hold both an ACN issued by ASIC and an ABN issued by the ABR, commonly registering for the ABN separately for GST or other tax purposes. The two identifiers come from two different bodies for the same company, which is part of why one should never be derived from the other, see Company Identifiers below. ASIC also operates the separate national Business Names Register. A business name is not a legal entity in its own right, so a business name search returns the person or organisation that holds the name, not a company profile. ASIC's register, not the ABR's thinner business-name lookup, is the source of record for who holds a name. ### Data Availability For company-type entities (proprietary companies, public companies, foreign companies, and registered Australian bodies): | Data point | Available | | --------------------- | ----------------------------------------------------------------------- | | Company name | Yes | | Registered address | Yes | | Legal form | Yes | | Registration date | Yes | | Status | Yes | | Representatives | Yes | | Share and member data | Varies by entity type, see Entity Types and Share and Member Data below | Registered schemes and other registrations (business names, associations, charities, and similar) follow a different profile. See Entity Types for the breakdown. ## Entity Types ASIC's term for the people who own a stake in a company is member, not shareholder. For most companies the two are the same group: everyone who holds a share is a member. This guide uses "member" throughout because a few entity types have members without having any shares at all (see limited by guarantee below), so "member" is the term that covers both cases. Entity types outside ASIC's companies register (business names, trusts, partnerships, sole traders, associations, and more) are administered by the ABR, which publishes its own [entity type list](https://abr.business.gov.au/Help/EntityTypeList) covering that wider set. The distinction that matters most for planning an integration: proprietary companies are the only entity type with member-level detail at ASIC. | Entity type | Legal form as returned | Full company profile | Share and member data | | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- | -------------------- | --------------------------------------------- | | Proprietary company | "Australian Proprietary Company Limited By Shares" | Yes | Yes, top twenty members per share class | | Public company (share capital) | "Australian Public Company" or "Australian Public Company Limited By Shares" | Yes | No | | Public company (limited by guarantee) | "Australian Public Company Limited By Guarantee" | Yes | No | | Foreign company | "Foreign Company (Overseas)" | Yes | No, register is held in the home jurisdiction | | Registered Australian body | "Registered Australian Body"\* | Yes | No | | Registered scheme | "Managed Investment Scheme" | Yes | No | | Other registrations (business names, trusts, partnerships, sole traders, associations, and more) | See the ABR entity type list above | No | Not applicable | \* Not directly observed in our own data. This is ASIC's own name for the type rather than a confirmed returned string. A shareholding result can come back empty for three different reasons, and they are not interchangeable: * **No members recorded.** Public companies and registered schemes are not required to notify ASIC of membership changes, so ASIC never holds that detail to return. * **No share capital to hold.** A company limited by guarantee has members but no shares, so there is no share register for ASIC, or anyone, to hold. * **Register held elsewhere.** A foreign company's member register stays with its home jurisdiction. ASIC's Australian record does not include it. ASIC has no public reference page equivalent to the ABR's, so its own type, class, and subclass codes are set out here instead: | Code | Description | | ------ | ------------------------------ | | `APTY` | Australian Proprietary Company | | `APUB` | Australian Public Company | | `ASSN` | Association | | `BUSN` | Business Name | | `CHAR` | Charity | | `COMP` | Community Purpose | | `COOP` | Co-Operative Society | | `FNOS` | Foreign Company (Overseas) | | `LTDP` | Limited Partnership | | `MISM` | Managed Investment Scheme | | `NONC` | Non Company | | `NRET` | Non Registered Entity | | `RACN` | Registered Australian Body | | `REBD` | Religious Body | | `RSVN` | Name Reservation | | `SOLS` | Solicitor Corporation | | `TRST` | Trust | | Code | Description | Has share capital | | ------ | ------------------------------------------------ | ----------------- | | `LMSH` | Limited By Shares | Yes | | `LMSG` | Limited By Shares and Guarantee | Yes | | `LMGT` | Limited By Guarantee | No | | `NLIA` | No Liability | Yes | | `UNLM` | Unlimited | Yes | | `EQUT` | Equity | Not applicable | | `MORT` | Mortgage | Not applicable | | `PROP` | Property | Not applicable | | `NONE` | Does Not Have An Equivalent Australian Liability | Not applicable | | `UNKN` | Liability Unknown | Not applicable | Subclasses refine a company's class further. The two most likely to appear on a public company: | Code | Description | | ------ | ----------------------- | | `LIST` | Listed Public Company | | `ULST` | Unlisted Public Company | The remaining subclasses cover narrower proprietary, foreign, and registrable-body variants: `PROP`, `EXPT`, `EXPN`, `EXPS`, `NEXT`, `NEXN`, `NEXS`, `PNPC`, `PSTC`, `HUNT`, `LISN`, `LISS`, `LXPT`, `NLTD`, `ULSN`, `ULSS`, `FXPT`, `PUBF`, `FFSP`, `RACA`, `RACO`, `NCCT`, `OABR`, `PTSH`, `SPEC`, `STFI`, `NONE`. Entity classification (proprietary, public, limited by guarantee, and so on) is drawn from the entity's legal form text. It is not returned as a separate, independently filterable attribute. ## Company Identifiers Which identifier is primary depends on the entity type: | Identifier | Format | Example | Primary for | | ------------------------------------------ | ---------------- | ------------- | --------------------------------------------------------------------------------- | | Australian Company Number (ACN) | 9-digit numeric | `123456789` | Proprietary and public companies | | Australian Registered Body Number (ARBN) | 9-digit numeric | `123456789` | Foreign companies and registered Australian bodies | | Australian Registered Scheme Number (ARSN) | 9-digit numeric | `123456789` | Registered schemes | | Australian Business Number (ABN) | 11-digit numeric | `12345678901` | Business names, non-registered entities, and a secondary identifier for companies | Some entities, such as certain non-registered entities, are tracked internally by the registry under a number that is never returned in search or profile data. For these, the ABN is the identifier that is exposed and should be treated as primary. ### ABN and ACN are related, but not interchangeable An ABN is often built from an existing ACN or ARBN plus two extra digits, so the two numbers can look related at a glance. That relationship does not hold consistently across every entity, so an ABN should never be derived from an ACN, or vice versa, by manipulating the digits. Always take each identifier from its own field. ## Search Behaviour | Search method | Supported | | ------------------------------------------- | --------- | | Search by company name | Yes | | Search by identifier (ACN, ABN, ARBN, ARSN) | Yes | Name search and identifier search behave differently. Name search matches on the text supplied, so a number typed into the name search field is matched as a literal string rather than resolved to the entity it identifies. To resolve a number to an entity, use an identifier search instead. An identifier search can return more than the identifier that was searched on. Looking a company up by its ABN, for example, returns its ACN alongside it in the same result, since both identifiers belong to the one entity. ## Share and Member Data As set out under Entity Types, only proprietary companies carry member-level detail at ASIC, and even there it is capped: ASIC keeps only the top twenty members of each share class, ranked by shareholding, plus any member tied with the twentieth. The twenty-member cap applies per share class, not per company, so a company with several classes can show far more than twenty holders in total. A class at exactly twenty may be silently truncated: nothing in the data indicates it, so treat such a class as potentially incomplete. A member's shareholding record can also carry a beneficially held indicator alongside the holding percentage, both reflecting exactly what the company itself lodged with ASIC. Beneficially held means the registered holder receives the direct benefit of the shares. Where a holding is recorded as not beneficially held, the registered holder is holding on someone else's behalf, and the register does not identify who that underlying beneficiary is. Each shareholding is also cross-referenced to the specific ASIC document the company lodged to record it. Ordering that document confirms exactly what was submitted, useful where a recorded percentage or status looks inconsistent, but it will not reveal a beneficiary that was never lodged. The register records what the company lodged, and the beneficiary's identity is not part of what is lodged: establishing who ultimately benefits from a holding that is not beneficially held is not a question the register, or any service that relays it, can answer. ## Known Limitations * **Registered schemes never carry an Australian Business Number.** ASIC does not record an ABN against a registered scheme, regardless of when it was registered. * **A business name's Australian Business Number belongs to the entity holding the name, not the business name itself.** Business names are trading names rather than legal entities: where an ABN is present against a business name record, it identifies the underlying legal entity, and the same ABN can appear against more than one business name held by that entity. # Austria (AT) Source: https://developer.kyckr.com/country-guides/austria Country guide for Austria company data including registry information and data availability. ## Overview **Firmenbuch** Official company registry of Austria Primary data source for company information ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | Yes | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Belgium (BE) Source: https://developer.kyckr.com/country-guides/belgium Country guide for Belgium company data including registry information and data availability. ## Overview **Kruispuntbank van Ondernemingen (KBO)** Official company registry of Belgium ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------------------------------------------------- | ---------------- | ------------ | -------------------------- | | Numéro d'entreprise / Ondernemingsnummer / Unternehmensnummer | 10 digit numeral | `0682594839` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Brazil (BR) Source: https://developer.kyckr.com/country-guides/brazil Country guide for Brazil company data including registry information and data availability. ## Overview **Receita Federal do Brasil** Official company registry of Brazil ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------------------------------- | ---------------- | ---------------- | -------------------------- | | CNPJ (Cadastro Nacional da Pessoa Jurídica) | 13 digit numeral | `35636288000170` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | No | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # China (CN) Source: https://developer.kyckr.com/country-guides/china Country guide for China company data including registry information, identifiers, legal forms, and data availability. ## Overview **NECIPS** (National Enterprise Credit Information Publicity System, 国家企业信用信息公示系统) Administered by the State Administration for Market Regulation (SAMR). Provincial / municipal sub-authorities exist but are normalised to NECIPS in the Kyckr response. China corporate data is sourced from NECIPS. Search, Lite Profile, and Enhanced Profile are all supported across V1 and V2. `registrationAuthority` is returned as `"NECIPS"` regardless of which provincial / municipal SAMR sub-authority is recorded at source. **Data quality improvements in progress.** CN responses are being refined for richer structured data and improved standard-value mappings; release notes will follow when updates ship. ## Company identifiers | Identifier | Format | Example | V2 location | V1 location | | --------------------------------- | ---------------------------------------------------------------- | -------------------- | --------------------------------------------------------- | ------------------------- | | Unified Social Credit Code (USCC) | 18-character alphanumeric | `91500112MA61A2D282` | `identifiers.primaryRegistrationNumber` | `codeField` | | Business Registration Number | 15-digit numeric | `110108000123456` | `identifiers.otherIdentifiers[]` with `type: "CN_BRN_CD"` | `otherIdentifiersField[]` | | Organization Code | 8 alphanumeric + check character (0-9 or X), commonly hyphenated | `10001700-2` | `identifiers.otherIdentifiers[]` with `type: "CN_ORG_CD"` | `otherIdentifiersField[]` | The USCC is the current primary CN registration number; it encodes registering authority, entity type, region, and a check digit. The Business Registration Number and Organization Code are pre-2015 legacy identifiers, retired when the USCC reform consolidated them into a single identifier; they remain available in `otherIdentifiers` for entities registered before the reform. ## Company names CN companies are registered in Chinese; an English name (when published) is a transliteration / translation. | V2 field | V1 field | Content | | ------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------- | | `companyName` | `nameField` | **Chinese-script** registered name. For CN entities the source treats the Chinese name as primary, so it occupies `companyName`. | | `englishName` | `englishNameField` | Latin-script English name when distinct from `companyName`. | For CN entities you should treat `englishName` (not `companyName`) as the Latin-script form for display in English-language contexts. ## Legal form CN legal form is populated on both `legalForm.original` (the registry-source label, in English) and `legalForm.normalized` (the [standard value](/documentation/useful-information/normalised-values#legalformnormalized)). | Source label (English) | `legalForm.normalized` | Notes | | ---------------------------------------------------------------------------------- | ------------------------- | ---------------------------------------------------------------------------------------------------- | | Limited Liability Company | `Private Limited Company` | LLC (有限责任公司) is the dominant CN form. All LLC variants map here. | | Joint-stock limited company (and variants — Public Listed / Private / State-Owned) | `Public Limited Company` | The CN 股份有限公司 form — statutorily distinct from LLC and the only CN form that can be publicly traded. | | Other Limited Company By Shares (Public Listed / Private) | `Public Limited Company` | Joint-stock variant; the "Private" qualifier here does not reduce to Private Limited. | | Limited partnership | `Limited Partnership` | 有限合伙. | | Subsidiary *(see callout below)* | `Branch` | Source-data English translation of 分公司 — semantic mistranslation; mapped to `Branch`. | | Other Limited Liability Company Branches | `Branch` | Variant of 分公司. | | Branch of a joint-stock limited company (and variants) | `Branch` | Joint-stock branch variant. | | Individually-owned business | `Sole Proprietor` | 个体工商户. | | Collective ownership (集体所有制) | `Other` | Semantic intermediate between cooperative and association. | | State-owned business unit (unincorporated) | `Other` | Unincorporated SOE form. | If the source label is absent, the legal form is inferred from the Chinese-script company-name suffix (`分公司`, `股份有限公司`, `有限责任公司`, `有限合伙`, `有限公司`). ### Branch vs Subsidiary — translation gotcha The source English translation of the Chinese **`分公司` (fēngōngsī)** is the word **`"Subsidiary"`** — a semantic mistranslation. In Chinese corporate law: * **`分公司` = branch** — no independent legal personality, an operating arm of the parent. * **`子公司` = subsidiary** — separate legal entity owned by the parent. This would map to `Private Limited Company` (or `Public Limited Company`) on its own merit. Kyckr maps both the source English string `"Subsidiary"` and the Chinese name-suffix `分公司` to `Branch` in the normalised response, so integrators see the correct concept. The raw source label is preserved in `legalForm.original`. ## Status CN `legalStatus.original` carries the registry-source English string (which varies across cohorts — multiple parallel translations of 在营 / 开业 appear in the wild). `legalStatus.normalized` maps to one of the standard values: | `legalStatus.original` (English) | Source Chinese | `legalStatus.normalized` | | -------------------------------- | -------------- | ------------------------ | | `In operation (opening)` | `在营（开业）` | `Active` | | `In Business` | `在营` | `Active` | | `Active` | (various) | `Active` | | `Deregistered` | `注销` | `Inactive` | ## Activity / industry codes CN activities populate `activities[]` with: * `activities[].description` — free-text Chinese / English description (e.g. `"Water conservancy, environment and public facility management"`) * `activities[].code` — registry-source industry code where present * `activities[].classificationScheme` — `null` (CN does not carry an explicit classification scheme — NACE / NAICS not used) * `activities[].type` — `"Primary"` when the source flags the activity as primary ## Address CN `address` returns the flat `fullAddress` only — there is no component parsing (`city`, `region`, `streetName`, etc. are null). * `country`: `"China"` * `isoCode`: `"CN"` * `postcode`, `rawAddressLines`, structured components: null ## Capital structure CN entities populate the standard V2 `capital` / `totalCapital` shape: * Currency: RMB (`人民币元` at source; surfaced as `RMB` in normalised output) * `totalCapital.type`: typically `Registered` — the registry reports registered-capital amount (rather than authorized or paid-in). See [Normalised values](/documentation/useful-information/normalised-values#totalcapitaltype). * Thousands-comma source values (e.g. `"302,973,182"`) are normalised to numeric `totalValue` Per-class shareholding capital is surfaced inside `shareholdings[]`. ## Shareholders CN shareholders are returned in V2 `shareholdings[].shareholders` split by entity type: * Corporate shareholders → `shareholdings[].shareholders.corporations[]` * Natural-person shareholders → `shareholdings[].shareholders.individuals[]` Subscribed-capital values that arrive with a currency suffix at source (e.g. `"156,000,000 RMB"`) are normalised to numeric `totalNominalValue` with the currency on the parent capital entry. ## Representatives / directors CN representatives populate V2 `representatives.individuals[]` with English and Chinese name, role, ID information, address, and appointment / outgoing dates. Common CN-specific roles (mapped to standard role values via the director-role lookup): * `Director`, `Supervisor`, `Chairman`, `Vice Chairman`, `Manager`, `General Manager`, `Executive director`, `Legal Representative`, `Board Secretary, Financial Officer of a Listed Company` * Compound roles follow most-significant-first (e.g. `"Manager, Director"` → `MANAGER`; `"Director, General Manager"` → `DIRECTOR`) * `"person in charge"` (the natural-person 负责人 commonly recorded for branch entities) → `LEGAL_REPRESENTATIVE` ## Contact details CN entities consistently surface contact details on V2 `contactDetails`: * `contactDetails.telNumber` * `contactDetails.email` (with `"N/A"` placeholders filtered out) * `contactDetails.website` (with `"N/A"` placeholders filtered out) This is CN-specific behaviour — HK and JP responses do not include contact details. ## Data Availability | Data Point | Available | | ------------------ | ------------------------------- | | Company Name | Yes (Chinese and Latin) | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Varies by entity type | | Share Capital | Yes (not surfaced for branches) | | Activities | Yes | | Contact Details | Yes | | UBOs | No | ## Additional resources * [Normalised values guide](/documentation/useful-information/normalised-values) * [Company V2 API Reference](/company-v2/api-reference/overview) # Denmark (DK) Source: https://developer.kyckr.com/country-guides/denmark Country guide for Danish company data including registry information, identifiers, legal forms, ownership bands, and data availability. ## Overview **CVR** (Det Centrale Virksomhedsregister) Central Business Register Denmark's Central Business Register (CVR) is the official registry for all business entities in Denmark and Greenland. It provides comprehensive company data including registration details, ownership information, and management structure. ## Company Identifiers | Identifier | Format | Example | Notes | | ----------------------- | ----------------- | ------------ | ---------------------------------------------- | | CVR Number (CVR-nummer) | 8-digit numeric | `36734205` | Primary identifier for all registered entities | | VAT Number | `DK` + CVR number | `DK36734205` | CVR number prefixed with country code | | P-Number (pNummer) | 10-digit numeric | `1001564464` | Production unit / establishment identifier | ### Additional Internal Identifiers | Identifier | Description | | -------------------------------- | ---------------------------------------------------- | | Entity Number (enhedsNummer) | Internal CVR system-level ID (up to 10 digits) | | Business Key (forretningsnoegle) | External registration number on participant entities | ## Search Capabilities | Search Method | Supported | | ---------------------- | -------------------------- | | Search by CVR number | Yes | | Search by company name | Yes | | Search by P-number | Yes (for production units) | ## Data Availability | Data Point | A/S | ApS | ENK | I/S / K/S | Non-Profits | Public Entities | | --------------- | ----------- | ----------- | ----------- | ----------- | ----------- | --------------- | | Basic profile | Yes | Yes | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | Yes | Yes | | Capital | Yes | Yes | No | Varies | No | No | | Shareholders | Yes | Yes | No | Varies | Limited | No | | Management | Yes | Yes | Yes | Yes | Yes | Limited | | Activities | Yes | Yes | Yes | Yes | Yes | Yes | | Establishments | Yes | Yes | Yes | Yes | Yes | Yes | | Contact details | If provided | If provided | If provided | If provided | If provided | If provided | **A/S** = Public Limited Company, **ApS** = Private Limited Company, **ENK** = Sole Proprietorship, **I/S** = General Partnership, **K/S** = Limited Partnership ## Legal Forms Denmark has an extensive set of legal form codes. Below are the most common categories. | Code | Abbreviation | Danish Name | English | Notes | | ---- | ------------ | --------------------------- | ----------------------------- | ------------------------------------------ | | 60 | A/S | Aktieselskab | Public Limited Company | Min capital DKK 400,000 | | 80 | ApS | Anpartsselskab | Private Limited Company | Min capital DKK 40,000 | | 81 | IVS | Iværksætterselskab | Entrepreneurial Company | Discontinued since 2019, min capital DKK 1 | | 290 | E/S | SE-selskab | European Company (SE) | Societas Europaea | | 285 | FIV | Særlig finansiel virksomhed | Special Financial Undertaking | Regulated financial entity | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | --------------------------------- | ------------------------------- | | 10 | ENK | Enkeltmandsvirksomhed | Sole Proprietorship | | 15 | PMV | Personligt ejet Mindre Virksomhed | Personally Owned Small Business | | 20 | DØD | Dødsbo | Estate of Deceased | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ------------------------------------ | --------------------------------- | | 30 | I/S | Interessentskab | General Partnership | | 40 | K/S | Kommanditselskab | Limited Partnership | | 45 | MSS | Medarbejderinvesteringsselskab | Employee Investment Company | | 50 | PAR | Partrederi | Shipping Partnership | | 70 | KAS | Kommanditaktieselskab/Partnerselskab | Limited Partnership Company (P/S) | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ---------------------------------------------- | ------------------------------------------ | | 130 | ANS | Andelsselskab (-forening) | Cooperative Society | | 140 | ABA | Andelsselskab (-forening) med begrænset ansvar | Cooperative Society (Limited Liability) | | 150 | FBA | Forening eller selskab med begrænset ansvar | Association or Company (Limited Liability) | | 151 | SMA | Selskab med begrænset ansvar | Company with Limited Liability (SMBA) | | 152 | FMA | Forening med begrænset ansvar | Association with Limited Liability (FMBA) | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | --------------------------------------- | ------------------------------------------- | | 90 | FON | Fonde og andre selvejende institutioner | Foundations and Self-Governing Institutions | | 100 | EFO | Erhvervsdrivende fond | Commercial Foundation | | 110 | FOR | Forening | Association | | 115 | FFO | Frivillig forening | Voluntary Association | | 95 | TRU | Trust | Trust | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ------------------------------------------ | ------------------------------------ | | 170 | FAS | Filial af udenlandsk aktieselskab | Branch of Foreign Public Ltd. Co. | | 190 | FBA | Filial af udenlandsk virksomhed | Branch of Foreign Ltd. Liability Co. | | 200 | - | Filial af anden udenlandsk virksomhedsform | Branch of Other Foreign Entity | | 210 | UDL | Anden udenlandsk virksomhed | Other Foreign Entity | | 291 | FES | Filial af SE-selskab | Branch of European Company (SE) | | 520 | GUS | Grønlandsk afdeling af udenlandsk selskab | Greenlandic Branch of Foreign Co. | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | -------------------------------- | ----------------------------- | | 230 | STA | Statslig administrativ enhed | State Administrative Unit | | 235 | SOV | Selvstændig offentlig virksomhed | Independent Public Enterprise | | 245 | REG | Region | Region | | 250 | KOM | Primærkommune | Municipality | | 260 | FKI | Folkekirkelige Institutioner | Church Institutions | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ------------------------------------------------------- | ------------------------------------------ | | 160 | EØF | Europæisk Økonomisk Firmagruppe | European Economic Interest Grouping (EEIG) | | 195 | SCE | SCE-selskab | European Cooperative Society (SCE) | | 220 | FEØ | Fast forretningssted af Europæisk økonomisk Firmagruppe | Permanent Establishment of EEIG | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ------------------------------------------ | -------------------------------- | | 240 | AMT | Amtskommune | County Municipality (historical) | | 270 | EUO | Enhed under oprettelse i Erhvervsstyrelsen | Entity Being Registered | | 280 | ØVR | Øvrige virksomhedsformer | Other Legal Forms | | 990 | UOP | Uoplyst virksomhedsform | Undisclosed Legal Form | ## Status Codes ### Primary Status Values | Danish Status | English | Normalized | | ---------------------------------- | ------------------------------------- | ---------- | | NORMAL | Active / Normal | Active | | OPLØST | Dissolved | Inactive | | OPLØST EFTER KONKURS | Dissolved after Bankruptcy | Inactive | | OPLØST EFTER ERKLÆRING | Dissolved after Declaration | Inactive | | OPLØST EFTER FRIVILLIG LIKVIDATION | Dissolved after Voluntary Liquidation | Inactive | | OPLØST EFTER FUSION | Dissolved after Merger | Inactive | | OPLØST EFTER SPALTNING | Dissolved after Demerger | Inactive | | OPHØRT | Ceased | Inactive | | KONKURS | Bankrupt | Inactive | | TVANGSOPLØST | Compulsorily Dissolved | Inactive | | SLETTET | Deleted | Inactive | | UNDER TVANGSOPLØSNING | Under Compulsory Dissolution | Distressed | | UNDER FRIVILLIG LIKVIDATION | Under Voluntary Liquidation | Distressed | | UNDER KONKURS | Under Bankruptcy | Distressed | | UNDER REKONSTRUKTION | Under Reconstruction | Distressed | Some entity types (particularly sole proprietorships, associations, and public entities) may use a simplified status system with values like "Aktiv" (Active) or "Ophørt" (Ceased). ## Activity Codes Denmark uses **DB07** (Dansk Branchekode 2007), the Danish implementation of **NACE Rev. 2**. | Field | Description | Example | | ---------------------------- | ------------------------------ | --------------------- | | Industry code (branchekode) | 6-digit NACE-compatible code | `620100` | | Industry text (branchetekst) | Activity description in Danish | Computerprogrammering | | Classification scheme | DB07\_NACErev2 | - | The first 4 digits align with the EU NACE standard; the last 2 digits provide Danish sub-detail. Companies may have a main activity (hovedbranche) and up to three secondary activities (bibranche). ## Ownership Data **Ownership is reported as bands, not exact percentages.** CVR reports ownership as ranges rather than precise values. This is a regulatory feature of Danish company law, not a data limitation. ### Ownership Bands | Band | Display Value | | ------------ | ------------- | | 5-9.99% | 5-9.99% | | 10-14.99% | 10-14.99% | | 15-19.99% | 15-19.99% | | 20-24.99% | 20-24.99% | | 25-33.32% | 25-33.32% | | 33.33-49.99% | 33.33-49.99% | | 50-66.66% | 50-66.66% | | 66.67-89.99% | 66.67-89.99% | | 90-99.99% | 90-99.99% | | 100% | 100% | Ownership data includes both share capital ownership and voting rights, which may be reported in different bands for the same shareholder. ## Address Format Danish addresses follow a structured format: **Standard format:** ```text theme={null} Højbro Plads 10, 1200 København K, Denmark ``` **With floor and apartment:** ```text theme={null} Vesterbrogade 42, 3. th, 1620 København V, Denmark ``` ### Address Components | Component | Description | Example | | ------------------------------ | --------------------------- | ---------------------- | | Street name (vejnavn) | Street name | Højbro Plads | | House number (husnummerFra) | Building number | 10 | | Floor (etage) | Floor number | 3 | | Side door (sidedoer) | Apartment indicator | th (til højre = right) | | Postal code (postnummer) | 4-digit postal code | 1200 | | Postal district (postdistrikt) | City/area name | København K | | Municipality (kommune) | Administrative municipality | KØBENHAVN | ## Capital Structure Standard minimum capital requirements: | Legal Form | Minimum Capital | | --------------------- | ------------------------------- | | A/S (Public Limited) | DKK 400,000 | | ApS (Private Limited) | DKK 40,000 | | IVS (Entrepreneurial) | DKK 1 (discontinued since 2019) | Capital is typically reported in Danish Kroner (DKK). If no currency is specified in the registry data, DKK is assumed. ## Representatives ### Common Roles | Danish Role | English | Description | | ------------------------ | --------------------- | --------------------------- | | DIREKTØR | Director | Company director | | ADMINISTRERENDE DIREKTØR | CEO | Chief Executive Officer | | BESTYRELSESFORMAND | Chairman of the Board | Board chairman | | NÆSTFORMAND | Deputy Chairman | Vice chairman | | BESTYRELSESMEDLEM | Board Member | Board member | | SUPPLEANT | Alternate | Substitute/alternate member | | REVISOR | Auditor | Company auditor | | LIKVIDATOR | Liquidator | Appointed for dissolution | | STIFTER | Founder | Company founder | | PROKURA | Procurator | Signatory authority holder | ## Establishments (Production Units) Danish companies can have multiple production units (penheder), representing physical locations where the company operates. Each is identified by a unique 10-digit P-number. Production unit details (name, address, activities) may require additional lookups. The primary company lookup returns P-numbers and validity periods for each unit. ## Implementation Notes **Empty results possible**: Some CVR numbers may return no results if the entity does not exist in the current registry index. **Historical data model**: All Danish company data is versioned with validity periods. Current values have no end date. For dissolved companies, all records have end dates, and the most recent values are used. ### Known Limitations 1. **Ownership bands**: Exact shareholding percentages are not available - only the band (range) is reported 2. **Establishment details**: Production unit records contain only identifiers and dates; detailed branch information requires separate lookups 3. **Status variations**: Different entity types may use different status reporting systems # Estonia (EE) Source: https://developer.kyckr.com/country-guides/estonia Country guide for Estonian company data including registry information, identifiers, legal forms, and data availability. ## Overview **RIK** (Registrite ja Infosüsteemide Keskus) Centre of Registers and Information Systems Estonia's business register (Äriregister) is the official registry for all legal entities in Estonia. It is maintained by the Centre of Registers and Information Systems (RIK) and provides comprehensive company data including registration details, shareholders, and management information. ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------------------------------ | --------------- | ------------- | ------------------------------------------------- | | Registration Number (Registrikood) | 8-digit numeric | `10422334` | Unique identifier for all Estonian legal entities | | VAT Number (Käibemaksukohustuslase number) | `EE` + 9 digits | `EE102269053` | Not all companies have VAT registration | ### Registration Number Patterns * Numbers starting with **1xxxxxxx** are typically older companies * Numbers starting with **8xxxxxxx** or **9xxxxxxx** are typically newer or special entities ### VAT Number Details VAT data includes: * VAT number * Active status (current VAT status) * Registration date * Deregistration date (if applicable) ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------------------------------- | | Search by registration number | Yes | | Search by company name | Yes | | Search by VAT number | Partial (via registration lookup) | ## Data Availability | Data Point | AS | OÜ | MTÜ | FIE | KÜ | | -------------------- | ------------- | ------------- | ------------- | ------------- | ------- | | Registration details | Yes | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | Limited | | Capital | Yes | Yes | No | No | No | | Shareholders | Yes | Yes | Yes | No | No | | Management board | Yes | Yes | Yes | No | Yes | | VAT number | If registered | If registered | If registered | If registered | No | | Activities (NACE) | Yes | Yes | Yes | Yes | Limited | **AS** = Public Limited Company, **OÜ** = Private Limited Company, **MTÜ** = Non-profit, **FIE** = Sole Proprietor, **KÜ** = Apartment Association ## Legal Forms | Code | Estonian | English | Notes | | ---- | ------------ | ----------------------- | ---------------------------- | | AS | Aktsiaselts | Public Limited Company | Min capital EUR 25,000 | | OÜ | Osaühing | Private Limited Company | Min capital EUR 2,500 | | TÜ | Täisühing | General Partnership | Unlimited liability | | UÜ | Usaldusühing | Limited Partnership | At least one limited partner | | Code | Estonian | English | Notes | | ---- | ----------------------------- | ----------------------- | ------------------------ | | FIE | Füüsilisest isikust ettevõtja | Sole Proprietor | Natural person business | | MTÜ | Mittetulundusühing | Non-profit Organisation | No profit distribution | | SA | Sihtasutus | Foundation | Asset-based legal entity | | KÜ | Korteriühistu | Apartment Association | Housing cooperative | | Code | Estonian | English | Notes | | ---- | -------- | ------- | ---------------------- | | - | Filiaal | Branch | Foreign company branch | ## Status Codes | Code | Estonian | English | Normalized Status | | ---- | ------------------------------------ | ----------------------------- | ----------------- | | R | Registrisse kantud | Entered into the register | Active | | L | Likvideerimisel | In liquidation | Distressed | | N | Pankrotis | In bankruptcy | Distressed | | K | Kustutatud | Deleted | Inactive | | KN | Kustutatud pankroti lõppemisel | Deleted following bankruptcy | Inactive | | KL | Kustutatud likvideerimise lõppemisel | Deleted following liquidation | Inactive | ## Activity Codes Estonia uses **EMTAK** (Eesti Majanduse Tegevusalade Klassifikaator), which maps to **NACE Rev. 2**. | Field | Description | Example | | ----------- | ------------------------------- | ---------------------------------------------------- | | `nace_code` | NACE Rev. 2 code format (XX.XX) | `70.20` | | `name` | Activity description in English | Business and other management consultancy activities | | `version` | NACE version | `2.1` | ## Address Format Estonian addresses use a component-based structure. Example formats: **Standard format:** ```text theme={null} Harju maakond, Tallinn, Kesklinna linnaosa, A. Weizenbergi tn 32 ``` **With apartment number:** ```text theme={null} Ida-Viru maakond, Narva linn, Pähklimäe tn 6-127 ``` ### Address Components | Component | Maps To | Example | | ------------------------ | --------------- | ------------------ | | County (maakond) | Region | Harju maakond | | Municipality | Municipality | Tallinn | | Settlement unit | City | Tallinn | | City district (linnaosa) | City (fallback) | Kesklinna linnaosa | | Thoroughfare (tn) | Street Name | A. Weizenbergi tn | | Building number | Street Number | 32 | ## Implementation Notes **Address may be null**: Some entity types (particularly apartment associations) may have no registered address in the registry data. **Non-profit shareholders**: Non-profit organisations (MTÜ) have members rather than shareholders with share capital. Ownership data for these entities will show percentage ranges (0-100%) rather than exact percentages, indicating that precise ownership cannot be determined from the registry data. ### Representatives Estonian companies distinguish between several types of officials: | Role | Code | Description | | ------------------------- | ---- | ---------------------------------------------------------------- | | Management Board Members | JUHL | Primary operational management (Juhatuse liikmed) | | Supervisory Board Members | NOUK | Oversight function, typically for AS companies (Nõukogu liikmed) | | Procuration Holders | - | Special commercial power of attorney (Prokuristid) | # Finland (FI) Source: https://developer.kyckr.com/country-guides/finland Country guide for Finland company data including registry information, identifiers (Y-tunnus), legal forms, status codes, and implementation notes. ## Overview **PRH** (Patentti- ja rekisterihallitus) Finnish Patent and Registration Office; maintains the Trade Register (Kaupparekisteri) Finnish company data in the Enhanced Profile is sourced from the Trade Register (Kaupparekisteri) maintained by PRH. You get the Business ID (Y-tunnus) as the primary identifier, company name, legal form, status, registered address, share capital when available, and legal representatives. ## Company Identifiers | Identifier | Format | Example | Notes | | ---------------------- | --------------------------------- | ------------ | ----------------------------------------------------------------- | | Y-tunnus (Business ID) | 7 digits + hyphen + 1 check digit | `2552951-7` | Primary company identifier; check digit uses modulo-11 validation | | VAT Number | FI + 8 digits | `FI25529517` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ------------------------------------------- | --------- | | Search by registration number (Business ID) | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | Yes | | UBOs | No | ## Legal Forms The Enhanced Profile returns legal form as an English description. The registry uses form codes; the main types you may see are listed below. | Code | Finnish | English | | ---- | ------------------- | ---------------------- | | OY | Osakeyhtiö | Limited company | | OYJ | Julkinen osakeyhtiö | Public limited company | | Code | Finnish | English | | ---- | -------------------------------- | ------------------- | | AY | Avoin yhtiö | Partnership | | KY | Kommandiittiyhtiö | Limited partnership | | YEH | Yksityinen elinkeinonharjoittaja | Private trader | | Code | Finnish | English | | ---- | ------------ | ----------------- | | OK | Osuuskunta | Co-operative | | OP | Osuuspankki | Co-operative bank | | SP | Säästöpankki | Savings bank | | Code | Finnish | English | | ---- | ------------------------------------------- | ------------------------------------------------------- | | SE | Eurooppayhtiö | European company | | SCE | Eurooppaosuuskunta | European co-operative society | | SCP | Eurooppaosuuspankki | European co-operative bank | | ETY | Eurooppalainen taloudellinen etuyhtymä | European economic interest grouping | | ETS | ETEY:n sivuliike Suomessa | Finnish branch of a European economic interest grouping | | SL | Ulkomaisen elinkeinonharjoittajan sivuliike | Branch of a foreign trader | | Code | Finnish | English | | ---- | ---------------------------------- | ---------------------------------------------- | | SÄÄ | Säätiö | Foundation | | TYH | Taloudellinen yhdistys | Association for carrying on economic activity | | AYH | Aatteellinen yhdistys | Non-profit association | | AOY | Asunto-osakeyhtiö | Housing company | | ASY | Asumisoikeusyhdistys | Right-of-occupancy association | | KKOY | Keskinäinen kiinteistöosakeyhtiö | Limited liability joint-stock property company | | VLL | Valtion liikelaitos | State-owned company | | VOY | Vakuutusosakeyhtiö | Limited insurance company | | VOJ | Julkinen vakuutusosakeyhtiö | Public limited insurance company | | KVY | Keskinäinen vakuutusyhtiö | Mutual insurance company | | KVJ | Julkinen keskinäinen vakuutusyhtiö | Public mutual insurance company | | HY | Hypoteekkiyhdistys | Mortgage society | | VY | Vakuutusyhdistys | Insurance association | ## Status Codes The Enhanced Profile returns a status description and a normalized status (Active or Inactive). | Code | Finnish | English | Normalized Status | | ---- | ------------ | --------------- | ----------------- | | R | Rekisterissä | In the register | Active | | L | Lakannut | Dissolved | Inactive | | P | — | (other state) | Inactive | ## Address Format Addresses in the Enhanced Profile include street name, city, postcode, and country (Finland). **Example format:** ```text theme={null} Mannerheimintie 10, 00100 Helsinki, Finland ``` ### Address components in the profile | Component | Description | | ---------- | ---------------------------- | | streetName | Street address (single line) | | city | City or locality | | postcode | Postal code | | country | Finland | ## Implementation Notes The Finnish registry holds data in Finnish and Swedish. The Enhanced Profile returns English descriptions for legal form and representative roles. ### Representatives Representatives in the Enhanced Profile include role (in English), an active flag, birth date when available, and name. Roles you may see include: | Role | | ------------------------------------- | | Chairperson | | Vice-chairperson | | Ordinary member | | Deputy member | | Managing Director | | Substitute for the Managing Director | | Deputy Managing Director | | Holder of procuration | | Representative | | Substitute representative | | Director | | Auditor | | Additional auditor | | Auditor with principal responsibility | | Liquidator | | Deputy liquidator | | In charge of administration | | House Manager | | Trader | Place of residence is not included in the profile. ### Capital When share capital is available, the Enhanced Profile returns **totalCapital** with: * **totalValue**: Capital amount * **quantity**: Amount of shares * **currency**: Currency code (e.g. EUR) No per-share-class breakdown is returned; only total capital is provided. # France (FR) Source: https://developer.kyckr.com/country-guides/france Country guide for France company data including registry information, identifiers (SIREN, SIRET), legal forms, status codes, APE activities, and implementation notes. ## Overview **RNE** (Registre National des Entreprises) Official company registry of France French company data is sourced from the Registre National des Entreprises (RNE) via the Institut National de la Propriété Industrielle (INPI). The data includes the SIREN as the primary company identifier, establishments identified by SIRET, representatives with INPI role codes, capital (amount, currency, fixed or variable), and APE (NAF) activity classification. ## Company Identifiers | Identifier | Format | Example | Notes | | ---------- | ---------------------------------- | ---------------- | ------------------------------------------------------------------------------------ | | SIREN | 9-digit numeric | `325013555` | Primary company identifier; used for search and profile requests | | SIRET | 14-digit numeric (9 SIREN + 5 NIC) | `32501355500012` | Identifies each establishment (principal and secondary); NIC is establishment number | | VAT Number | FR + digits | `FR12345678901` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ------------------------------------- | --------- | | Search by registration number (SIREN) | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | Yes | | Establishments | Yes | | UBOs | No | ## Legal Forms Legal form is provided from INPI/INSEE forme juridique (numeric code), mapped to a French description in the API response. Unmapped codes may appear as "Form" followed by the code. | Code | Description | | ---- | -------------------------------------------------------------------- | | 5710 | SAS, société par actions simplifiée (Simplified Joint Stock Company) | Other numeric codes (e.g. 5202, 5499, 5599, 6220, 6540, 6565, 6599) may appear in data; the full list is maintained by INSEE. Occasionally the source may provide a text description (e.g. Société en nom collectif) instead of a code. ## Status Codes Status is derived from cessation and dissolution indicators in the registry. Normalized values are **Active**, **Distressed**, or **Inactive**. | Condition | Normalized Status | | ---------------------------------------------------------------------------------------------------------------------- | ----------------- | | No cessation details, or dissolution false and no dissolution/disappearance date | Active | | Dissolution in progress (e.g. liquidator appointed, registration maintained) | Distressed | | Effective cessation date or removal from register present; or dissolution and legal entity disappearance both complete | Inactive | Granular cessation information is available in status details: removal date, effective date, total activity cessation date, liquidation closure date, dissolution type, liquidator appointment publication (date and journal), and principal establishment formality status or closure/transfer dates when applicable. ## Activity Codes France uses **APE** (Activité Principale Exercée), aligned with **NAF rev. 2**, for business activity classification. | Field | Description | Notes | | ----------- | -------------------- | --------------------------------------------------------------------------- | | code | APE/NAF code | Company-level code is the primary activity | | description | Activity description | From company objet or establishment description | | type | Primary or Secondary | Primary = company-level; Secondary = from principal or other establishments | Activities from closed establishments (closure effective date present) or activities with an end date are excluded from the response. ## Address Format Company and establishment addresses use a component-based structure. **Example format:** ```text theme={null} 12, rue de la Paix, 75002 Paris, France ``` ### Address Components | Source Component | Maps To | Description | | -------------------------------- | ---------------- | --------------------------------------- | | numVoie | streetNumber | Street number | | typeVoie + voie (establishments) | streetName | Street type and name (e.g. rue, avenue) | | voie (company address) | streetName | Street name | | complementLocalisation | (in fullAddress) | Additional location detail | | distributionSpeciale | (in fullAddress) | Special distribution (e.g. Bâtiment A) | | commune | city | Commune/town name | | codePostal | postcode | 5-digit postal code | | pays | country | Country name | ## Implementation Notes ### Representatives Representatives are split into corporations (legal entities) and individuals. Each has a role derived from the INPI role code (roleEntreprise), mapped to a French role name. Known mappings include: | Code | Role (French) | | ---- | --------------------------------- | | 53 | Directeur Général | | 71 | Commissaire aux comptes titulaire | | 99 | Autre | Other codes (e.g. 13, 28, 29, 30, 40, 51, 65, 70, 72, 73, 75) may appear in data; unmapped codes are returned as "Role" followed by the code. Corporations include SIREN and company name; individuals include name, birth date, and place of residence (city, postcode, country). ### Establishments Each company has a principal establishment and zero or more other establishments. Each establishment includes: * **id**: SIRET (14 digits) * **isPrincipal**: true for the principal establishment * **isActive**: false if closure effective date or end-of-activity date is present * **creationDate** / **endDate**: from establishment activity or registration dates * **address**: same component structure as above (typeVoie + voie for street name) ### Capital When capital is present in the registry: * **totalCapital** includes total value, currency, and type (**Fixed** or **Variable** from the capitalVariable indicator). * The **capital** array contains nominal value and currency. It is populated only when a capital amount is present. ### Status details The status details array includes the number of open establishments and, when present, cessation-related keys (e.g. dissolution indicator, removal date, effective date, liquidation closure date, dissolution type, liquidator appointment publication, principal establishment formality status or closure/transfer dates). Use these for granular visibility into company and establishment status. # Germany (DE) Source: https://developer.kyckr.com/country-guides/germany Country guide for Germany company data including registry information and data availability. ## Overview **Bundesanzeiger Verlagsgesellschaft mbH & Common register portal of the German federal states (Handelsregister)** Official company registry of Germany ## Company Identifiers | Identifier | Format | Example | Notes | | ---------------------- | ------------ | ------------ | -------------------------- | | Handelsregisternummern | Alphanumeric | `HRB 130192` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Gibraltar (GI) Source: https://developer.kyckr.com/country-guides/gibraltar Country guide for Gibraltar company data including registry information and data availability. ## Overview **Companies House Gibraltar** Official company registry of Gibraltar ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | No | | Shareholders | No | | Share Capital | Yes | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Greece (GR) Source: https://developer.kyckr.com/country-guides/greece Country guide for Greece company data including registry information and data availability. ## Overview **General Commercial Register (G.E.M.I.)** Official company registry of Greece ## Company Identifiers | Identifier | Format | Example | Notes | | ----------- | ------- | -------------- | -------------------------- | | GEMI Number | Numeric | `157741701000` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Guernsey (GG) Source: https://developer.kyckr.com/country-guides/guernsey Country guide for Guernsey company data including registry information and data availability. ## Overview **Guernsey Registry** Official company registry of Guernsey ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Hong Kong (HK) Source: https://developer.kyckr.com/country-guides/hong-kong Country guide for Hong Kong company data including registry information, identifiers, legal forms, bilingual name handling, and data availability. ## Overview **ICRIS** (Integrated Companies Registry Information System) for companies + **BRO** (Business Registration Office) for sole proprietorships Operated by the Companies Registry of Hong Kong and the Inland Revenue Department respectively Hong Kong corporate data is sourced from ICRIS for Companies Registry entities and from the Business Registration Office for sole proprietorships. Search, Lite Profile, and Enhanced Profile are all supported across V1 and V2. Registry Documents search is supported for CR entities (94+ filing types observed in production); sole proprietorships and mutual funds are not supported on the document-search endpoint. **Data quality improvements in progress.** HK responses are being refined for richer structured data and improved standard-value mappings; release notes will follow when updates ship. ## Company identifiers The HK identifier is the **Company Registration Number**: typically an 8-digit zero-padded numeric string. Different prefixes indicate different entity types, and sole proprietorships use a hyphenated format. | Identifier | Format | Example | Notes | | ------------------- | --------------------------- | -------------- | ------------------------------------------------------------- | | Standard CR Number | 8-digit numeric (no prefix) | `03645219` | Private Ltd and Public Ltd HK-incorporated companies | | Non-HK company | `F-` prefix | `F0008739` | Registered non-Hong Kong companies (foreign) | | Guarantee company | `C-` prefix | `C0486085` | Companies limited by guarantee, charities, special categories | | Mutual Fund | `MF-` prefix | `MF001910` | Investment funds | | Sole proprietorship | `NNNNNNN-NNN` (hyphenated) | `41409990-000` | Business Registration; suffix is branch number | In V2 the CR Number is `companyNumber` and is also the registry-encoded portion of the V2 `id`. In V1 it appears as `codeField`. **Do not confuse with the Business Registration Number (BRN).** The BRN is a separate document issued by the Inland Revenue Department. The Company Registration Number (above) is the correct identifier for API requests. ## Entity types Six entity types are returned for HK. The Kyckr response shape is consistent across all six (transformation reconciles registry-specific source-data differences); the matrix at the bottom of this guide details which fields are populated per entity type. | Entity type | Coverage source | | --------------------------------------- | ---------------------------- | | Private company limited by shares | ICRIS | | Public company limited by shares | ICRIS | | Registered non-Hong Kong company | ICRIS | | Mutual Fund | ICRIS | | Company limited by guarantee | ICRIS | | Sole proprietorship (`個人 / INDIVIDUAL`) | Business Registration Office | ## Company names Hong Kong companies frequently hold both an English and a Traditional Chinese registered name. Three Kyckr fields carry HK name information: | V2 field | V1 field | Content | | --------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `companyName` | `nameField` | The **primary** registered name as held at source: for most HK-incorporated companies this is the English (Latin-script) name. For some registered non-HK companies (e.g. Bank of China subsidiaries) the source treats the **Chinese** name as primary, and `companyName` carries the Chinese name. | | `englishName` | `englishNameField` | Populated only when `companyName` is non-Latin AND a distinct Latin-script name is available at source. This is the recovery field for the registered-non-HK-company case where the English name is not in the primary slot. | | `aliases[]` (type: `Original Language`) | `aliasesField` | The source original-language name when distinct from `companyName`: for normal HK entities (English primary) this is where the Traditional Chinese name appears. Suppressed when `englishName` is populated, to avoid mislabelling an English string as "Original Language". | This means: * **Normal HK case (Latin primary):** `companyName` = English, `englishName` = `null`, `aliases[]` = Chinese (Original Language). * **Bank of China-style case (Chinese primary):** `companyName` = Chinese, `englishName` = English, `aliases[]` = `null`. In both cases the English name is reachable on a single field: `companyName` when present there, otherwise `englishName`. Some Chinese names appear in parentheses at the registry (e.g. `(中銀集團人壽保險有限公司)`); these are preserved as supplied. Previous names, including bilingual previous-name pairs, are surfaced in `previousNames`. ## Legal form HK Lite Profile populates `legalForm.normalized` only when the regulator-mandated Chinese suffix `有限公司` appears on the original-script name. This is the official suffix that signals an HK Private Limited Company; emission is rule-based, not heuristic. | Source signal | `legalForm.normalized` | Notes | | ------------------------------------------------------------- | ------------------------- | --------------------------------------------------------------------------------------- | | Chinese name contains `有限公司` | `Private Limited Company` | Regulator-mandated suffix; emitted when present | | English-only registered names (PLC, FOUNDATION, FUND, BANK …) | `null` | Source rule: emit when the source has the signal; null when it does not | | Lite payload missing the suffix entirely | `null` | E.g. HSBC BANK PLC, BOCHK CHARITABLE FOUNDATION, HSBC ASSET MANAGEMENT INVESTMENT FUNDS | HK Enhanced Profile surfaces an explicit entity-type signal and populates `legalForm.normalized` for all entity types (`Private Limited Company`, `Public Limited Company`, `Association`, `Collective Investment Vehicle`, `Foreign Registered Body`, `Sole Proprietor`, etc.). ## Status `legalStatus.original` carries the registry-source string; `legalStatus.normalized` maps to one of the standard values: | `legalStatus.original` | Meaning | `legalStatus.normalized` | | ---------------------------------------- | ------------------------------------------------------------- | ------------------------ | | `Live` | Active and in good standing | `Active` | | `Dissolved` | No longer exists (dissolution method on `legalStatus.detail`) | `Inactive` | | `Ceased place of business` | Non-HK company ceased HK operations | `Inactive` | | `Live, Commenced dormancy on YYYY-MM-DD` | Active but dormant (compound status with date) | `Active` | ### Dissolution methods For dissolved companies, the dissolution method is surfaced alongside the status: * Dissolved by Deregistration: administrative removal from register * Dissolved by Winding Up (Others): court-ordered or other winding up * Dissolved by Members' Voluntary Winding Up: solvent company, members' choice * Dissolved by Creditors' Voluntary Winding Up: insolvent company, creditors' process * Deregistration in progress: company may still be `Live` while deregistration is processed A separate non-dissolution marker, "Licence granted to dispense with `Limited` and/or `有限公司` in company name", is a special licence, not a dissolution. ## Capital structure CR entities populate the standard V2 `capital` / `totalCapital` shape. Mutual funds, sole proprietorships, and guarantee companies do not have capital data. * Issued and paid-up capital are usually identical for HK-incorporated companies. * Paid-up capital is null for registered non-HK companies. * **Multi-currency entries are common**: some entities have capital entries with different currencies (e.g. GBP + USD on the same company). Do not assume one entity = one currency. * Decimal values are returned as decimals. ### Currency distribution (observed) | Currency | Typical entity | | -------- | ------------------------------------------------------- | | HKD | Most HK-incorporated companies | | USD | Some holding companies (e.g. asset-management holdings) | | GBP | UK-incorporated companies registered in HK | | CHF | Swiss-incorporated companies registered in HK | ## Shareholders HK shareholders are returned in V2 `shareholdings[].shareholders` split by entity type: * Natural-person shareholders → `shareholdings[].shareholders.individuals[]` * Corporate shareholders → `shareholdings[].shareholders.corporations[]` Share types observed: `ORDINARY` (most common), with occasional source variant `ORDINARY SHARE`. Around half of HK fixtures have shareholder data; mutual funds, sole proprietorships, guarantee companies, and some registered non-HK companies have no shareholders. ## Representatives / directors CR entities populate V2 `representatives.individuals[]` with the role `Director`. Sole proprietorships surface the sole proprietor on the same array with a null role. ### Identity documents Identity documents are masked in HK responses (consistent with HK Identity Card / Passport privacy convention): | Type | Format | | ------------------ | ---------------------------------- | | Hong Kong ID | Letter + 3 digits + `***` (masked) | | Passport Number | Masked with `****` | | Sole-proprietor ID | Full value (not masked) | ### Nationality * HK residents: `"Hong Kong"` * Non-HK nationals: bilingual format `" "` (e.g. `"英國 UNITED KINGDOM"`, `"中國 CHINA"`) Surfaced on V2 `representatives.individuals[].nationality`. Chinese names alongside Latin names are populated for most HK-resident directors and null for most foreign nationals. Appointment / outgoing dates are populated for sole proprietorship records; an empty / sentinel date in the source means "still active" / "not departed". ## Address HK `address` is returned with the flat `fullAddress` only on Lite Profile: no component breakdown (`city`, `region`, `streetName`, etc. are null on Lite). * `country`: `"Hong Kong"`, `isoCode`: `"HK"` * `fullAddress`: flat string (e.g. `"46/F, FAR EAST FINANCE CENTRE 16 HARCOURT ROAD HONG KONG"`) * `city`, `region`, `postcode`, `streetName`, `buildingName`: null on Lite Mutual Funds have null address; sole proprietorship addresses may be in Chinese only. ## Activity / industry codes Hong Kong uses **HSIC** (Hong Kong Standard Industrial Classification, derived from ISIC Rev 4) at the registry, but activity codes are **not surfaced** for Companies Registry entities: the registry does not expose HSIC via the data interfaces Kyckr connects to. `activities[]` is empty for HK CR companies. For sole proprietorships, a single activity is mapped from the Business Registration industry field with a Chinese-language description and no code. ## Enhanced Profile: async workflow Hong Kong Enhanced Profile is ordered asynchronously, via the POST route only: registry fulfilment runs too long for a held connection, so it is not served by `GET`. **On V2:** place the order with `POST /v2/companies/{kyckrId}/enhanced`, which returns `202` with an `orderId` in the response body, then poll `GET /v2/orders/{orderId}` until `data.status` is `Success` and retrieve the profile from the order result. See the [async order pattern release note](/company-v2/developer-news/2026-08-async-order-pattern) for the full pattern. HK Lite Profile and Search are synchronous and return data immediately. ## Data Availability | Data Point | Available | | ------------------ | ------------------------------- | | Company Name | Yes (English and Chinese) | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Private and public limited only | | Share Capital | Private and public limited only | | Activities | Sole proprietorships only | | Contact Details | No | | UBOs | No | ## Registry documents Companies Registry filings are searchable for HK CR entities (production data shows 94+ distinct filing types across \~20 UAT entities). Document categories include Company Governance & Officers (FND2A, FND2B, FD2 series), Annual Returns & Accounts (FNAR1, FAR1, FNN3), Incorporation & Constitution (FNNC1, FNC1), Registered Office (FR1, FNR1), Share Capital & Charges (FNSC1, FNDB1, FNM series), Winding Up & Dissolution (FW1–FW5, FNDR1), and Non-HK Company specific filings (FNN5–FNN13, FF1–FF5). Legacy form codes (FD2, FAR1, FN3) predate the Companies Ordinance (Cap. 622) effective 2014-03-03. **Not supported for:** sole proprietorships (Business Registration) and mutual funds. ## Additional resources * [Async order pattern (V2)](/company-v2/developer-news/2026-08-async-order-pattern) * [Async order pattern (V1)](/company-v1/developer-news/2026-08-async-order-pattern) * [Normalised values guide](/documentation/useful-information/normalised-values) * [Company V2 API Reference](/company-v2/api-reference/overview) # Ireland (IE) Source: https://developer.kyckr.com/country-guides/ireland Country guide for Irish company data including registry information, identifiers, legal forms, and data availability. ## Overview **CRO** (Companies Registration Office) Official company registry of Ireland The Companies Registration Office (CRO) is the official registry for all companies and business names in Ireland. Basic company information is accessed directly from the CRO API, while enhanced data (directors, shareholders, share capital) is extracted from filed B1C Annual Return documents through automated document processing. ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------------------ | -------- | -------------------------- | | Registration Number | Numeric, variable length | `175525` | No fixed length or padding | | VAT Number | N/A | N/A | Not available from CRO | Irish company registration numbers have no fixed length or leading zeros. They are simply numeric identifiers assigned sequentially by the CRO. ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------------------- | | Search by registration number | Yes | | Search by company name | Yes (contains search) | ## Data Availability ### Companies | Data Point | LTD | DAC | ULC | PLC | CLG | External | | -------------------- | ------- | ------- | ------- | ------- | ------- | -------- | | Registration details | Yes | Yes | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | Yes | Yes | | Directors | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | | Company Secretary | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | | Shareholders | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | Limited | | Share Capital | Yes\* | Yes\* | Yes\* | Yes\* | No | No | | Group Structure | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | No | | Activity Codes | Yes\*\* | Yes\*\* | Yes\*\* | Yes\*\* | Yes\*\* | Yes\*\* | \*Extracted from B1C Annual Return filings \*\*Via separate API (not in enhanced profile response) **LTD** = Private Company Limited by Shares, **DAC** = Designated Activity Company, **ULC** = Private Unlimited Company, **PLC** = Public Limited Company, **CLG** = Company Limited by Guarantee ### Business Names | Data Point | Individual | Body Corporate | | -------------------- | ---------- | -------------- | | Registration details | Yes | Yes | | Address | Yes | Yes | | Owners | Yes\* | Yes\* | | Shareholders | No | No | | Share Capital | No | No | \*Extracted from filed documents ## Legal Forms | Code | Abbreviation | Full Name | Notes | | ---- | ------------ | --------------------------------- | ------------------------------------- | | 1153 | LTD | Private Company Limited by Shares | Most common company type | | 1150 | DAC | Designated Activity Company | Limited by shares, restricted objects | | 1157 | ULC | Private Unlimited Company | Unlimited liability | | 1155 | CLG | Company Limited by Guarantee | Non-profits, charities | | Code | Abbreviation | Full Name | Notes | | ---- | ------------ | ---------------------- | ------------------------- | | 1154 | PLC | Public Limited Company | Publicly traded companies | | Code | Type | Description | Notes | | ---- | -------------- | ------------------------------ | ------------------------------------------ | | 1130 | Individual | Business name - Individual | Sole trader trading under a different name | | 1132 | Body Corporate | Business name - Body Corporate | Company trading under a different name | | Code | Abbreviation | Full Name | Notes | | ---- | ------------ | ----------------------- | --------------------------------- | | 1177 | SE | Societas Europaea | European company form | | 1178 | External | Foreign Registered Body | Foreign company with Irish branch | | Code | Abbreviation | Full Name | Notes | | ---- | ------------ | ----------------------------------------- | ------------------- | | 1175 | ICAV | Irish Collective Asset-management Vehicle | Investment funds | | 1176 | - | Investment Company | Investment entities | ## Status Codes | Status | Description | Normalized Status | | ------------------ | ---------------------------------------- | ----------------- | | Normal | Active company | Active | | In Liquidation | Liquidation proceedings in progress | Distressed | | In Receivership | Receivership proceedings in progress | Distressed | | Strike-Off Listed | Listed for removal from register | Distressed | | Strike-Off Pending | Strike-off pending final dissolution | Distressed | | Dissolved | Company has been dissolved | Inactive | | Examinership | Court protection (similar to Chapter 11) | Distressed | ## Activity Codes Ireland uses **NACE Rev. 2** for classifying business activities. | Field | Description | Example | | ----------- | ----------------------- | ------------------------------- | | `nace_code` | NACE Rev. 2 code format | `62.01` | | `name` | Activity description | Computer programming activities | | `version` | NACE version | `2` | Activity codes are sourced via a separate CRO Open Data API and are **not included** in the main enhanced profile response. The `activities` array will be populated by a separate service. ## Address Format Irish addresses use a line-based structure from the CRO: **Example format:** ```text theme={null} SUITE 6, RINEANNA HOUSE, SHANNON FREE ZONE, CO. CLARE ``` ### Address Components | Component | Maps To | Description | | --------------- | ------------------- | ------------------------------ | | CompanyAddress1 | rawAddressLines\[0] | Primary line (building/street) | | CompanyAddress2 | rawAddressLines\[1] | Secondary line (area/locality) | | CompanyAddress3 | rawAddressLines\[2] | Region/county | | CompanyAddress4 | rawAddressLines\[3] | Additional (often empty) | | Eircode | postcode | Irish postal code | | Country | country | Always "Ireland" | Eircode (Irish postal code) is not always present, particularly for older registrations or rural addresses. ## Implementation Notes **Data Currency**: Director, secretary, and shareholder data is extracted from B1C Annual Return filings through document processing. This data reflects the **last filed annual return**, not real-time changes. Recent appointments, resignations, or share transfers may not be reflected until the next annual return is filed and processed. **Joint Shareholdings**: When shares are jointly owned, shareholder names may appear combined in the source data (e.g., "JOHN DOE & JANE DOE"). These are split into separate entries in the API response. **Foreign Registered Bodies**: Companies with type code 1178 are foreign entities with an Irish branch or presence. The `registrationType` field will be "Foreign Registered Body" and `registrationTypeDetails` will contain the country of origin. ### Representatives | Role | Description | Notes | | ------------------------- | ----------------------- | ------------------------------------ | | Director | Company director | Primary governance role | | Company Secretary | Statutory secretary | Required for all Irish companies | | Registered Business Owner | Business name owner | For business name registrations only | | Ultimate Parent | Ultimate parent company | From group structure data | | Immediate Parent | Direct parent company | From group structure data | ### Capital Types Share capital data is grouped by share class (e.g., "ORDINARY", "A ORDINARY", "PREFERENCE") with each class including: * Total nominal value * Currency (typically EUR) * Shareholdings with percentage ownership **CLG companies** (Companies Limited by Guarantee) and **External companies** (Foreign Registered Bodies) do not have share capital data, as CLGs have members rather than shareholders, and external companies' capital is registered in their home jurisdiction. # Italy (IT) Source: https://developer.kyckr.com/country-guides/italy Country guide for Italy company data including registry information, identifiers (REA, VAT, Codice Fiscale), search capabilities, and implementation notes. ## Overview **REA** (Repertorio Economico Amministrativo) Provincial trade registers maintained by Italian Chambers of Commerce (CCIA) Italian company data is sourced from the Repertorio Economico Amministrativo (REA), the provincial business register. Each Italian province has its own Chamber of Commerce (Camera di Commercio - CCIA) that maintains a register of companies within its jurisdiction. The **REA number** (province code plus registration number) is the unique primary identifier for API requests; the Codice Fiscale (national tax code) is not unique per company and must not be used for profile or filing orders. ## Company Identifiers | Identifier | Type Code | Format | Example | Notes | | --------------------------- | ----------- | --------------------- | --------------- | ------------------------------------------------------------------------------------------------------------ | | REA (Trade Register Number) | IT\_REA\_CD | 2 letters + digits | `NA0091712` | Primary identifier. Province code (e.g. NA = Naples) followed by unique registration number within that CCIA | | VAT Number | IT\_VAT\_CD | IT + 11 digits | `IT12345678912` | European VAT identifier | | Codice Fiscale (Tax Code) | IT\_TAX\_CD | 11 digits (companies) | `12345678901` | National tax identification; not unique per company | **Use REA for all profile and filing requests.** The Codice Fiscale is not unique and may be shared by related companies. Lite and Enhanced profile orders using Codice Fiscale may fail; filing search is not supported with Codice Fiscale. Always use the REA identifier from the search response. ## Search Capabilities | Search Method | Supported | Notes | | ------------------------ | --------- | ----------------------------------------------------------------------- | | Search by company name | Yes | | | Search by REA number | Yes | Use the full REA (e.g. `MI123456`) | | Search by Codice Fiscale | Yes | May return multiple entities; use REA from results for subsequent calls | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | Yes | | UBOs | No | ## Implementation Notes **Use search response data for API calls.** Use the company identifier (REA) from the search response for all Lite Profile, Enhanced Profile, and Filings Search requests. Include the registration authority code (province code) as the `RegAuth` query parameter where supported; it is optional for Italy but recommended. ### Identifier handling * The primary company identifier in API responses is the **REA number** (e.g. `MI123456`). * For secondary identifiers (Codice Fiscale, VAT), use the `otherIdentifiers` array in Lite and Enhanced profile responses, with type codes `IT_TAX_CD` and `IT_VAT_CD`. * Systems that store Italian company identifiers should store and use REA. Do not rely on Codice Fiscale for lookups or ordering. ### Province code reference REA numbers begin with a two-letter province code. Each province has its own Chamber of Commerce (CCIA). Below is the reference for province codes used in the REA format. | Province | Code | Province | Code | Province | Code | | --------------------- | ---- | ------------- | ---- | ------------- | ---- | | Agrigento | AG | Alessandria | AL | Ancona | AN | | Aosta | AO | Arezzo | AR | Ascoli Piceno | AP | | Asti | AT | Avellino | AV | Bari | BA | | Barletta-Andria-Trani | BT | Belluno | BL | Benevento | BN | | Bergamo | BG | Biella | BI | Bologna | BO | | Bolzano | BZ | Brescia | BS | Brindisi | BR | | Cagliari | CA | Caltanissetta | CL | Campobasso | CB | | Caserta | CE | Catania | CT | Catanzaro | CZ | | Chieti | CH | Como | CO | Cosenza | CS | | Cremona | CR | Crotone | KR | Cuneo | CN | | Enna | EN | Fermo | FM | Ferrara | FE | | Firenze | FI | Foggia | FG | Forlì-Cesena | FC | | Frosinone | FR | Genova | GE | Gorizia | GO | | Grosseto | GR | Imperia | IM | Isernia | IS | | Province | Code | Province | Code | Province | Code | | --------------- | ---- | --------------- | ---- | --------------- | ---- | | La Spezia | SP | L'Aquila | AQ | Latina | LT | | Lecce | LE | Lecco | LC | Livorno | LI | | Lodi | LO | Lucca | LU | Macerata | MC | | Mantova | MN | Massa-Carrara | MS | Matera | MT | | Messina | ME | Milano | MI | Modena | MO | | Monza e Brianza | MB | Napoli | NA | Novara | NO | | Nuoro | NU | Oristano | OR | Padova | PD | | Palermo | PA | Parma | PR | Pavia | PV | | Perugia | PG | Pesaro e Urbino | PU | Pescara | PE | | Piacenza | PC | Pisa | PI | Pistoia | PT | | Pordenone | PN | Potenza | PZ | Prato | PO | | Ragusa | RG | Ravenna | RA | Reggio Calabria | RC | | Reggio Emilia | RE | Rieti | RI | Rimini | RN | | Province | Code | Province | Code | Province | Code | | -------- | ---- | -------------------- | ---- | -------- | ---- | | Roma | RM | Rovigo | RO | Salerno | SA | | Sassari | SS | Savona | SV | Siena | SI | | Siracusa | SR | Sondrio | SO | Taranto | TA | | Teramo | TE | Terni | TR | Torino | TO | | Trapani | TP | Trento | TN | Treviso | TV | | Trieste | TS | Udine | UD | Varese | VA | | Venezia | VE | Verbano-Cusio-Ossola | VB | Vercelli | VC | | Verona | VR | Vibo Valentia | VV | Vicenza | VI | | Viterbo | VT | | | | | # Japan (JP) Source: https://developer.kyckr.com/country-guides/japan Country guide for Japan company data including registry information, identifiers, legal forms, bilingual name handling, and data availability. ## Overview **National Tax Agency (NTA)** corporate-number system Backed by company registrations held by the Ministry of Justice's Legal Affairs Bureaus (法務局) Japan corporate data is sourced from the National Tax Agency's corporate-number system. Search, Lite Profile, and Enhanced Profile are all supported across V1 and V2. Data quality varies by company size: listed companies expose their top 10 shareholders, and small private companies generally have no shareholder or director data. **Data quality improvements in progress.** JP responses are being refined for richer structured data and improved standard-value mappings; release notes will follow when updates ship. ## Company identifiers | Identifier | Format | Example | Notes | | ---------------- | ---------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | Corporate number | 13-digit numeric | `5010001060426` | Issued by NTA; globally unique. Consumption tax (Japan's VAT-equivalent) uses the same number — there is no separate VAT identifier. | In V2, the corporate number is the `companyNumber` and is also the registry-encoded portion of the V2 `id`. In V1, it appears as `codeField`. ## Legal form JP source data does not include a discrete legal-form field; `legalForm.normalized` is inferred from the Japanese-script company-name suffix, and `legalForm.original` carries the literal Japanese suffix where present. | Japanese suffix | `legalForm.normalized` | English equivalent | Notes | | -------------------- | ------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `株式会社` | `Private Limited Company` | Kabushiki Kaisha (K.K.) | The default Japanese corporate form; literally "stock company" by name but in practice \~99% are private. Can appear at the start (`株式会社リクルートホールディングス`) or end (`ソニーグループ株式会社`) of the name. Public / listed status is a separate axis determined by stock-exchange listing, not by the form itself. | | `合同会社` | `Private Limited Company` | Godo Kaisha (G.K.) | Japanese LLC, introduced 2006. Often used by inbound subsidiaries (e.g. Apple Japan, Google Japan). | | `有限会社` | `Private Limited Company` | Yugen Kaisha (Y.K.) | Legacy limited company. New registrations disallowed since 2006 but many existing entities remain. | | (no matching suffix) | `Other` | — | Fallback for special-purpose or imported entities. `legalForm.normalized` is never null — `Other` is used when no specific value fits, and the raw suffix remains in `legalForm.original`. | Despite 株式会社 literally translating as "stock company", it maps to `Private Limited Company` rather than `Public Limited Company`. Japan's statutory regime treats `株式会社` as a unified umbrella corporate form, with listing being a separate state — unlike China where joint-stock (`股份有限公司`) is statutorily distinct from LLC (`有限责任公司`) and only the former can be publicly traded. ## Status | Source value (Japanese) | `legalStatus.original` | `legalStatus.normalized` | | ------------------------------ | ---------------------- | ------------------------ | | `営業中` (eigyō-chū, "operating") | `Active` | `Active` | Other status values are uncommon in the observable JP sample. ## Activity / industry codes JP activities are returned as a comma-joined string of numeric industry codes (e.g. `"110,111,112,115,...,315"`) on `activities[].description`. No standardised classification scheme (NACE / NAICS) is provided for JP — `activities[].code`, `activities[].classificationScheme`, and `activities[].type` are typically null. ## Address JP `address` is returned in the standard V2 structured shape on both Lite Profile and Enhanced Profile (most other Asia-Pacific jurisdictions return only the flat `fullAddress` on Lite — JP is the exception). | V2 field | Populated | Notes | | --------------------------------- | --------------- | --------------------------------------------------- | | `fullAddress` | ✓ | E.g. `"1-9-2 Marunouchi, Chiyoda-ku, Tokyo"` | | `region` | ✓ | Prefecture, with the trailing ` Prefecture` removed | | `city` | ✓ where present | Segment ending `-shi` / containing `City` | | `municipality` | ✓ where present | Segment ending `-ku` | | `streetName`, `streetNumber` | ✓ where present | Parsed from the street segment | | `buildingName` | ✓ where present | Any building segment preceding the street segment | | `country` | `"Japan"` | | | `isoCode` | `"JP"` | | | `postcode`, `secondaryPostalCode` | — | Not surfaced for JP | Typical Latin form: `"1-9-2 Marunouchi, Chiyoda-ku, Tokyo"`. Typical Japanese form: `"東京都千代田区丸の内１丁目９番２号"`. ## Company names | V2 field | V1 field | Content | | -------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `companyName` | `nameField` | **Japanese-script** registered name (e.g. `"株式会社リクルートホールディングス"`). For JP entities the source treats the Japanese name as primary, so it occupies `companyName`. | | `englishName` | `englishNameField` | Latin-script English name (e.g. `"Recruit Holdings Co., Ltd."`) when distinct from `companyName`. | | `aliases[]` (type: `Kana`) | `aliasesField` | Phonetic Kana variant of the name where the source surfaces one. | For JP entities you should treat `englishName` (not `companyName`) as the Latin-script form for display in English-language contexts. ## Capital JP entities populate the standard V2 `capital` / `totalCapital` shape: * Currency: typically `Yen` * `totalCapital.type`: typically `Registered` — the registry reports registered-capital amount (rather than authorized or paid-in). See [Normalised values](/documentation/useful-information/normalised-values#totalcapitaltype). ## Representatives / directors JP entities expose representatives on V2 `representatives.individuals[]` with the Latin and Japanese name pair populated. Roles are free-text labels (e.g. `"President and CEO"`, `"Director"`). JP companies typically surface a single representative even for very large listed entities. ## Shareholders V2 `shareholdings[]` is populated for listed companies (and many mid-caps) but capped at the **top 10 shareholders**. For listed entities, the per-shareholder percentages typically sum to 40–60% rather than 100%. Shareholder names occasionally carry Japanese-language parentheticals such as `"(Permanent Agent: …)"` or `"(Standing Proxy: …)"` on custody-bank and foreign-institutional holders. These are returned as-is. ## Data Availability | Data Point | Available | | ------------------ | --------------------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Limited | | Status | Yes | | Representatives | Yes | | Shareholders | Listed companies only | | Share Capital | Yes | | Activities | Yes | | Contact Details | No | | UBOs | No | ## Additional resources * [Normalised values guide](/documentation/useful-information/normalised-values) * [Company V2 API Reference](/company-v2/api-reference/overview) # Jersey (JE) Source: https://developer.kyckr.com/country-guides/jersey Country guide for Jersey company data including registry information and data availability. ## Overview **Jersey Financial Service Commission (JFSC)** Official company registry of Jersey ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | No | | Shareholders | No | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Latvia (LV) Source: https://developer.kyckr.com/country-guides/latvia Country guide for Latvian company data including registry information, identifiers, legal forms, and data availability. ## Overview **UR** (Uzņēmumu reģistrs) Register of Enterprises of the Republic of Latvia Latvia's Register of Enterprises (Uzņēmumu reģistrs) is the official registry for all legal entities in Latvia. It is maintained by the Ministry of Justice and provides comprehensive company data including registration details, shareholders, and management information. ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------------------------------ | -------------------------- | --------------- | ---------------------------- | | Registration Number (Reģistrācijas numurs) | 11-digit numeric | `40103548442` | Prefix indicates entity type | | VAT Number (PVN numurs) | `LV` + registration number | `LV40103548442` | For VAT-registered companies | ### Registration Number Patterns The first two digits indicate the entity type: * **40** - Commercial companies (SIA, AS) * **50** - Non-profit organisations * **90** - State and municipal institutions ### VAT Number Details VAT data includes: * VAT number * Active status (current VAT status) * Registration date ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | SIA/AS | IK | Partnerships | Non-Profits | | -------------------- | ------ | --- | ------------ | ----------- | | Registration details | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | | Capital | Yes | No | No | No | | Shareholders | Yes | No | No | No | | Management | Yes | Yes | Yes | Yes | | Activities (NACE) | Yes | Yes | Yes | Yes | **SIA** = Limited Liability Company, **AS** = Public Limited Company, **IK** = Sole Trader ## Legal Forms | Code | Latvian | English | Notes | | ---- | ---------------------------------- | ------------------------- | ---------------------------- | | SIA | Sabiedrība ar ierobežotu atbildību | Limited Liability Company | Min capital EUR 2,800 | | AS | Akciju sabiedrība | Public Limited Company | Min capital EUR 35,000 | | PS | Pilnsabiedrība | General Partnership | Unlimited liability | | KS | Komandītsabiedrība | Limited Partnership | At least one limited partner | | Code | Latvian | English | Notes | | ---- | ------------------------ | ---------------------- | ----------------------- | | IK | Individuālais komersants | Sole Trader | Natural person business | | IND | Individuālais uzņēmums | Individual Undertaking | Legacy form | | Z/S | Zemnieku saimniecība | Farm | Agricultural business | | Code | Latvian | English | Notes | | ---- | ---------------------- | ---------------------- | ------------------ | | BDR | Biedrība | Association | Membership-based | | NOD | Nodibinājums | Foundation | Asset-based entity | | REL | Reliģiskā organizācija | Religious Organisation | Religious entities | | Code | Latvian | English | Notes | | ---- | ------------------------------ | ---------------------------- | ---------------------- | | SE | Eiropas komercsabiedrība | European Company | EU company form | | SCE | Eiropas kooperatīvā sabiedrība | European Cooperative Society | EU cooperative form | | FIL | Ārvalsts komersanta filiāle | Branch of Foreign Company | Foreign company branch | ## Status Codes | Code | Latvian | English | Normalized Status | | ---------------------------- | ------------------------ | -------------- | ----------------- | | REGISTERED | Reģistrēts | Registered | Active | | REGISTERED (IN\_LIQUIDATION) | Reģistrēts (likvidācijā) | In Liquidation | Distressed | | REMOVED | Izslēgts | Removed | Inactive | | ANNULLED | Anulēts | Annulled | Inactive | ## Activity Codes Latvia uses **NACE Rev. 2** (Saimniecisko darbību statistiskā klasifikācija) for classifying business activities. | Field | Description | Example | | ----------- | ------------------------------- | ------------------------------- | | `nace_code` | NACE Rev. 2 code format (XX.XX) | `62.01` | | `name` | Activity description in English | Computer programming activities | | `version` | NACE version | `2` | Older companies may have activity codes from NACE Rev. 1 or 1.1. These are mapped to NACE Rev. 2 where possible. ## Address Format Latvian addresses use a component-based structure. Example formats: **Standard format:** ```text theme={null} Brīvības iela 21, Rīga, LV-1010, Latvia ``` **With apartment number:** ```text theme={null} Brīvības iela 21 - 20, Rīga, LV-1010, Latvia ``` ### Address Components | Component | Maps To | Example | | ---------------------- | ------------------------ | --------------- | | Street (iela/bulvāris) | Street Name | Brīvības iela | | House number | Street Number | 21 | | Flat number | Street Number (appended) | 21 - 20 | | City (pilsēta) | City | Rīga | | Village (ciems) | City (fallback) | Mārupe | | Parish (pagasts) | Municipality | Mārupes pagasts | | Postal code | Postcode | LV-1010 | ## Implementation Notes **Currency history**: Latvia adopted the Euro (EUR) on January 1, 2014. Historical capital records may show amounts in Latvian Lats (LVL). The exchange rate was fixed at 1 EUR = 0.702804 LVL. **Founders vs Shareholders**: In Latvian company law, "founders" (dibinātāji) become shareholders (dalībnieki) upon company registration. The data returned represents current shareholdings, not founding roles. The "Founded.from/to" dates in the source data track share acquisition and disposal, not governance appointments. **Shareholder data availability**: Shareholder information is only available for commercial companies (SIA and AS). Other entity types such as sole traders (IK), partnerships, and non-profits do not have shareholder data in the registry. ### Capital Types | Code | Description | Notes | | ---- | ----------------------------------------------- | ------------------------- | | APM | Paid capital (Apmaksātais pamatkapitāls) | Most commonly returned | | REG | Registered capital (Reģistrētais pamatkapitāls) | Authorised capital amount | ### Representatives Latvian companies have officials (Valde members) who serve as the management board: | Role | Latvian | Description | | ----------------- | --------------------- | ------------------------------------ | | Board Member | Valdes loceklis | Management board member | | Board Chair | Valdes priekšsēdētājs | Chairman of the board | | Supervisory Board | Padomes loceklis | Oversight function (AS companies) | | Procurist | Prokurists | Special commercial power of attorney | # Luxembourg (LU) Source: https://developer.kyckr.com/country-guides/luxembourg Country guide for Luxembourg company data including registry information, identifiers, legal forms, and data availability. ## Overview **RCS** (Registre de Commerce et des Societes) Official company registry of Luxembourg The RCS (Registre de Commerce et des Societes) is the official business register of Luxembourg, accessed via the LBR (Luxembourg Business Registers) XML API. Unlike many jurisdictions that rely on PDF document parsing, Luxembourg provides **fully fielded structured XML data** directly from LBR, with detailed shareholding information, court ruling data, and granular status codes. Lite Profile and Search are returned synchronously. Enhanced Profile fulfilment is covered under [Enhanced Profile: async workflow](#enhanced-profile-async-workflow) below. ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ---------------------- | --------- | --------------------------------- | | Registration Number | Letter prefix + digits | `B136303` | Unique identifier assigned by RCS | | VAT Number | N/A | N/A | Not available from RCS | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Companies | Sole Traders | Partnerships | Funds | Associations | Foreign Branches | | -------------------- | --------- | ------------ | ------------ | ----- | ------------ | ---------------- | | Registration details | Yes | Yes | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | Yes | Yes | | Capital/Shares | Yes | No | Some | No | No | No | | Representatives | Yes | Limited | Yes | Yes | Yes | Yes | | NACE Codes | \~28% | \~28% | \~28% | \~28% | \~28% | \~28% | | Foreign Details | N/A | N/A | N/A | N/A | N/A | Yes | ## Legal Forms | Abbreviation | French | English | Notes | | ------------ | --------------------------------- | ------------------------------ | ------------------------------------- | | SA | Societe anonyme | Public Limited Company | Most common for larger companies | | SARL | Societe a responsabilite limitee | Private Limited Company | Most common company type | | SAS | Societe par actions simplifiee | Simplified Joint Stock Company | Flexible governance | | SE | Societe europeenne | European Company | EU-wide company form | | SCA | Societe en commandite par actions | Partnership Limited by Shares | Limited and general partners | | SCS | Societe en commandite simple | Limited Partnership | At least one unlimited partner | | SNC | Societe en nom collectif | General Partnership | All partners have unlimited liability | | Type | French | English | Notes | | -------------------- | ------------------------------ | -------------------- | ------------------------- | | Civil Partnership | Societe civile | Civil Partnership | Non-commercial purposes | | Cooperative | Societe cooperative | Cooperative Society | Member-owned organization | | European Cooperative | Societe cooperative europeenne | European Cooperative | EU-wide cooperative form | | Abbreviation | French | English | Notes | | ------------ | ------------------------------------------- | ---------------------------------------- | ----------------------- | | SICAV | Societe d'investissement a capital variable | Investment Company with Variable Capital | Open-ended fund | | FCP | Fonds commun de placement | Common Investment Fund | Contractual fund | | FIAR | Fonds d'investissement alternatif reserve | Reserved Alternative Investment Fund | For qualified investors | | Abbreviation | French | English | Notes | | ------------ | ----------------------------- | ---------------------- | --------------------------- | | ASBL | Association sans but lucratif | Non-profit Association | Most common non-profit form | | - | Fondation | Foundation | Charitable foundation | | - | Mutuelle | Mutual Society | Mutual benefit organization | | Type | French | English | Notes | | ---------------------- | ---------------------------------------------------------------- | ----------------------------------- | ------------------------------- | | Foreign Company Branch | Succursale d'une personne morale de droit etranger | Branch of Foreign Legal Person | Most common foreign presence | | Foreign Trader Branch | Succursale d'un commercant personne physique etabli a l'etranger | Branch of Foreign Individual Trader | Foreign sole trader | | Foreign EEIG Branch | Succursale d'un GEIE etranger | Branch of Foreign EEIG | Foreign economic interest group | | Type | French | English | Notes | | ----------------- | ---------------------------- | ----------------- | ---------------------------------- | | Individual Trader | Commercant personne physique | Individual Trader | Natural person conducting business | ## Status Codes | Status | Description | Normalized Status | | ------------------------------ | ------------------------------ | ----------------- | | (none) | Active entity | Active | | en liquidation volontaire | Voluntary liquidation | Distressed | | en liquidation judiciaire | Judicial liquidation | Distressed | | en faillite | In bankruptcy | Distressed | | radiee | Struck off | Inactive | | avec administrateur provisoire | With provisional administrator | Distressed | | en sursis de paiement | Payment suspension | Distressed | Luxembourg has 20 detailed observation codes for non-active statuses. The `statusDetailsBeta` field provides granular status information including court ruling dates, court names, and specific closure reasons. ## Activity Codes Luxembourg uses **NACE Rev. 2** for classifying business activities. | Field | Description | Example | | ------------- | -------------------- | -------- | | `code` | NACE Rev. 2 code | `96.021` | | `description` | Activity description | Coiffure | | `type` | Classification type | NACE | Only approximately 28% of Luxembourg entities have NACE codes in the registry data. The company's stated purpose (objet social) is available in `activityDeclarations`. ## Address Format Luxembourg addresses use a component-based structure: **Example format:** ```text theme={null} 10 rue du Test, 1234 Luxembourg ``` ### Address Components | Component | Maps To | Description | | -------------- | ------------------------- | --------------------------------------- | | BuildingNumber | streetNumber | Street number | | BuildingName | buildingName | Building name (if applicable) | | StreetName | streetName | Street name | | Floor | (included in fullAddress) | Floor information | | PostalCode | postcode | 4-digit postal code | | Locality | city | City/town name | | Country | country | Country name | | CountryCode | isoCode | Converted from 3-letter to 2-letter ISO | Source data uses 3-letter ISO country codes (e.g., LUX, FRA, BEL) which are converted to 2-letter codes (LU, FR, BE) in the API response. ## Implementation Notes **Fully Structured Data**: Unlike jurisdictions that rely on PDF parsing (with 1-6 hour processing delays), Luxembourg provides fully fielded XML data directly from LBR, with structured shareholding information, detailed court ruling data, and comprehensive status tracking. ### Representatives Luxembourg classifies representatives into multiple categories: | Role | French | Description | | ------------------------ | -------------------------------- | ------------------------------ | | Director/Manager | Administrateur/Gerant | Directors and managers | | Board Member | Membre | Board members | | Daily Management | Delegue a la gestion journaliere | Daily management delegates | | Permanent Representative | Representant permanent | Branch representatives | | Partner | Associe | Partners (in partnerships) | | Legal Agent | Agent legal | Liquidators, bankruptcy agents | | Management Company | Societe de gestion | Fund management company | ### Capital and Shareholding Data **Structured Shareholding**: Luxembourg provides fully fielded shareholding data including shareholder names, share counts, and share types - a significant advantage over jurisdictions where this data must be parsed from documents. Share classes commonly include: * `Parts de categorie A` / `Parts de categorie B` - Class A/B shares * `Parts sociales` - Social shares * `Actions` - Regular shares Capital type is indicated as either "Fixed" (Fixe) or "Variable". ### Foreign Entities For foreign-registered entities with a Luxembourg presence: | Field | Value | | ---------------------------- | ------------------------------- | | `registrationType` | "Foreign Registered Body" | | `registrationTypeDetails` | Source jurisdiction information | | `otherIdentifiers[].type` | "LU\_FOREIGN\_REG\_CD" | | `otherIdentifiers[].isoCode` | Source country code | | `otherIdentifiers[].value` | Foreign registration number | ## Enhanced Profile: async workflow Luxembourg Enhanced Profile is fulfilled synchronously on `GET` when the registry responds in time. A slower order is handled by the async order pattern: the request returns `202` with an `orderId` instead, and the profile is retrieved by polling `GET /v2/orders/{orderId}`. On V2, Enhanced Profile can also be ordered asynchronously from the start with `POST /v2/companies/{kyckrId}/enhanced`, polled the same way, with no held connection. See the async order pattern release notes for [V2](/company-v2/developer-news/2026-08-async-order-pattern) and [V1](/company-v1/developer-news/2026-08-async-order-pattern) for integration guidance. Lite Profile and Search remain synchronous and return data immediately. # Malaysia (MY) Source: https://developer.kyckr.com/country-guides/malaysia Country guide for Malaysia company data including registry information and data availability. ## Overview **Companies Commission of Malaysia** Official company registry of Malaysia ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Netherlands (NL) Source: https://developer.kyckr.com/country-guides/netherlands Country guide for Netherlands company data including registry information and data availability. ## Overview **Kamer van Koophandel** Official company registry of Netherlands ## Company Identifiers | Identifier | Format | Example | Notes | | ---------- | --------------- | ---------- | -------------------------- | | KVK-nummer | 8 digit numeral | `55114628` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # New Zealand (NZ) Source: https://developer.kyckr.com/country-guides/new-zealand Country guide for New Zealand company data including registry information and data availability. ## Overview **New Zealand Companies Register** Official company registry of New Zealand ## Company Identifiers | Identifier | Format | Example | Notes | | ---------------------- | ------------ | ------- | -------------------------- | | Source Registry Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Norway (NO) Source: https://developer.kyckr.com/country-guides/norway Country guide for Norway company data including registry information and data availability. ## Overview **Brønnøysund Register Centre (BRC)** Official company registry of Norway ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | --------------- | -------------- | -------------------------- | | Organisasjonsnummer | 9 digit numeral | `977538963` | Primary company identifier | | VAT Number | NO + digits | `123456789MVA` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Singapore (SG) Source: https://developer.kyckr.com/country-guides/singapore Country guide for Singapore company data including registry information and data availability. ## Overview **Accounting and Corporate Regulatory Authority (ACRA)** Official company registry of Singapore ## Company Identifiers | Identifier | Format | Example | Notes | | -------------------------- | ------------ | ------------ | -------------------------- | | UEN (Unique Entity Number) | Aplhanumeric | `200801391M` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Spain (ES) Source: https://developer.kyckr.com/country-guides/spain Country guide for Spain company data including registry information and data availability. ## Overview **Registradores de España, Registro Mercantil Central, BORME** Official company registry of Spain ## Company Identifiers | Identifier | Format | Example | Notes | | ---------------------------------- | ------------------------------------------------------------ | ------------- | -------------------------- | | NIF (Fiscal Identification Number) | One letter followed by 8 numerals (9-character alphanumeric) | `B86007945` | Primary company identifier | | VAT Number | ES + digits | `ESX12345678` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | ------------------------------------------------ | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes - Single Shareholders only (Where available) | | Share Capital | Yes | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Sweden (SE) Source: https://developer.kyckr.com/country-guides/sweden Country guide for Sweden company data including registry information and data availability. ## Overview **Bolagsverket** Official company registry of Sweden ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ---------------- | ---------------- | -------------------------- | | Organisationsnummer | 10 digit numeral | `556849-5484` | Primary company identifier | | VAT Number | SE + digits | `SE123456789123` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | Yes | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # United Kingdom (GB) Source: https://developer.kyckr.com/country-guides/united-kingdom Country guide for United Kingdom company data including registry information and data availability. ## Overview **Companies House** Official company registry of United Kingdom ## Company Identifiers | Identifier | Format | Example | Notes | | ---------- | ---------------------- | ---------- | -------------------------- | | CRN Number | Numeric & Alphanumeric | `06388542` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | Yes | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Perform a KYB Check Source: https://developer.kyckr.com/documentation/features/perform-a-kyb-check-v2 Retrieve a company's full profile, including company information, representatives, and shareholders, sourced live from the official company register. A KYB (Know Your Business) check gives you a verified, structured view of a company's legal identity, ownership structure, and key personnel. Kyckr retrieves this data live from the official company register at the point of request, ensuring you are always working with current information rather than a cached snapshot. This article covers how to retrieve an Enhanced Profile, what data it contains, and how to work with the response. *** ## When to use an Enhanced Profile Retrieve a full list of company officials and directors, including their functions, dates of birth, and addresses, to support deeper due diligence. Access shareholder data, including share counts and percentages, to understand who owns and controls a company. Includes all Lite Profile data (company name, registration number, legal status, and registered address), with expanded details where available from the registry. Combine all registry-sourced data (registration details, capital structure, officers, and shareholders) into a single profile for comprehensive onboarding checks. *** ## What the Enhanced Profile Contains The Enhanced Profile is Kyckr's primary KYB data product. It extends the [Lite Profile](/documentation/features/verify-basic-details-v2) with structured ownership and representative data sourced directly from the company register. | Data category | Description | | -------------------------- | -------------------------------------------------------------------------------------------- | | Company information | Legal name, registration number, status, addresses, legal form, and key dates | | Representatives | Directors and other officers, including role, date of birth, and address | | Shareholders | Individual and corporate shareholders with share count, percentage, and identity information | | Ultimate Beneficial Owners | UBO data where filed in structured form at the register | Data availability varies by jurisdiction. Not all company registers file shareholder, representative, or UBO information in structured, machine-readable form. Where this information is unavailable, the relevant fields will be absent or empty in the response. *** ## How It Works Retrieving an Enhanced Profile is a two-step process: Use the [Company Search](/api-reference/companies/search-for-companies) endpoint to locate the company and confirm it exists in the registry. The search response returns an `id` field: a unique identifier for that company in Kyckr's network. Pass the `id` from the search response as the resource identifier in the Enhanced Profile request. Kyckr retrieves the current data from the registry and returns it in the response. ### Example using a New Zealand company ```bash theme={null} curl --location 'https://api.kyckr.com/v2/companies/NZ|OTQyOTAzMjk4MjU3Mg/enhanced' \ --header 'Authorization: {{apiKey}}' ``` *** ## Asynchronous fulfilment For most jurisdictions, `GET /v2/companies/{kyckrId}/enhanced` returns the profile synchronously. Where upstream fulfilment takes too long, the response times out without delivery. Two patterns retrieve the profile without waiting on that timeout: Returns a `202` with `orderId` nested under `data`, no server-side connection hold. Poll `GET /v2/orders/{orderId}` until `data.status` is `Success`, then retrieve the profile from the order result. `GET /enhanced` holds the connection open while waiting; returns `200` with the profile if ready, or `202` with `orderId` nested under `data` if not. Poll `GET /v2/orders/{orderId}` the same way. See the [async order pattern release note](/company-v2/developer-news/2026-08-async-order-pattern) for jurisdiction scope and full integration guidance. *** ## Optional Parameters You can include a `customerreference` parameter to attach your own reference to a transaction. This is useful for: * Tracking orders against internal records, such as a case ID or onboarding workflow reference. * Reconciling API transactions in your billing or audit logs. * Identifying requests when reviewing order history via the `/orders` endpoint. *** ## Understanding the Response The response is structured around four main data blocks: company information, representatives, shareholders (via the `capital` array), and ultimate beneficial owners. ### Company information Core identity and registration details are returned at the top level of the `data` object. Key fields include: | Field | Description | | --------------------------------------- | ------------------------------------------------------------------------- | | `companyName` | Legal name of the company as filed at the register | | `englishName` | English-language name, where provided by the register | | `aliases` | Alternative or trading names | | `previousNames` | Former legal names with applicable date ranges | | `identifiers.primaryRegistrationNumber` | Primary company registration number | | `registrationAuthority` | Name of the authority where the company is registered | | `status.normalized` | Company status mapped to a controlled value (e.g. `Active`, `Dissolved`) | | `legalForm.normalized` | Legal entity type (e.g. `Private Limited Company`) | | `addresses` | Array of addresses, each typed (e.g. `Registered Address`, `Head Office`) | | `foundationDate` | Date the company was founded | | `registrationDate` | Date the company was registered | | `incorporationDate` | Date the company was incorporated | | `dissolutionDate` | Date of dissolution, where applicable | | `activities` | Industry classifications (NACE, SIC, NAICS) | Date fields follow a consistent structure throughout the response, providing both the original value as recorded at the register and a normalized ISO 8601 date: ```json theme={null} "registrationDate": { "original": "01 November 2018", "normalized": "2018-11-01" } ``` Company status similarly provides both the raw value from the register and a normalized equivalent: ```json theme={null} "status": { "original": "Active - Registered", "normalized": "Active" } ``` *** ### Representatives Representatives are the filed officers of the company: directors, senior management, legal representatives, and similar roles. They are returned in the `representatives` object, which contains two arrays: `individuals` for natural persons and `corporations` for corporate entities. #### Individual representative ```json theme={null} "representatives": { "individuals": [ { "type": "Person", "name": "SMITH, Jane", "address": { "fullAddress": "10 Example Street, Wellington, 6011, NZ", "postcode": "6011", "country": "NZ" }, "birthdate": { "original": "15 March 1975", "normalized": "1975-03-15" }, "role": { "original": "Director", "normalized": "Director" }, "startDate": { "original": "01 January 2020", "normalized": "2020-01-01" }, "isActive": true } ] } ``` #### Corporate representative Where a company (rather than an individual) holds a representative role, that entity appears in `representatives.corporations`: ```json theme={null} "representatives": { "corporations": [ { "type": "Corporation", "name": "PARENT HOLDINGS LIMITED", "registrationNumber": "987654321", "registrationAuthority": "Companies House, United Kingdom", "role": { "original": "Corporate Director", "normalized": "Director" }, "isActive": true } ] } ``` #### Key representative fields | Field | Description | | ----------------------- | ---------------------------------------------------------------------- | | `type` | Entity type: `Person`, `Corporation`, or `Other` | | `name` | Name of the representative | | `role.original` | Role as described at the source register | | `role.normalized` | Role mapped to a controlled dictionary value | | `startDate` / `endDate` | Appointment and resignation dates | | `isActive` | Whether the representative is currently in post | | `birthdate` | Date of birth (individuals only, where filed) | | `address` | Address of the representative | | `powers` | Descriptions of the representative's powers, as stated at the register | | `directorships` | Other directorships held (UK only, see below) | #### Directorship data (UK only) For UK companies, passing the `showDirectorships=true` query parameter enriches each representative with a `directorships` array, listing other companies where the individual or corporation holds a position. ```bash theme={null} curl --location 'https://api.kyckr.com/v2/companies/{id}/enhanced?showDirectorships=true' \ --header 'Authorization: {{apiKey}}' ``` Each directorship entry contains the company number, company name, role, appointment dates, and whether the position is currently active. *** ### Shareholders Where the company register files shareholder information in structured form, the `capital` array contains one or more share class blocks. Each block describes a class of shares and its associated shareholdings. Within each shareholding, shareholders appear in either `shareholders.individuals` (natural persons) or `shareholders.corporations` (corporate entities), with their respective percentage of that share class. ```json theme={null} "capital": [ { "quantity": 100.0, "shareholdings": [ { "percentage": "99.00", "shareholders": { "individuals": [ { "type": "Person", "name": "KIELER, Mette", "address": { "fullAddress": "1 Cornford Street, Karori, Wellington, 6012, NZ", "postcode": "6012", "country": "NZ" } } ] } }, { "percentage": "1.00", "shareholders": { "individuals": [ { "type": "Person", "name": "JOYCE, Darryl", "address": { "fullAddress": "1 Cornford Street, Karori, Wellington, 6012, NZ", "postcode": "6012", "country": "NZ" } } ] } } ] } ] ``` In this example, two individuals hold shareholdings of 99% and 1% respectively within a single share class. #### Percentage ranges Some registers express shareholdings as a range rather than a precise figure. When this is the case, `percentageIsRange` is `true` and the `percentage` field is `null`. Use `percentageRange`, `percentageLowerLimit`, and `percentageUpperLimit` instead. ```json theme={null} { "percentageIsRange": true, "percentageRange": "25-50%", "percentageLowerLimit": "25", "percentageUpperLimit": "50", "percentage": null } ``` #### Key shareholding fields | Field | Description | | ------------------- | -------------------------------------------------------------------------------------------------------- | | `percentage` | Percentage of the share class held. Null when expressed as a range | | `percentageIsRange` | `true` when the register provides a range rather than a precise value | | `count` | Number of shares held in this class, where available | | `totalNominalValue` | Total nominal value of shares in this shareholding | | `beneficiallyHeld` | Indicates whether the holding is beneficially held. Where `false`, further investigation may be required | *** ### PDF download link Every Enhanced Profile response includes a `links.document` field containing a path to a downloadable PDF version of the profile. ```json theme={null} "links": { "document": "/orders/12345/download" } ``` The PDF is generated on demand. If the profile contains a large volume of representative or shareholder records, allow a few seconds after receiving the API response before following the download link. *** ## Data Availability by Jurisdiction The depth of structured data in an Enhanced Profile depends on what the company register files and whether it is available in machine-readable form. | Scenario | Behaviour | | --------------------------------------------------- | ----------------------------------------------------------------------- | | Register files structured UBO data | UBO records appear in `ultimateBeneficialOwners` | | Register files representatives but not shareholders | `capital` array will be absent or empty | | Register files shareholdings as ranges | `percentageIsRange` is `true`; use range fields instead of `percentage` | | Decentralised register (e.g. Germany, Canada) | Data is aggregated from regional sub-registries. | For a full breakdown of data availability by country, see [Supported Jurisdictions](/documentation/useful-information/country-coverage). *** ## Related Endpoints Find a company by name or registration number to retrieve the `id` needed for an Enhanced Profile request. Retrieve a company's core registration details without representative or shareholder data. Order official register extracts and filings alongside your KYB check. View register coverage and data availability across 100+ countries. ```text theme={null} ``` # Retrieve a Document Source: https://developer.kyckr.com/documentation/features/retrieve-a-document-v2 Search for available registry documents, place an order, and download the file. Kyckr provides access to official documents sourced directly from company registries across 100+ countries. This guide covers the complete workflow: searching for available documents, placing an order, polling for completion, and downloading the file. Documents are sourced at the point of request from the originating company registry. Availability and format vary by jurisdiction. *** ## How it works Retrieving a document involves three sequential API calls: 1. **List documents** — discover which documents are available for a specific company 2. **Create order** — place an order for a chosen document 3. **Check order status** — poll until the document is ready, then download *** ## Before you begin You will need the company's `kyckrId` — a unique identifier returned by a [Company Search](/documentation/features/search-for-a-company-v2) or [Global Search](/documentation/features/search-for-a-company-v2). The `kyckrId` takes the format `{countryISO}|{companyId}`, for example `GB|MTE2NTUyOTA`. If you do not yet have a `kyckrId`, run a company search first. *** ## Step 1: List available documents Call the documents endpoint to retrieve the full catalogue of documents available for a given company from its registry. ### Request ```bash theme={null} curl --location 'https://api.kyckr.com/v2/companies/{kyckrId}/documents' \ --header 'Authorization: {{apiKey}}' ``` **Path parameters** | | Parameter | Required | Description | | --------- | --------- | -------- | ----------- | | `kyckrId` | Yes | | | ### Response ```json theme={null} { "correlationId": "019ce19d-8fce-719c-947c-c2ddef9725e4", "cost": { "type": "credit", "value": 0 }, "timeStamp": "2026-03-12T10:35:26.012603Z", "details": "Success", "data": [ { "id": "Q0hPTnwxMTY1NTI5MHxHQl9DSF9DUHwxMDJ8Q29tcGFueSBQcm9maWxl", "cost": { "type": "credit", "value": 1.00 }, "name": "Company Profile", "category": "Extract", "deliveryTimeMinutes": 0, "documentFormat": [ "application/pdf" ] }, { "id": "Q0hPTnwxMTY1NTI5MHxHQl9DSF9DT3wxMDJ8Q29tcGFueSBPZmZpY2lhbHM=", "cost": { "type": "credit", "value": 1.00 }, "name": "Company Officials", "category": "Extract", "deliveryTimeMinutes": 0, "documentFormat": [ "application/pdf" ] } ] } ``` **Key response fields** | Field | Description | | --------------------- | ----------------------------------------------------------------------- | | `id` | Unique document identifier — required to place an order | | `name` | Human-readable document name as provided by the registry | | `cost.value` | Cost in Kyckr Credits to order this document | | `deliveryTimeMinutes` | Expected delivery time in minutes; `0` indicates real-time availability | | `documentFormat` | MIME type of the file that will be delivered | ### Delivery times Some documents — such as company profiles — are available in real time and will show a `deliveryTimeMinutes` of `0`. Others require retrieval by Kyckr's operations team and carry a non-zero delivery estimate. Close to 90% of available documents are delivered within 15 minutes or less. *** ## Step 2: Place an order Once you have identified the document you need, place an order using the `id` from the documents list as the `productId`. You can also supply a `customerReference` to help organise and retrieve orders later. ### Request ```bash theme={null} curl --location 'https://api.kyckr.com/v2/orders?customerReference=my-ref-001' \ --header 'Authorization: {{apiKey}}' \ --header 'Content-Type: application/json' \ --data '{ "kyckrId": "GB|MTE2NTUyOTA", "productId": "Q0hPTl9RMGhmUTI5dGNHRnVlVTF2Y25SbllXZGxjMTh4X01URTJOVFV5T1RBPQ==" }' ``` **Query parameters** | Parameter | Required | Description | | ------------------- | -------- | --------------------------------------------------------------------- | | `customerReference` | No | Your own reference for this order; can be used to filter orders later | **Request body** | Field | Required | Description | | ----------- | -------- | --------------------------------------------- | | `kyckrId` | Yes | Unique company identifier | | `productId` | Yes | The `id` value returned by the documents list | Always supply a `customerReference`. It gives you a stable, human-readable identifier for each order and makes it easy to filter your order history without needing to track internal order IDs. ### Response A successful order returns a confirmation and a unique `orderId` that you will use to track and retrieve the document. ```json theme={null} { "correlationId": "4ca0f21f4b6b4b93a9f64a040914ea4a", "customerReference": "my-ref-001", "timeStamp": "2024-01-25T11:32:26.7086668Z", "details": "Success", "data": { "status": "Pending", "orderId": 302151 } } ``` *** ## Step 3: Check order status Use the orders endpoint to check whether the document is ready. When the order is complete, the response includes download links for the file. ### Request by orderId ```bash theme={null} curl --location 'https://api.kyckr.com/v2/orders/{orderId}' \ --header 'Authorization: {{apiKey}}' \ --header 'Content-Type: application/json' ``` ### Request with filters To retrieve multiple orders, omit the `orderId` path parameter and use query parameters to scope the results. ```bash theme={null} curl --location 'https://api.kyckr.com/v2/orders?pageNumber=1&pageSize=100&startDate=2024-01-20&endDate=2024-01-26' \ --header 'Authorization: {{apiKey}}' \ --header 'Content-Type: application/json' ``` **Query parameters** | Parameter | Description | | ------------------- | ---------------------------------------------------------- | | `pageNumber` | Page number for pagination (default: `1`) | | `pageSize` | Number of results per page (default: `100`) | | `startDate` | Return orders placed on or after this date (`YYYY-MM-DD`) | | `endDate` | Return orders placed on or before this date (`YYYY-MM-DD`) | | `customerReference` | Filter by the reference supplied when placing the order | ### Response ```json theme={null} { "correlationId": "48b9e32527974ca0bc1f606d198669c8", "customerReference": "my-ref-001", "timeStamp": "2024-01-25T12:55:22.351548Z", "details": "Success", "data": { "orderId": "302151", "orderDate": "2024-01-25T11:32:26.7086668Z", "customerReference": "my-ref-001", "status": "Complete", "cost": { "creditCost": 1 }, "productDetails": { "productName": "CH_CompanyMortgages_1", "productId": "Q0hPTl9RMGhmUTI5dGNHRnVlVTF2Y25SbllXZGxjMTh4X01URTJOVFV5T1RBPQ==", "productCategory": "Company Mortgages" }, "companyDetails": { "companyName": "Kyckr", "companyNumber": "11655290", "kyckrID": "GB|MTE2NTUyOTA" }, "links": { "data": "/orders/302151/download?format=json", "document": "/orders/302151/download?format=pdf" } } } ``` ### Order status values | `status` | Description | | ---------- | ---------------------------------------------------- | | `Pending` | Order has been placed and is in progress | | `Complete` | Document is ready — use `links.document` to download | | `Failed` | Order could not be fulfilled | ### Polling guidance For documents that are not delivered in real time, poll the order status endpoint until `status` changes from `Pending` to `Complete` or `Failed`. Polling once per minute is a sensible default. Depending on the jurisdictions and document types your integration relies on, a more tailored interval may be appropriate. Do not attempt to download the document until `status` is `Complete`. The `links` object is only present in the response once the order has been fulfilled. *** ## Step 4: Download the document When `status` is `Complete`, download the document using the path from `links.document`, appended to the API base URL. Two download formats are available. | Format | Description | | ------------- | ------------------------------------------------------- | | `format=pdf` | Returns the document as a PDF file | | `format=json` | Returns structured data in JSON format, where available | ### Request ```bash theme={null} curl --location 'https://api.kyckr.com/v2/orders/302151/download?format=pdf' \ --header 'Authorization: {{apiKey}}' \ --output document.pdf ``` *** ## Complete workflow Run a Company Search or Global Search to confirm the entity and retrieve its `kyckrId`. Call `GET /v2/companies/{kyckrId}/documents` to retrieve the document catalogue for that company. Note the `id` of the document you need. Call `POST /v2/orders` with the `kyckrId`, `productId`, and an optional `customerReference`. Store the `orderId` from the response. Call `GET /v2/orders/{orderId}` repeatedly until `status` is `Complete` or `Failed`. Polling once per minute is recommended. Use the path in `links.document` to download the file. Append `?format=pdf` or `?format=json` depending on the output you need. *** ## API reference Retrieve available documents for a company Place an order for a specific document Retrieve order status and download links # Search for a Company Source: https://developer.kyckr.com/documentation/features/search-for-a-company-v2 Find a company and retrieve the identifier needed for profiles, filings, and ownership discovery. Company search is the entry point to Kyckr. Every subsequent API call — Lite Profile, Enhanced Profile, Filing Search — requires the `id` returned by a successful search. There are two ways to search, both served by the same endpoint. | Search mode | When to use | Required parameters | | ----------------------- | ---------------------------------------------------- | ------------------------------------- | | **Jurisdiction search** | You know the company's country — use this by default | `isocode` + `name` or `companyNumber` | | **Global search** | You don't know the country and cannot determine it | `name` only | Use global search only when the jurisdiction is genuinely unknown. It queries a stored company index rather than live registries, so results may not reflect the current state of the register. Once global search has helped you identify the correct country, always follow up with a jurisdiction search to confirm the company's current status before proceeding. *** ## Jurisdiction search A jurisdiction search queries the official company register for a specific jurisdiction, returning live data at the point of request. Provide either a company name or registration number alongside the two-letter ISO country code for the jurisdiction. The same endpoint handles both search modes. ISO country codes are two-letter and uppercase — for example, `GB` for the United Kingdom, `DE` for Germany, `AU` for Australia. See the full list of [supported jurisdictions](/company-v2/guides/jurisdictions). ### Search by name ```bash theme={null} curl --request GET \ --url 'https://api.kyckr.com/v2/companies?isocode=GB&name=Kyckr' \ --header 'Authorization: Bearer YOUR_API_KEY' ``` ### Search by registration number ```bash theme={null} curl --request GET \ --url 'https://api.kyckr.com/v2/companies?isocode=GB&companyNumber=11655290' \ --header 'Authorization: Bearer YOUR_API_KEY' ``` ### Example response ```json theme={null} { "correlationId": "019cdd97-ac7b-719c-97e2-e7cff9c18769", "cost": { "type": "credit", "value": 0 }, "timeStamp": "2026-03-11T15:50:32.031275Z", "details": "Success", "data": [ { "id": "GB|MTE2NTUyOTA", "companyName": "KYCKR UK LIMITED", "companyNumber": "11655290", "address": "Kemp House, 160 City Road, London, United Kingdom, EC1V 2NX", "status": "Active", "type": "Private limited company", "startDate": "2018-11-01", "registrationAuthority": "Companies House, United Kingdom" } ] } ``` *** ## Global search Use global search only when you cannot determine the company's jurisdiction by other means — for example, when a counterparty hasn't provided their country of registration. It queries a search index across 100+ countries and returns matching entities alongside their jurisdiction, which you can then use to run a jurisdiction search. Global search is a discovery tool, not a substitute for jurisdiction search. Use it to identify the country, then immediately follow up with a jurisdiction search to retrieve live, authoritative data from the official register. Search by name only — no `isocode` is required. ```bash theme={null} curl --request GET \ --url 'https://api.kyckr.com/v2/companies?name=Kyckr' \ --header 'Authorization: Bearer YOUR_API_KEY' ``` ### Example response ```json theme={null} { "correlationId": "976a3da3b7fa4a229958ddd61c8f349f", "timeStamp": "2025-01-15T08:10:30.5431146Z", "details": "Success", "data": { "totalCount": 4, "totalPages": 1, "pageNumber": 1, "pageSize": 50, "companies": [ { "id": "AU|NjA5MzIzMjU3", "companyName": "KYCKR PTY LIMITED", "companyNumber": "609323257", "address": "MASCOT, New South Wales, 2020", "status": "Registered", "type": "Australian Proprietary Company, Limited By Shares", "startDate": "2015-11-16" }, { "id": "IE|NDM2MDI0", "companyName": "KYCKR IRELAND LIMITED", "companyNumber": "436024", "address": "ARC LABS RESEARCH CENTER, WIT WEST CAMPUS, CARRIGANORE WATERFORD, CO WATERFORD, WATERFORD, IRELAND", "status": "Normal", "type": "LTD - Private Company Limited by Shares", "startDate": "2007-03-08" }, { "id": "GB|MTE2NTUyOTA", "companyName": "KYCKR UK LIMITED", "companyNumber": "11655290", "address": "Kemp House, 160 City Road, London, EC1V 2NX", "status": "Active", "type": "Private Limited Company", "startDate": "2018-11-01" }, { "id": "US-OR|ODc4ODc3OTE", "companyName": "KYCKR, LLC", "companyNumber": "87887791", "status": "Inactive", "type": "DOMESTIC LIMITED LIABILITY COMPANY", "startDate": "2012-08-29" } ] } } ``` The `id` field prefix identifies the jurisdiction — `GB` for United Kingdom, `AU` for Australia, `US-OR` for Oregon, and so on. Use this to run a jurisdiction search as your next step. *** ## Key response fields These fields are consistent across both search modes. | Field | Description | | --------------- | -------------------------------------------------------------------------------------------------------------------------------- | | `id` | Unique Kyckr identifier for this company. Required for all subsequent API calls — Lite Profile, Enhanced Profile, Filing Search. | | `companyName` | The company's registered legal name. | | `companyNumber` | The registration number on the company register. | | `status` | Current legal status as reported by the registry (e.g. `active`, `inactive`, `Registered`). | | `type` | Legal form of the company (e.g. `ltd`, `Private Limited Company`). | | `startDate` | Date the company was registered. | | `address` | Registered address as held on the registry. | *** ## Search matching and fuzzy search Kyckr passes search queries directly through to the underlying company register and returns the results as-is. There is no additional matching layer applied on top. As a result, the quality and flexibility of search results depends entirely on the technical capability of each registry — some support partial and fuzzy matching, while others are more rudimentary. This means search behaviour will vary across jurisdictions. A query that returns strong results in one country may return nothing in another, not because the company doesn't exist, but because the registry enforces stricter matching rules. To maximise the likelihood of a successful result: * **Search by registration number when possible.** Number-based searches are exact lookups and are not affected by registry matching quality. They are always the most reliable approach when you have the number available. * **Retry without legal suffixes, if a name search fails.** Terms such as "Limited", "Ltd", "GmbH", "Inc", or "Pty" are handled inconsistently across registries. Searching for the core trading name tends to produce broader results. *** ## Next steps Once you have an `id` from a search result, you're ready to retrieve company data. Fast company verification — status, registered address, and legal form. Full company profile including directors, shareholders, and filing history. Order official registry documents and extracts. Full list of supported countries and ISO codes. *** ## API reference `GET /v2/companies` — full parameter reference and response schema. # Test the API Source: https://developer.kyckr.com/documentation/features/test-the-api-v2 Use the Kyckr sandbox environment to build and verify your integration before going live — at no cost. The Kyckr sandbox is a dedicated test environment that mirrors the full functionality of the production API. You can complete the entire integration journey — searching for companies, retrieving profiles, ordering filings — without incurring charges or touching live registry data. The sandbox covers the V2 REST API only. If you are working with V1, refer to the V1 documentation. *** ## What the sandbox supports The sandbox is designed to let you validate the complete end-to-end flow your integration will rely on in production: | Capability | Available in sandbox | | ------------------------------------- | ---------------------------------- | | Company search by name | ✓ | | Company search by registration number | ✓ | | Lite Profile retrieval | ✓ | | Enhanced Profile retrieval | ✓ (select jurisdictions) | | Filing list retrieval | ✓ | | Filing document download | ✓ (blank PDF returned) | | Order history (`/orders`) | ✓ (fixed response, see note below) | *** ## Connecting to the sandbox The sandbox uses a separate base URL from the production environment. Use your sandbox credentials when making requests. ```bash theme={null} # Base URL — sandbox https://test-api.kyckr.com/v2 ``` All endpoints, request formats, and response schemas are identical to production. No changes to your request structure are needed when switching environments. *** ## Known differences from production Keep the following in mind when building against the sandbox. These are intentional design choices, not bugs. **Name search behaviour.** When searching by company name, the sandbox returns all companies available for the selected country, regardless of the search term you provide. This is expected behaviour — do not rely on search-term filtering when writing sandbox tests. **Performance** Response times in the sandbox are not representative of production. Do not use sandbox performance as a benchmark for SLA planning or latency estimates. **Filing documents** The `/companies/{kyckrId}/documents` endpoint returns a valid list of available filings for any sandbox company. However, the PDF returned on download is always a blank document. This is sufficient to test the ordering and retrieval flow end-to-end. **Order history** The `/orders` endpoint always returns the same fixed list of orders. Querying for a specific order ID is not supported in the sandbox. *** ## Available jurisdictions ### Lite Profile and Enhanced Profile The following jurisdictions have full Lite and Enhanced Profile data available: | Country | Code | | ------------------------ | ------- | | Australia | `AU` | | Austria | `AT` | | Belgium | `BE` | | China | `CN` | | Denmark | `DK` | | Estonia | `EE` | | France | `FR` | | Germany | `DE` | | India | `IN` | | Ireland | `IE` | | Italy | `IT` | | Luxembourg | `LU` | | Netherlands | `NL` | | New Zealand | `NZ` | | Singapore | `SG` | | Spain | `ES` | | United Arab Emirates | `AE` | | United Kingdom | `GB` | | United States — Florida | `US-FL` | | United States — New York | `US-NY` | ### Lite Profile only The following jurisdictions return Lite Profile data only. Enhanced Profile is not available for these in the sandbox. | Country | Code | | ---------------------- | -------- | | Canada (all provinces) | `CA-ALL` | | Canada — Ontario | `CA-ON` | | Canada — Quebec | `CA-QC` | | Switzerland | `CH` | *** ## Recommended test sequence Work through the following sequence to validate your integration before moving to production. Use `/companies/search` with a supported jurisdiction code. Confirm that results are returned and that the response structure matches your expected schema. Use the `kyckrId` from your search result to call `/companies/{kyckrId}/lite`. Verify the fields your integration depends on are present and correctly typed. Call `/companies/{kyckrId}/enhanced` for a jurisdiction that supports it (see table above). Check that the `representatives` and `shareholders` arrays are populated as expected. Call `/companies/{kyckrId}/documents` to retrieve the filing list. Confirm the response structure and that document metadata is present. Order and download a filing document. Verify your pipeline handles the PDF response correctly. The file returned will be blank — this is expected. Call `/orders` to confirm your order history logic handles the fixed sandbox response without errors. *** ## Moving to production Once you have validated your integration in the sandbox, switch to your production credentials and update the base URL. No other changes to your request structure are required. If you do not yet have production credentials, [request access via the Kyckr demo page](https://www.kyckr.com/book-a-demo). # Verify Basic Details Source: https://developer.kyckr.com/documentation/features/verify-basic-details-v2 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. 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. *** ## When to use a Lite Profile Confirm a company's name, registration number, and legal status before proceeding with a full due diligence workflow. Retrieve the company's registered address for identity confirmation or document delivery. Quickly confirm whether a company is active, dissolved, or otherwise no longer trading. Validate a company's existence and basic details before committing to a more detailed — and more expensive — Enhanced Profile order. *** ## How it works Ordering a Lite Profile is a two-step process: Use the [Company Search](/api-reference/companies/search-for-companies) endpoint to locate the company and confirm it exists in the registry. The search response returns an `id` field — a unique identifier for that company in Kyckr's network. Pass the `id `from the search response as the resource identifier in the Lite Profile request. Kyckr retrieves the current data from the registry and returns it in the response. *** ## Request ```bash theme={null} GET /v2/lite/profile/{id}/lite ``` Replace `{id}` with the company identifier returned by the search endpoint. ### Optional Parameters You can include a customer reference for the transaction using the parameter\ key `customerreference` ### Authentication All requests require a Bearer token in the `Authorization` header. ### Example request ```bash theme={null} curl --location 'https://api.kyckr.com/v2/lite/profile/GB|MTE2NTUyOTA/lite' \ --header 'Authorization: Bearer {{apiKey}}' ``` The `id` format encodes the jurisdiction and a registry-specific identifier. In the example above, `GB|MTE2NTUyOTA` identifies Kyckr UK Limited on the UK Companies House register. *** ## Response ### Example response ```json theme={null} { "correlationId": "019cddaa-227e-719c-b9fd-914971d5af98", "customerReference": "", "cost": { "type": "lite", "value": 1 }, "timeStamp": "2026-03-11T16:10:40.8765946Z", "details": "Success", "data": { "activity": [ { "code": "63120", "description": "Web portals", "classificationScheme": "SIC07", "type": "Primary" } ], "address": { "fullAddress": "78 York Street, London, England, W1H 1DP", "buildingName": "78 York Street", "city": "London", "postcode": "W1H 1DP", "country": "England" }, "companyNumber": "11655290", "companyName": "KYCKR UK LIMITED", "foundationDate": { "original": "2018-11-01", "normalized": "2018-11-01" }, "registrationDate": { "original": "2018-11-01", "normalized": "2018-11-01" }, "legalForm": { "original": "Private limited company" }, "legalStatus": { "original": "Active", "normalized": "Active" }, "registrationAuthority": "Companies House, United Kingdom" } } ``` ### Response fields | Field | Description | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `correlationId` | Unique identifier for this API request. Useful for support queries and request tracing. | | `customerReference` | Optional reference value passed in the request. Returned as-is. | | `cost.type` | Will always be `"Lite"`. | | `cost.value` | All lite profiles have the same cost. | | `timeStamp` | UTC timestamp of when the response was generated. | | `details` | High-level status of the request. A value of `"Success"` indicates data was retrieved. | | `data.activity` | Industry activity codes and descriptions as recorded at the registry. Includes a `type` field where available (e.g. `Primary`). | | `data.address` | The company's registered address. Field availability varies by registry. | | `data.companyNumber` | The company's registration number as issued by the registry. | | `data.companyName` | The company's registered name as it appears on the registry. | | `data.foundationDate.original` | The company's registration or foundation date in the registry's original format. | | `data.legalForm.original` | The company's legal form in the registry's original terminology (e.g. `ltd`, `plc`). | | `data.legalStatus.original` | The company's current registration status in the registry's own terminology. This is always a raw string sourced directly from the registry — it is never normalised or mapped to a controlled vocabulary. Values vary by jurisdiction (e.g. `active`, `dissolved`, `radierad`, `liquidation`). | | `data.registrationAuthority` | The name of the company register from which the data was sourced. | 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. `data.legalStatus.original` 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. *** ## 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/companies/enhanced-profile) when your workflow requires ownership structure, representatives, or filings. *** ## Best practices The Lite Profile endpoint requires a valid `id` from the search response. Attempting to construct an `id` manually is not supported and will produce unreliable results. Always derive the `id` from a prior search call. Before passing a company's details into any downstream workflow, inspect `data.legalStatus.original`. Because this value is sourced verbatim from the registry and varies by jurisdiction, do not hardcode checks against a specific string like `"active"`. Instead, build your logic to handle the range of values your target jurisdictions may return, and consider flagging unrecognised values for manual review. Because field availability varies by registry, your integration should treat all `data` fields as optional and handle their absence without throwing errors. Do not assume that a field present in one jurisdiction will be present in another. If you encounter unexpected results or need to raise a support query, include the `correlationId` from the response. This allows Kyckr's support team to trace the exact registry interaction. *** ## Next steps Retrieve directors, shareholders, and full ownership structure for a company. Order official registry documents and historical filings. Browse the full list of countries and registries covered by Kyckr. Full endpoint specification with all parameters and response schemas. # Data-vs-Documents Source: https://developer.kyckr.com/documentation/understanding-kyckr/data-vs-documents When to use structured data versus registry documents. Kyckr provides two distinct types of registry output: **structured company data** (Lite and Enhanced profiles) and **registry documents**. Both are sourced directly from official registers, but they serve different purposes and carry different trade-offs. Understanding the distinction helps you build faster, more reliable KYB workflows. ## Structured Data: Lite and Enhanced Profiles Lite and Enhanced profiles deliver official company information as structured JSON or XML — along with a programmatically generated PDF — retrieved directly from the relevant company register at the point of request. Every profile is a **live record**. When you make a request, Kyckr retrieves the data directly from the official source — synchronously for most jurisdictions. (An async order pattern is in development \[preview] for cases where upstream fulfilment exceeds the connection-hold window.) Either way, the response is time- and date-stamped at the moment of retrieval, giving you a verifiable, point-in-time snapshot of the official register record. In certain jurisdictions where ownership data is not provided in structured form by the registry, shareholding information is extracted from the latest declarations held within registry documents and appended to the live profile at request. ### Lite Profile The Lite profile returns core company information — including registered name, registration number, address, status, legaly type, company activity and incorporation date. It is well-suited to initial entity verification and autofill workflows where speed and volume matter. ### Enhanced Profile The Enhanced profile returns a fuller picture: officers, shareholders and additional structured data where available from the register. It is the appropriate choice for in-depth KYB, onboarding due diligence, and ongoing monitoring. *** ## Why Structured Data Is the Right Choice for Most KYB A common misconception is that documents are inherently more authoritative than data. In practice, the opposite is often true — and the difference matters for the quality of your KYB process. Kyckr's structured profiles are sourced from the same official registers as the documents themselves. They are not interpretations or third-party aggregations. They are the register record, delivered as structured data, timestamped at the point of retrieval. This has meaningful operational advantages: Structured data populates your systems directly. There is no need for an AML analyst to manually transcribe names, addresses, or company numbers from a PDF — eliminating a common source of rework and transcription errors. Profile data is typically returned in seconds. For high-volume onboarding or screening workflows, this is a material advantage over document retrieval. Every profile response includes a retrieval timestamp. This is your audit trail — evidence of what the official register showed at a specific moment in time. JSON and XML responses integrate directly into your KYB platform, case management system, or risk engine without intermediate processing steps. When an AML analyst receives a registry document and manually keys data into a system, every step introduces risk: misread characters, formatting inconsistencies, version confusion. Structured data removes that layer entirely. For the majority of KYB use cases — including regulated onboarding, periodic review, and screening — Lite or Enhanced profile data is sufficient, faster, and less error-prone than document-based extraction. Reserve document orders for cases where the source document itself is required as evidence, or where data fields are unavailable via the structured profile. *** ## Registry Documents Kyckr's document network covers **3,000+ document types** across 100+ countries. The guiding principle is straightforward: if a document is publicly available from a registry - or available subject to legitimate interest - Kyckr can obtain it. Document types include certificates of incorporation, articles of association, annual returns, financial statements, UBO declarations and many more — depending on what each individual register makes available. ### How Documents Are Retrieved Kyckr retrieves documents via two methods, depending on the capabilities of the underlying register. **API-based retrieval** Where a register exposes an API or digital ordering system, Kyckr automates retrieval end-to-end. You place the order; the document is returned without manual intervention. **Agent-assisted retrieval** A significant proportion of registers worldwide do not offer digital APIs. For these, Kyckr employs a specialist network of retrieval agents — available across all timezones — who are expert in obtaining official documents on behalf of clients. Critically, **the customer experience is identical in both cases**. You place the order through the same API or portal. You receive a notification and a link to retrieve the document when it is ready. There is no need to liaise with an agent, track a manual process, or manage a third-party relationship. ### Retrieval Times Every document on the Kyckr network has a defined **target retrieval time**. | Delivery band | Proportion of documents | | ------------------ | -------------------------------- | | 15 minutes or less | \~80% | | Same day | Varies by register | | 1–5 business days | Some jurisdictions | | Longer | Complex or manual-only registers | Retrieval time estimates are available before you place an order, so you can set accurate expectations within your own workflows. *** ## Choosing the Right Output | | Structured Profile (Lite / Enhanced) | Registry Document | | -------------------- | ------------------------------------ | -------------------------------------------------------- | | **Format** | JSON, XML, PDF | Native registry document (PDF, image, or certified copy) | | **Freshness** | Live | Depends on document | | **Retrieval** | Real-time, automated | Automated or agent-assisted | | **Speed** | Seconds | Minutes to days | | **Timestamped** | Yes - at point of retrieval | Yes - at point of retrieval | | **Machine-readable** | Yes | No (requires manual extraction or OCR) | | **Best for** | KYB data population, monitoring | Audit evidence, legal requirements, certified copies | | **KYB-appropriate** | Yes | Yes, where the document itself is required | In many workflows, both are used in combination: structured data to populate and verify records automatically, and documents where a certified source file is required for audit, legal, or regulatory purposes. *** ## Summary Kyckr's structured profiles and document network are complementary, not competing. For most KYB data needs, the Lite or Enhanced profile is faster, more accurate for data population, and directly timestamped from the official source. Documents remain essential where the source file itself carries evidential or legal weight — but should not be the default choice simply because they feel more "official". The data is official. It comes from the same place. If you are unsure which output type is right for your use case, [speak to the Kyckr team](https://www.kyckr.com/book-a-demo). # Country Coverage Source: https://developer.kyckr.com/documentation/useful-information/country-coverage An overview of Kyckr's global registry network — where coverage is strongest, where it is developing, and how to explore availability before you build. Kyckr connects to **300+ company registers across 100+ countries**, sourcing data directly and in real time from official registry sources. This page explains the scope of that network, its current boundaries, and how to check availability for a specific country or register. For a complete, up-to-date list of supported countries and registers, visit the **[Kyckr Coverage Portal](https://coverage.kyckr.com)**. *** ## How the network works Kyckr's registry connections are exclusively **digital**. We integrate directly with registers that provide machine-readable access to company data — whether through an official API, a structured web interface, or a real-time data feed. We do not currently cover registers that require **in-person retrieval** — for example, jurisdictions where official records can only be obtained by physically attending a government office or filing a written request with a local agent. Where this is the case, we note it in the Coverage Portal. This approach ensures that every response you receive reflects data sourced at the point of request, rather than from a static or cached database. *** ## Strong coverage regions ### Europe Kyckr provides comprehensive coverage across **all 27 EU member states** and the **United Kingdom**. This includes the major commercial registries — Companies House (UK), the Handelsregister (Germany), the Registre du Commerce (France), and equivalents across the continent. European coverage is among the deepest in our network, with support for both company search and enhanced profile retrieval in most jurisdictions. ### Offshore financial centres We cover the major **offshore and international financial centres** most commonly required for KYC, AML, and corporate structure work, including: * Cayman Islands * British Virgin Islands (BVI) * Jersey * Guernsey ### APAC financial centres Key **Asia-Pacific** markets are supported, including: * Australia * New Zealand * Singapore * Malaysia * Japan * China ### United States Kyckr covers **all 50 US states**, connecting to the individual Secretary of State registers that maintain company formation and status records at the state level. Because company registration in the US is administered at the state level rather than federally, data structure and availability can vary between states. The Coverage Portal provides state-level detail. *** ## Developing coverage regions ### Middle East and Africa Coverage across the **Middle East and Africa** is currently limited. Many registers in this region still require in-person or manual retrieval processes, which fall outside the scope of Kyckr's digital-only network. We do cover select jurisdictions — check the Coverage Portal for current availability. ### South America **South American** coverage is patchy for similar reasons. Digitalisation of company registers across the region is uneven, and a number of jurisdictions do not yet provide machine-readable access to official data. Coverage continues to expand as registries modernise. *** ## How we expand coverage Kyckr continuously evaluates and upgrades its registry network — both **proactively**, as new digital registries become available, and **reactively**, in response to customer demand and emerging compliance requirements. If you need coverage for a jurisdiction not currently supported, contact your Kyckr representative or [request a demo](https://www.kyckr.com/book-a-demo) to discuss your requirements. *** ## Explore coverage before you build Before integrating against a specific country or register, we recommend verifying availability in the Coverage Portal. It provides: * A full list of supported countries and registers * Indication of which profile types are available per jurisdiction (lite, enhanced, documents) * Notes on any known data limitations or retrieval constraints Explore the full list of supported countries, registers, and data availability by jurisdiction. # Normalised values Source: https://developer.kyckr.com/documentation/useful-information/normalised-values Standard values used in the Kyckr Company API for legal form, capital type, and legal status — the full list and what each value means. Several fields in the Kyckr Company API are returned both as the raw value from the registry (`*.original`) and as a standard Kyckr value (`*.normalized`). The standard values are a smaller, consistent set so you can route entities through the right path in your KYC workflow without parsing every variation a registry might use. The values describe the **legal structure** of an entity. They are intended to support triage in your KYC workflow — for example, routing a Trust to a different sub-workflow than a Public Limited Company. Kyckr does not prescribe what each path should do; the regulatory treatment of an entity depends on your jurisdiction, the rules that apply to your firm, and your internal policy. For finer detail than the standard value provides — for example distinguishing 株式会社 (KK) from 合同会社 (GK) within `Private Limited Company` — read the `*.original` field, which keeps the exact registry-source string. ## `legalForm.normalized` **Beta.** `legalForm.normalized` will first be populated for **Hong Kong**, **China**, and **Japan** in an upcoming release. Other jurisdictions will follow. The `legalForm` field on Lite Profile and Enhanced Profile responses includes both `original` (the registry label) and `normalized` (one of the 15 values below). | Value | What it describes | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `Private Limited Company` | Company with limited shareholder liability that is not publicly tradable. The dominant corporate form in most jurisdictions. | | `Public Limited Company` | Company with limited shareholder liability whose shares may be publicly traded (whether or not the entity is currently listed on an exchange). | | `Limited Partnership` | Partnership with at least one general partner (unlimited liability) and one or more limited partners (liability limited to their contribution). | | `Limited Liability Partnership` | Partnership in which every partner's liability is limited. Member-managed rather than shareholder-managed. | | `General Partnership` | Partnership in which every partner carries unlimited liability. No limited partners. | | `Cooperative` | Member-owned entity, typically with one-member-one-vote governance. Includes mutual societies, mutual insurance, and savings cooperatives. | | `Collective Investment Vehicle` | Pooled investment vehicle — UCITS, AIF, mutual fund, MISM, and similar fund structures. | | `Association` | Member-based entity, not shareholder-based. | | `Sole Proprietor` | A single natural person operating as a business. No separate legal entity from the individual. | | `Branch` | A registered place of business of another legal entity. Has no independent legal personality of its own — the entity that carries the obligations of the branch is the parent. | | `Foreign Registered Body` | A foreign-incorporated legal entity that has registered locally. Has its own legal personality (incorporated elsewhere). | | `Government or Public Body` | An entity owned or controlled by a government or public authority. | | `Foundation` | Civil-law foundation. An entity without members or shareholders, governed by a board against its founding charter. | | `Trust` | Legal arrangement in which property is held by trustees for beneficiaries. | | `Other` | No specific value fits. The registry label is in `legalForm.original`. | ### Branch vs Foreign Registered Body `Branch` and `Foreign Registered Body` look similar but describe different things: * **`Branch`** — no independent legal personality. The branch is an operating arm of a parent entity. The legal entity carrying the obligations of the branch is the parent. The parent may be domestic or foreign — whether the parent is foreign is captured separately on `registrationType`, not in this field. * **`Foreign Registered Body`** — has its own legal personality, incorporated elsewhere. The locally-registered entity is the same legal entity as the foreign-incorporated parent. Some registry data uses the English word "subsidiary" for what is structurally a branch. The Chinese 分公司 (branch) is sometimes rendered upstream as `"Subsidiary"` — a mistranslation, because 子公司 (separate legal entity owned by the parent) is the actual Chinese term for "subsidiary". In the Kyckr response both the string `"Subsidiary"` and the Chinese suffix 分公司 are mapped to `Branch`. See the [China country guide](/country-guides/china) for the full mapping. ### Good to know * **Charity, religious, and similar regulatory designations are an overlay, not a legal form.** A "Company limited by guarantee" registered as a charity is `Private Limited Company` (its legal form); the charity status will be carried separately in a future `regulatoryDesignations[]` field. * **The three partnership values describe different legal structures.** General Partnership, Limited Partnership, and Limited Liability Partnership differ in which partners carry unlimited liability and which carry limited liability. They are not interchangeable. * **Sector labels like "Bank" or "Insurance Company" are not legal forms.** A bank registered as a public company is `Public Limited Company`. The sector aspect is downstream classification. ## `totalCapital.type` The `totalCapital` summary on Enhanced Profile responses includes a `type` field with three possible values. | Value | What it describes | | ------------ | ----------------------------------------------------------------------------------------------------------------------------- | | `Fixed` | Share capital cannot vary without amendment. | | `Variable` | Share capital can vary (open-ended fund / SICAV / mutual structure). | | `Registered` | The registry reports registered-capital amount (rather than authorized or paid-in). Used primarily for CN / JP / VN entities. | ## `legalStatus.normalized` The `legalStatus` field on Lite Profile and Enhanced Profile responses includes both `original` (the registry string) and `normalized` (one of the values below). | Value | What it describes | | ------------ | ------------------------------------------------------------------------------------- | | `Active` | In good standing at the registry. | | `Inactive` | Dissolved, struck off, or otherwise no longer active. | | `Distressed` | In administration, liquidation, insolvency, or similar non-terminal distressed state. | | `Other` | No specific value fits. The registry string is in `legalStatus.original`. | ## How the mapping works Each upstream data source has a lookup table that maps its terms to these standard values. As an integrator you only see the result — both the original registry string and the standard value are returned on every response. ## Future normalised fields Additional fields will be normalised over time and documented here. Likely next: activity / industry classifications, and regulatory-designation overlays (charity, religious, etc.). ## Related references * [Company V2 API Reference](/company-v2/api-reference/overview) * [Company V2 FAQs](/company-v2/guides/faqs) * [Company V1 FAQ](/company-v1/guides/faq) # Understanding Register Data Source: https://developer.kyckr.com/documentation/useful-information/understanding-register-data Why company register data behaves differently — and what to expect when consuming it at scale. Company register data is unlike most data you'll work with. It doesn't behave like a well-maintained SaaS API. It doesn't conform to a global standard. It doesn't come from a single, purpose-built system. It comes from hundreds of independent government-administered registries — each operating to its own legal mandate, on its own infrastructure, under its own rules. Understanding that reality will help you build a more robust integration and set appropriate expectations across your organisation. *** ## Registers are official authorities, not commercial data vendors The starting point for understanding register data is recognising what company registers actually are. They exist to maintain an authoritative legal record of corporate entities within a jurisdiction. Developer access is, at best, a secondary consideration — and in many cases, not a consideration at all. This shapes everything: the data models, the interfaces, the reliability characteristics, and the pace of change. A registry that hasn't meaningfully updated its technical infrastructure in fifteen years isn't failing — it's functioning exactly as its administrators intend. The legal record is intact. The API experience is incidental. What this means for the data you receive: * There is no global standard for how company information is structured or what fields are required * The same concept — registered address, legal status, share capital — may be represented differently across jurisdictions, or not present at all * Data quality reflects what has been submitted to the register, not what a developer might hope to receive * Each registry defines its own data model, and those definitions evolve independently When you query Kyckr, you are retrieving what the official register holds. That is the point — but it is also the source of the behaviours described below. *** ## What reliable access actually requires Building a production-grade integration with a single company registry is a substantial project. Across 300+ registries, the complexity at every stage multiplies. ### Establishing access Before a line of code is written, access to many registries requires clearing procedural and commercial hurdles. Some registries restrict access to locally registered entities. Others require signed data agreements, background checks on the requesting organisation, or manual approval from a government department. A small number require physical presence in the jurisdiction. These aren't edge cases. They represent a meaningful share of the registries that cover commercially significant markets. The timeline for resolving them is measured in weeks or months, not days. ### Building the integration Once access is established, the technical challenge begins. Registries do not offer a uniform interface. Some provide modern APIs with structured responses. Others operate SOAP endpoints, require VPN connections, or mandate IP whitelisting. Some are only accessible by navigating public-facing websites that were built for human use, not programmatic access. A number of registries don't support live queries at all — they publish periodic bulk data exports, which introduces its own data freshness considerations. The integration approach for each registry is determined by what the registry offers — not by what would be most convenient to build. ### Maintaining it This is where the long-term cost is often underestimated. Registries change. Websites are redesigned. Authentication models are updated. Data schemas evolve. APIs are deprecated without notice. For a single integration, this is manageable. Across a large network, it is a permanent operational commitment. A change that appears minor from the registry's side — a renamed field, a certificate renewal, a session handling update — can silently break a production integration. Detecting these failures, diagnosing the root cause, and adapting the integration requires continuous monitoring and the capacity to respond quickly, often without any advance warning from the registry itself. *** ## What to expect from register data in practice ### Reliability is jurisdiction-dependent Public registries are not always available. Scheduled maintenance is common — many systems go offline overnight or at weekends. Unplanned outages occur, particularly on legacy infrastructure under load. Some registries apply rate limits that, if exceeded, result in temporary access blocks. Kyckr handles transient failures with retry logic and monitoring, but some instability will surface to your integration. Build error handling that distinguishes between a Kyckr-side issue and a registry-side event, and implement retry behaviour for requests that matter. ### Response times reflect the underlying registry Response times across the Kyckr network are not uniform — they are a direct function of how the underlying registry operates. A modern registry with a well-maintained API will respond quickly. A registry accessed via legacy infrastructure or web navigation will take longer. Some registries handle requests asynchronously on their side, meaning a single order may take minutes before data is available. Design your integration accordingly. For time-sensitive workflows, understand the typical response characteristics for the jurisdictions you care about most. For bulk or background processing, build for asynchronous patterns from the start. ### Documents are the primary record in many jurisdictions In a significant number of markets, the authoritative company data doesn't exist as structured database fields — it exists in filed documents. Certificates of incorporation, constitutional documents, shareholder registers, and financial statements are frequently available only as PDFs. In many cases, those PDFs are scans of physical documents, not digitally-generated files. This affects what you can do with the data downstream. If your workflow depends on extracting specific fields from documents, that extraction layer needs to be accounted for in your integration design. Structured data returned by the API reflects what the registry exposes programmatically; documents are often the only route to information that sits outside that scope. ### Data completeness varies significantly A response from a UK or German registry will contain substantially more structured data than a response from a registry in a jurisdiction with less developed digital infrastructure. This isn't a gap in Kyckr's coverage — it reflects what each register captures and makes available. When building across multiple jurisdictions, design your data model to treat most fields as optional. Assume that presence in one jurisdiction doesn't imply availability in another, and handle missing fields explicitly rather than defensively. *** ## What a single-country integration looks like To make this concrete, consider what building and maintaining direct access to a single mid-complexity registry typically involves: * Researching access requirements and identifying the correct registration or agreement process * Completing any formal access applications — which may require legal entity verification, signed contracts, or local representation * Building and testing the technical integration against whatever interface the registry offers * Handling data normalisation from the registry's native format into your internal schema * Monitoring for registry-side changes and maintaining the integration as they occur * Managing access credentials, certificates, and any ongoing commercial obligations Multiply that across every jurisdiction your product needs to support, and the operational picture becomes clear. For most organisations, maintaining a global registry network is not the product — it is infrastructure that sits beneath it. Kyckr's network has been built and maintained over more than 20 years. The API abstracts that operational complexity so your integration stays consistent regardless of what is happening at the registry level. For details on supported jurisdictions and document availability by country, see the [Country Coverage](/documentation/useful-information/country-coverage) guide. # Australia (AU) Source: https://developer.kyckr.com/country-guides/australia Country guide for Australian company data including registry information, entity types, identifiers, and data availability. ## Overview **Australian Securities and Investments Commission (ASIC)** Australia's corporate regulator and company registry ASIC registers various types of legal entities under the Corporations Act, ranging from companies to registered schemes and business names. How much company data a lookup returns depends heavily on the entity type involved, which is why entity type is covered before identifiers, search, and share data below. ASIC itself runs more than one register. Its companies register covers the proprietary companies, public companies, foreign companies, registered bodies, and registered schemes that make up the rest of this guide. A second, separate government body sits alongside ASIC: the Australian Business Register (ABR), operated by the Australian Taxation Office, not ASIC. The ABR issues Australian Business Numbers (ABNs) across a far wider range of entity types than ASIC's companies register, see Entity Types below. Many companies hold both an ACN issued by ASIC and an ABN issued by the ABR, commonly registering for the ABN separately for GST or other tax purposes. The two identifiers come from two different bodies for the same company, which is part of why one should never be derived from the other, see Company Identifiers below. ASIC also operates the separate national Business Names Register. A business name is not a legal entity in its own right, so a business name search returns the person or organisation that holds the name, not a company profile. ASIC's register, not the ABR's thinner business-name lookup, is the source of record for who holds a name. ### Data Availability For company-type entities (proprietary companies, public companies, foreign companies, and registered Australian bodies): | Data point | Available | | --------------------- | ----------------------------------------------------------------------- | | Company name | Yes | | Registered address | Yes | | Legal form | Yes | | Registration date | Yes | | Status | Yes | | Representatives | Yes | | Share and member data | Varies by entity type, see Entity Types and Share and Member Data below | Registered schemes and other registrations (business names, associations, charities, and similar) follow a different profile. See Entity Types for the breakdown. ## Entity Types ASIC's term for the people who own a stake in a company is member, not shareholder. For most companies the two are the same group: everyone who holds a share is a member. This guide uses "member" throughout because a few entity types have members without having any shares at all (see limited by guarantee below), so "member" is the term that covers both cases. Entity types outside ASIC's companies register (business names, trusts, partnerships, sole traders, associations, and more) are administered by the ABR, which publishes its own [entity type list](https://abr.business.gov.au/Help/EntityTypeList) covering that wider set. The distinction that matters most for planning an integration: proprietary companies are the only entity type with member-level detail at ASIC. | Entity type | Legal form as returned | Full company profile | Share and member data | | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- | -------------------- | --------------------------------------------- | | Proprietary company | "Australian Proprietary Company Limited By Shares" | Yes | Yes, top twenty members per share class | | Public company (share capital) | "Australian Public Company" or "Australian Public Company Limited By Shares" | Yes | No | | Public company (limited by guarantee) | "Australian Public Company Limited By Guarantee" | Yes | No | | Foreign company | "Foreign Company (Overseas)" | Yes | No, register is held in the home jurisdiction | | Registered Australian body | "Registered Australian Body"\* | Yes | No | | Registered scheme | "Managed Investment Scheme" | Yes | No | | Other registrations (business names, trusts, partnerships, sole traders, associations, and more) | See the ABR entity type list above | No | Not applicable | \* Not directly observed in our own data. This is ASIC's own name for the type rather than a confirmed returned string. A shareholding result can come back empty for three different reasons, and they are not interchangeable: * **No members recorded.** Public companies and registered schemes are not required to notify ASIC of membership changes, so ASIC never holds that detail to return. * **No share capital to hold.** A company limited by guarantee has members but no shares, so there is no share register for ASIC, or anyone, to hold. * **Register held elsewhere.** A foreign company's member register stays with its home jurisdiction. ASIC's Australian record does not include it. ASIC has no public reference page equivalent to the ABR's, so its own type, class, and subclass codes are set out here instead: | Code | Description | | ------ | ------------------------------ | | `APTY` | Australian Proprietary Company | | `APUB` | Australian Public Company | | `ASSN` | Association | | `BUSN` | Business Name | | `CHAR` | Charity | | `COMP` | Community Purpose | | `COOP` | Co-Operative Society | | `FNOS` | Foreign Company (Overseas) | | `LTDP` | Limited Partnership | | `MISM` | Managed Investment Scheme | | `NONC` | Non Company | | `NRET` | Non Registered Entity | | `RACN` | Registered Australian Body | | `REBD` | Religious Body | | `RSVN` | Name Reservation | | `SOLS` | Solicitor Corporation | | `TRST` | Trust | | Code | Description | Has share capital | | ------ | ------------------------------------------------ | ----------------- | | `LMSH` | Limited By Shares | Yes | | `LMSG` | Limited By Shares and Guarantee | Yes | | `LMGT` | Limited By Guarantee | No | | `NLIA` | No Liability | Yes | | `UNLM` | Unlimited | Yes | | `EQUT` | Equity | Not applicable | | `MORT` | Mortgage | Not applicable | | `PROP` | Property | Not applicable | | `NONE` | Does Not Have An Equivalent Australian Liability | Not applicable | | `UNKN` | Liability Unknown | Not applicable | Subclasses refine a company's class further. The two most likely to appear on a public company: | Code | Description | | ------ | ----------------------- | | `LIST` | Listed Public Company | | `ULST` | Unlisted Public Company | The remaining subclasses cover narrower proprietary, foreign, and registrable-body variants: `PROP`, `EXPT`, `EXPN`, `EXPS`, `NEXT`, `NEXN`, `NEXS`, `PNPC`, `PSTC`, `HUNT`, `LISN`, `LISS`, `LXPT`, `NLTD`, `ULSN`, `ULSS`, `FXPT`, `PUBF`, `FFSP`, `RACA`, `RACO`, `NCCT`, `OABR`, `PTSH`, `SPEC`, `STFI`, `NONE`. Entity classification (proprietary, public, limited by guarantee, and so on) is drawn from the entity's legal form text. It is not returned as a separate, independently filterable attribute. ## Company Identifiers Which identifier is primary depends on the entity type: | Identifier | Format | Example | Primary for | | ------------------------------------------ | ---------------- | ------------- | --------------------------------------------------------------------------------- | | Australian Company Number (ACN) | 9-digit numeric | `123456789` | Proprietary and public companies | | Australian Registered Body Number (ARBN) | 9-digit numeric | `123456789` | Foreign companies and registered Australian bodies | | Australian Registered Scheme Number (ARSN) | 9-digit numeric | `123456789` | Registered schemes | | Australian Business Number (ABN) | 11-digit numeric | `12345678901` | Business names, non-registered entities, and a secondary identifier for companies | Some entities, such as certain non-registered entities, are tracked internally by the registry under a number that is never returned in search or profile data. For these, the ABN is the identifier that is exposed and should be treated as primary. ### ABN and ACN are related, but not interchangeable An ABN is often built from an existing ACN or ARBN plus two extra digits, so the two numbers can look related at a glance. That relationship does not hold consistently across every entity, so an ABN should never be derived from an ACN, or vice versa, by manipulating the digits. Always take each identifier from its own field. ## Search Behaviour | Search method | Supported | | ------------------------------------------- | --------- | | Search by company name | Yes | | Search by identifier (ACN, ABN, ARBN, ARSN) | Yes | Name search and identifier search behave differently. Name search matches on the text supplied, so a number typed into the name search field is matched as a literal string rather than resolved to the entity it identifies. To resolve a number to an entity, use an identifier search instead. An identifier search can return more than the identifier that was searched on. Looking a company up by its ABN, for example, returns its ACN alongside it in the same result, since both identifiers belong to the one entity. ## Share and Member Data As set out under Entity Types, only proprietary companies carry member-level detail at ASIC, and even there it is capped: ASIC keeps only the top twenty members of each share class, ranked by shareholding, plus any member tied with the twentieth. The twenty-member cap applies per share class, not per company, so a company with several classes can show far more than twenty holders in total. A class at exactly twenty may be silently truncated: nothing in the data indicates it, so treat such a class as potentially incomplete. A member's shareholding record can also carry a beneficially held indicator alongside the holding percentage, both reflecting exactly what the company itself lodged with ASIC. Beneficially held means the registered holder receives the direct benefit of the shares. Where a holding is recorded as not beneficially held, the registered holder is holding on someone else's behalf, and the register does not identify who that underlying beneficiary is. Each shareholding is also cross-referenced to the specific ASIC document the company lodged to record it. Ordering that document confirms exactly what was submitted, useful where a recorded percentage or status looks inconsistent, but it will not reveal a beneficiary that was never lodged. The register records what the company lodged, and the beneficiary's identity is not part of what is lodged: establishing who ultimately benefits from a holding that is not beneficially held is not a question the register, or any service that relays it, can answer. ## Known Limitations * **Registered schemes never carry an Australian Business Number.** ASIC does not record an ABN against a registered scheme, regardless of when it was registered. * **A business name's Australian Business Number belongs to the entity holding the name, not the business name itself.** Business names are trading names rather than legal entities: where an ABN is present against a business name record, it identifies the underlying legal entity, and the same ABN can appear against more than one business name held by that entity. # Austria (AT) Source: https://developer.kyckr.com/country-guides/austria Country guide for Austria company data including registry information and data availability. ## Overview **Firmenbuch** Official company registry of Austria Primary data source for company information ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | Yes | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Belgium (BE) Source: https://developer.kyckr.com/country-guides/belgium Country guide for Belgium company data including registry information and data availability. ## Overview **Kruispuntbank van Ondernemingen (KBO)** Official company registry of Belgium ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------------------------------------------------- | ---------------- | ------------ | -------------------------- | | Numéro d'entreprise / Ondernemingsnummer / Unternehmensnummer | 10 digit numeral | `0682594839` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Brazil (BR) Source: https://developer.kyckr.com/country-guides/brazil Country guide for Brazil company data including registry information and data availability. ## Overview **Receita Federal do Brasil** Official company registry of Brazil ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------------------------------- | ---------------- | ---------------- | -------------------------- | | CNPJ (Cadastro Nacional da Pessoa Jurídica) | 13 digit numeral | `35636288000170` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | No | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # China (CN) Source: https://developer.kyckr.com/country-guides/china Country guide for China company data including registry information, identifiers, legal forms, and data availability. ## Overview **NECIPS** (National Enterprise Credit Information Publicity System, 国家企业信用信息公示系统) Administered by the State Administration for Market Regulation (SAMR). Provincial / municipal sub-authorities exist but are normalised to NECIPS in the Kyckr response. China corporate data is sourced from NECIPS. Search, Lite Profile, and Enhanced Profile are all supported across V1 and V2. `registrationAuthority` is returned as `"NECIPS"` regardless of which provincial / municipal SAMR sub-authority is recorded at source. **Data quality improvements in progress.** CN responses are being refined for richer structured data and improved standard-value mappings; release notes will follow when updates ship. ## Company identifiers | Identifier | Format | Example | V2 location | V1 location | | --------------------------------- | ---------------------------------------------------------------- | -------------------- | --------------------------------------------------------- | ------------------------- | | Unified Social Credit Code (USCC) | 18-character alphanumeric | `91500112MA61A2D282` | `identifiers.primaryRegistrationNumber` | `codeField` | | Business Registration Number | 15-digit numeric | `110108000123456` | `identifiers.otherIdentifiers[]` with `type: "CN_BRN_CD"` | `otherIdentifiersField[]` | | Organization Code | 8 alphanumeric + check character (0-9 or X), commonly hyphenated | `10001700-2` | `identifiers.otherIdentifiers[]` with `type: "CN_ORG_CD"` | `otherIdentifiersField[]` | The USCC is the current primary CN registration number; it encodes registering authority, entity type, region, and a check digit. The Business Registration Number and Organization Code are pre-2015 legacy identifiers, retired when the USCC reform consolidated them into a single identifier; they remain available in `otherIdentifiers` for entities registered before the reform. ## Company names CN companies are registered in Chinese; an English name (when published) is a transliteration / translation. | V2 field | V1 field | Content | | ------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------- | | `companyName` | `nameField` | **Chinese-script** registered name. For CN entities the source treats the Chinese name as primary, so it occupies `companyName`. | | `englishName` | `englishNameField` | Latin-script English name when distinct from `companyName`. | For CN entities you should treat `englishName` (not `companyName`) as the Latin-script form for display in English-language contexts. ## Legal form CN legal form is populated on both `legalForm.original` (the registry-source label, in English) and `legalForm.normalized` (the [standard value](/documentation/useful-information/normalised-values#legalformnormalized)). | Source label (English) | `legalForm.normalized` | Notes | | ---------------------------------------------------------------------------------- | ------------------------- | ---------------------------------------------------------------------------------------------------- | | Limited Liability Company | `Private Limited Company` | LLC (有限责任公司) is the dominant CN form. All LLC variants map here. | | Joint-stock limited company (and variants — Public Listed / Private / State-Owned) | `Public Limited Company` | The CN 股份有限公司 form — statutorily distinct from LLC and the only CN form that can be publicly traded. | | Other Limited Company By Shares (Public Listed / Private) | `Public Limited Company` | Joint-stock variant; the "Private" qualifier here does not reduce to Private Limited. | | Limited partnership | `Limited Partnership` | 有限合伙. | | Subsidiary *(see callout below)* | `Branch` | Source-data English translation of 分公司 — semantic mistranslation; mapped to `Branch`. | | Other Limited Liability Company Branches | `Branch` | Variant of 分公司. | | Branch of a joint-stock limited company (and variants) | `Branch` | Joint-stock branch variant. | | Individually-owned business | `Sole Proprietor` | 个体工商户. | | Collective ownership (集体所有制) | `Other` | Semantic intermediate between cooperative and association. | | State-owned business unit (unincorporated) | `Other` | Unincorporated SOE form. | If the source label is absent, the legal form is inferred from the Chinese-script company-name suffix (`分公司`, `股份有限公司`, `有限责任公司`, `有限合伙`, `有限公司`). ### Branch vs Subsidiary — translation gotcha The source English translation of the Chinese **`分公司` (fēngōngsī)** is the word **`"Subsidiary"`** — a semantic mistranslation. In Chinese corporate law: * **`分公司` = branch** — no independent legal personality, an operating arm of the parent. * **`子公司` = subsidiary** — separate legal entity owned by the parent. This would map to `Private Limited Company` (or `Public Limited Company`) on its own merit. Kyckr maps both the source English string `"Subsidiary"` and the Chinese name-suffix `分公司` to `Branch` in the normalised response, so integrators see the correct concept. The raw source label is preserved in `legalForm.original`. ## Status CN `legalStatus.original` carries the registry-source English string (which varies across cohorts — multiple parallel translations of 在营 / 开业 appear in the wild). `legalStatus.normalized` maps to one of the standard values: | `legalStatus.original` (English) | Source Chinese | `legalStatus.normalized` | | -------------------------------- | -------------- | ------------------------ | | `In operation (opening)` | `在营（开业）` | `Active` | | `In Business` | `在营` | `Active` | | `Active` | (various) | `Active` | | `Deregistered` | `注销` | `Inactive` | ## Activity / industry codes CN activities populate `activities[]` with: * `activities[].description` — free-text Chinese / English description (e.g. `"Water conservancy, environment and public facility management"`) * `activities[].code` — registry-source industry code where present * `activities[].classificationScheme` — `null` (CN does not carry an explicit classification scheme — NACE / NAICS not used) * `activities[].type` — `"Primary"` when the source flags the activity as primary ## Address CN `address` returns the flat `fullAddress` only — there is no component parsing (`city`, `region`, `streetName`, etc. are null). * `country`: `"China"` * `isoCode`: `"CN"` * `postcode`, `rawAddressLines`, structured components: null ## Capital structure CN entities populate the standard V2 `capital` / `totalCapital` shape: * Currency: RMB (`人民币元` at source; surfaced as `RMB` in normalised output) * `totalCapital.type`: typically `Registered` — the registry reports registered-capital amount (rather than authorized or paid-in). See [Normalised values](/documentation/useful-information/normalised-values#totalcapitaltype). * Thousands-comma source values (e.g. `"302,973,182"`) are normalised to numeric `totalValue` Per-class shareholding capital is surfaced inside `shareholdings[]`. ## Shareholders CN shareholders are returned in V2 `shareholdings[].shareholders` split by entity type: * Corporate shareholders → `shareholdings[].shareholders.corporations[]` * Natural-person shareholders → `shareholdings[].shareholders.individuals[]` Subscribed-capital values that arrive with a currency suffix at source (e.g. `"156,000,000 RMB"`) are normalised to numeric `totalNominalValue` with the currency on the parent capital entry. ## Representatives / directors CN representatives populate V2 `representatives.individuals[]` with English and Chinese name, role, ID information, address, and appointment / outgoing dates. Common CN-specific roles (mapped to standard role values via the director-role lookup): * `Director`, `Supervisor`, `Chairman`, `Vice Chairman`, `Manager`, `General Manager`, `Executive director`, `Legal Representative`, `Board Secretary, Financial Officer of a Listed Company` * Compound roles follow most-significant-first (e.g. `"Manager, Director"` → `MANAGER`; `"Director, General Manager"` → `DIRECTOR`) * `"person in charge"` (the natural-person 负责人 commonly recorded for branch entities) → `LEGAL_REPRESENTATIVE` ## Contact details CN entities consistently surface contact details on V2 `contactDetails`: * `contactDetails.telNumber` * `contactDetails.email` (with `"N/A"` placeholders filtered out) * `contactDetails.website` (with `"N/A"` placeholders filtered out) This is CN-specific behaviour — HK and JP responses do not include contact details. ## Data Availability | Data Point | Available | | ------------------ | ------------------------------- | | Company Name | Yes (Chinese and Latin) | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Varies by entity type | | Share Capital | Yes (not surfaced for branches) | | Activities | Yes | | Contact Details | Yes | | UBOs | No | ## Additional resources * [Normalised values guide](/documentation/useful-information/normalised-values) * [Company V2 API Reference](/company-v2/api-reference/overview) # Denmark (DK) Source: https://developer.kyckr.com/country-guides/denmark Country guide for Danish company data including registry information, identifiers, legal forms, ownership bands, and data availability. ## Overview **CVR** (Det Centrale Virksomhedsregister) Central Business Register Denmark's Central Business Register (CVR) is the official registry for all business entities in Denmark and Greenland. It provides comprehensive company data including registration details, ownership information, and management structure. ## Company Identifiers | Identifier | Format | Example | Notes | | ----------------------- | ----------------- | ------------ | ---------------------------------------------- | | CVR Number (CVR-nummer) | 8-digit numeric | `36734205` | Primary identifier for all registered entities | | VAT Number | `DK` + CVR number | `DK36734205` | CVR number prefixed with country code | | P-Number (pNummer) | 10-digit numeric | `1001564464` | Production unit / establishment identifier | ### Additional Internal Identifiers | Identifier | Description | | -------------------------------- | ---------------------------------------------------- | | Entity Number (enhedsNummer) | Internal CVR system-level ID (up to 10 digits) | | Business Key (forretningsnoegle) | External registration number on participant entities | ## Search Capabilities | Search Method | Supported | | ---------------------- | -------------------------- | | Search by CVR number | Yes | | Search by company name | Yes | | Search by P-number | Yes (for production units) | ## Data Availability | Data Point | A/S | ApS | ENK | I/S / K/S | Non-Profits | Public Entities | | --------------- | ----------- | ----------- | ----------- | ----------- | ----------- | --------------- | | Basic profile | Yes | Yes | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | Yes | Yes | | Capital | Yes | Yes | No | Varies | No | No | | Shareholders | Yes | Yes | No | Varies | Limited | No | | Management | Yes | Yes | Yes | Yes | Yes | Limited | | Activities | Yes | Yes | Yes | Yes | Yes | Yes | | Establishments | Yes | Yes | Yes | Yes | Yes | Yes | | Contact details | If provided | If provided | If provided | If provided | If provided | If provided | **A/S** = Public Limited Company, **ApS** = Private Limited Company, **ENK** = Sole Proprietorship, **I/S** = General Partnership, **K/S** = Limited Partnership ## Legal Forms Denmark has an extensive set of legal form codes. Below are the most common categories. | Code | Abbreviation | Danish Name | English | Notes | | ---- | ------------ | --------------------------- | ----------------------------- | ------------------------------------------ | | 60 | A/S | Aktieselskab | Public Limited Company | Min capital DKK 400,000 | | 80 | ApS | Anpartsselskab | Private Limited Company | Min capital DKK 40,000 | | 81 | IVS | Iværksætterselskab | Entrepreneurial Company | Discontinued since 2019, min capital DKK 1 | | 290 | E/S | SE-selskab | European Company (SE) | Societas Europaea | | 285 | FIV | Særlig finansiel virksomhed | Special Financial Undertaking | Regulated financial entity | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | --------------------------------- | ------------------------------- | | 10 | ENK | Enkeltmandsvirksomhed | Sole Proprietorship | | 15 | PMV | Personligt ejet Mindre Virksomhed | Personally Owned Small Business | | 20 | DØD | Dødsbo | Estate of Deceased | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ------------------------------------ | --------------------------------- | | 30 | I/S | Interessentskab | General Partnership | | 40 | K/S | Kommanditselskab | Limited Partnership | | 45 | MSS | Medarbejderinvesteringsselskab | Employee Investment Company | | 50 | PAR | Partrederi | Shipping Partnership | | 70 | KAS | Kommanditaktieselskab/Partnerselskab | Limited Partnership Company (P/S) | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ---------------------------------------------- | ------------------------------------------ | | 130 | ANS | Andelsselskab (-forening) | Cooperative Society | | 140 | ABA | Andelsselskab (-forening) med begrænset ansvar | Cooperative Society (Limited Liability) | | 150 | FBA | Forening eller selskab med begrænset ansvar | Association or Company (Limited Liability) | | 151 | SMA | Selskab med begrænset ansvar | Company with Limited Liability (SMBA) | | 152 | FMA | Forening med begrænset ansvar | Association with Limited Liability (FMBA) | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | --------------------------------------- | ------------------------------------------- | | 90 | FON | Fonde og andre selvejende institutioner | Foundations and Self-Governing Institutions | | 100 | EFO | Erhvervsdrivende fond | Commercial Foundation | | 110 | FOR | Forening | Association | | 115 | FFO | Frivillig forening | Voluntary Association | | 95 | TRU | Trust | Trust | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ------------------------------------------ | ------------------------------------ | | 170 | FAS | Filial af udenlandsk aktieselskab | Branch of Foreign Public Ltd. Co. | | 190 | FBA | Filial af udenlandsk virksomhed | Branch of Foreign Ltd. Liability Co. | | 200 | - | Filial af anden udenlandsk virksomhedsform | Branch of Other Foreign Entity | | 210 | UDL | Anden udenlandsk virksomhed | Other Foreign Entity | | 291 | FES | Filial af SE-selskab | Branch of European Company (SE) | | 520 | GUS | Grønlandsk afdeling af udenlandsk selskab | Greenlandic Branch of Foreign Co. | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | -------------------------------- | ----------------------------- | | 230 | STA | Statslig administrativ enhed | State Administrative Unit | | 235 | SOV | Selvstændig offentlig virksomhed | Independent Public Enterprise | | 245 | REG | Region | Region | | 250 | KOM | Primærkommune | Municipality | | 260 | FKI | Folkekirkelige Institutioner | Church Institutions | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ------------------------------------------------------- | ------------------------------------------ | | 160 | EØF | Europæisk Økonomisk Firmagruppe | European Economic Interest Grouping (EEIG) | | 195 | SCE | SCE-selskab | European Cooperative Society (SCE) | | 220 | FEØ | Fast forretningssted af Europæisk økonomisk Firmagruppe | Permanent Establishment of EEIG | | Code | Abbreviation | Danish Name | English | | ---- | ------------ | ------------------------------------------ | -------------------------------- | | 240 | AMT | Amtskommune | County Municipality (historical) | | 270 | EUO | Enhed under oprettelse i Erhvervsstyrelsen | Entity Being Registered | | 280 | ØVR | Øvrige virksomhedsformer | Other Legal Forms | | 990 | UOP | Uoplyst virksomhedsform | Undisclosed Legal Form | ## Status Codes ### Primary Status Values | Danish Status | English | Normalized | | ---------------------------------- | ------------------------------------- | ---------- | | NORMAL | Active / Normal | Active | | OPLØST | Dissolved | Inactive | | OPLØST EFTER KONKURS | Dissolved after Bankruptcy | Inactive | | OPLØST EFTER ERKLÆRING | Dissolved after Declaration | Inactive | | OPLØST EFTER FRIVILLIG LIKVIDATION | Dissolved after Voluntary Liquidation | Inactive | | OPLØST EFTER FUSION | Dissolved after Merger | Inactive | | OPLØST EFTER SPALTNING | Dissolved after Demerger | Inactive | | OPHØRT | Ceased | Inactive | | KONKURS | Bankrupt | Inactive | | TVANGSOPLØST | Compulsorily Dissolved | Inactive | | SLETTET | Deleted | Inactive | | UNDER TVANGSOPLØSNING | Under Compulsory Dissolution | Distressed | | UNDER FRIVILLIG LIKVIDATION | Under Voluntary Liquidation | Distressed | | UNDER KONKURS | Under Bankruptcy | Distressed | | UNDER REKONSTRUKTION | Under Reconstruction | Distressed | Some entity types (particularly sole proprietorships, associations, and public entities) may use a simplified status system with values like "Aktiv" (Active) or "Ophørt" (Ceased). ## Activity Codes Denmark uses **DB07** (Dansk Branchekode 2007), the Danish implementation of **NACE Rev. 2**. | Field | Description | Example | | ---------------------------- | ------------------------------ | --------------------- | | Industry code (branchekode) | 6-digit NACE-compatible code | `620100` | | Industry text (branchetekst) | Activity description in Danish | Computerprogrammering | | Classification scheme | DB07\_NACErev2 | - | The first 4 digits align with the EU NACE standard; the last 2 digits provide Danish sub-detail. Companies may have a main activity (hovedbranche) and up to three secondary activities (bibranche). ## Ownership Data **Ownership is reported as bands, not exact percentages.** CVR reports ownership as ranges rather than precise values. This is a regulatory feature of Danish company law, not a data limitation. ### Ownership Bands | Band | Display Value | | ------------ | ------------- | | 5-9.99% | 5-9.99% | | 10-14.99% | 10-14.99% | | 15-19.99% | 15-19.99% | | 20-24.99% | 20-24.99% | | 25-33.32% | 25-33.32% | | 33.33-49.99% | 33.33-49.99% | | 50-66.66% | 50-66.66% | | 66.67-89.99% | 66.67-89.99% | | 90-99.99% | 90-99.99% | | 100% | 100% | Ownership data includes both share capital ownership and voting rights, which may be reported in different bands for the same shareholder. ## Address Format Danish addresses follow a structured format: **Standard format:** ```text theme={null} Højbro Plads 10, 1200 København K, Denmark ``` **With floor and apartment:** ```text theme={null} Vesterbrogade 42, 3. th, 1620 København V, Denmark ``` ### Address Components | Component | Description | Example | | ------------------------------ | --------------------------- | ---------------------- | | Street name (vejnavn) | Street name | Højbro Plads | | House number (husnummerFra) | Building number | 10 | | Floor (etage) | Floor number | 3 | | Side door (sidedoer) | Apartment indicator | th (til højre = right) | | Postal code (postnummer) | 4-digit postal code | 1200 | | Postal district (postdistrikt) | City/area name | København K | | Municipality (kommune) | Administrative municipality | KØBENHAVN | ## Capital Structure Standard minimum capital requirements: | Legal Form | Minimum Capital | | --------------------- | ------------------------------- | | A/S (Public Limited) | DKK 400,000 | | ApS (Private Limited) | DKK 40,000 | | IVS (Entrepreneurial) | DKK 1 (discontinued since 2019) | Capital is typically reported in Danish Kroner (DKK). If no currency is specified in the registry data, DKK is assumed. ## Representatives ### Common Roles | Danish Role | English | Description | | ------------------------ | --------------------- | --------------------------- | | DIREKTØR | Director | Company director | | ADMINISTRERENDE DIREKTØR | CEO | Chief Executive Officer | | BESTYRELSESFORMAND | Chairman of the Board | Board chairman | | NÆSTFORMAND | Deputy Chairman | Vice chairman | | BESTYRELSESMEDLEM | Board Member | Board member | | SUPPLEANT | Alternate | Substitute/alternate member | | REVISOR | Auditor | Company auditor | | LIKVIDATOR | Liquidator | Appointed for dissolution | | STIFTER | Founder | Company founder | | PROKURA | Procurator | Signatory authority holder | ## Establishments (Production Units) Danish companies can have multiple production units (penheder), representing physical locations where the company operates. Each is identified by a unique 10-digit P-number. Production unit details (name, address, activities) may require additional lookups. The primary company lookup returns P-numbers and validity periods for each unit. ## Implementation Notes **Empty results possible**: Some CVR numbers may return no results if the entity does not exist in the current registry index. **Historical data model**: All Danish company data is versioned with validity periods. Current values have no end date. For dissolved companies, all records have end dates, and the most recent values are used. ### Known Limitations 1. **Ownership bands**: Exact shareholding percentages are not available - only the band (range) is reported 2. **Establishment details**: Production unit records contain only identifiers and dates; detailed branch information requires separate lookups 3. **Status variations**: Different entity types may use different status reporting systems # Estonia (EE) Source: https://developer.kyckr.com/country-guides/estonia Country guide for Estonian company data including registry information, identifiers, legal forms, and data availability. ## Overview **RIK** (Registrite ja Infosüsteemide Keskus) Centre of Registers and Information Systems Estonia's business register (Äriregister) is the official registry for all legal entities in Estonia. It is maintained by the Centre of Registers and Information Systems (RIK) and provides comprehensive company data including registration details, shareholders, and management information. ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------------------------------ | --------------- | ------------- | ------------------------------------------------- | | Registration Number (Registrikood) | 8-digit numeric | `10422334` | Unique identifier for all Estonian legal entities | | VAT Number (Käibemaksukohustuslase number) | `EE` + 9 digits | `EE102269053` | Not all companies have VAT registration | ### Registration Number Patterns * Numbers starting with **1xxxxxxx** are typically older companies * Numbers starting with **8xxxxxxx** or **9xxxxxxx** are typically newer or special entities ### VAT Number Details VAT data includes: * VAT number * Active status (current VAT status) * Registration date * Deregistration date (if applicable) ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------------------------------- | | Search by registration number | Yes | | Search by company name | Yes | | Search by VAT number | Partial (via registration lookup) | ## Data Availability | Data Point | AS | OÜ | MTÜ | FIE | KÜ | | -------------------- | ------------- | ------------- | ------------- | ------------- | ------- | | Registration details | Yes | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | Limited | | Capital | Yes | Yes | No | No | No | | Shareholders | Yes | Yes | Yes | No | No | | Management board | Yes | Yes | Yes | No | Yes | | VAT number | If registered | If registered | If registered | If registered | No | | Activities (NACE) | Yes | Yes | Yes | Yes | Limited | **AS** = Public Limited Company, **OÜ** = Private Limited Company, **MTÜ** = Non-profit, **FIE** = Sole Proprietor, **KÜ** = Apartment Association ## Legal Forms | Code | Estonian | English | Notes | | ---- | ------------ | ----------------------- | ---------------------------- | | AS | Aktsiaselts | Public Limited Company | Min capital EUR 25,000 | | OÜ | Osaühing | Private Limited Company | Min capital EUR 2,500 | | TÜ | Täisühing | General Partnership | Unlimited liability | | UÜ | Usaldusühing | Limited Partnership | At least one limited partner | | Code | Estonian | English | Notes | | ---- | ----------------------------- | ----------------------- | ------------------------ | | FIE | Füüsilisest isikust ettevõtja | Sole Proprietor | Natural person business | | MTÜ | Mittetulundusühing | Non-profit Organisation | No profit distribution | | SA | Sihtasutus | Foundation | Asset-based legal entity | | KÜ | Korteriühistu | Apartment Association | Housing cooperative | | Code | Estonian | English | Notes | | ---- | -------- | ------- | ---------------------- | | - | Filiaal | Branch | Foreign company branch | ## Status Codes | Code | Estonian | English | Normalized Status | | ---- | ------------------------------------ | ----------------------------- | ----------------- | | R | Registrisse kantud | Entered into the register | Active | | L | Likvideerimisel | In liquidation | Distressed | | N | Pankrotis | In bankruptcy | Distressed | | K | Kustutatud | Deleted | Inactive | | KN | Kustutatud pankroti lõppemisel | Deleted following bankruptcy | Inactive | | KL | Kustutatud likvideerimise lõppemisel | Deleted following liquidation | Inactive | ## Activity Codes Estonia uses **EMTAK** (Eesti Majanduse Tegevusalade Klassifikaator), which maps to **NACE Rev. 2**. | Field | Description | Example | | ----------- | ------------------------------- | ---------------------------------------------------- | | `nace_code` | NACE Rev. 2 code format (XX.XX) | `70.20` | | `name` | Activity description in English | Business and other management consultancy activities | | `version` | NACE version | `2.1` | ## Address Format Estonian addresses use a component-based structure. Example formats: **Standard format:** ```text theme={null} Harju maakond, Tallinn, Kesklinna linnaosa, A. Weizenbergi tn 32 ``` **With apartment number:** ```text theme={null} Ida-Viru maakond, Narva linn, Pähklimäe tn 6-127 ``` ### Address Components | Component | Maps To | Example | | ------------------------ | --------------- | ------------------ | | County (maakond) | Region | Harju maakond | | Municipality | Municipality | Tallinn | | Settlement unit | City | Tallinn | | City district (linnaosa) | City (fallback) | Kesklinna linnaosa | | Thoroughfare (tn) | Street Name | A. Weizenbergi tn | | Building number | Street Number | 32 | ## Implementation Notes **Address may be null**: Some entity types (particularly apartment associations) may have no registered address in the registry data. **Non-profit shareholders**: Non-profit organisations (MTÜ) have members rather than shareholders with share capital. Ownership data for these entities will show percentage ranges (0-100%) rather than exact percentages, indicating that precise ownership cannot be determined from the registry data. ### Representatives Estonian companies distinguish between several types of officials: | Role | Code | Description | | ------------------------- | ---- | ---------------------------------------------------------------- | | Management Board Members | JUHL | Primary operational management (Juhatuse liikmed) | | Supervisory Board Members | NOUK | Oversight function, typically for AS companies (Nõukogu liikmed) | | Procuration Holders | - | Special commercial power of attorney (Prokuristid) | # Finland (FI) Source: https://developer.kyckr.com/country-guides/finland Country guide for Finland company data including registry information, identifiers (Y-tunnus), legal forms, status codes, and implementation notes. ## Overview **PRH** (Patentti- ja rekisterihallitus) Finnish Patent and Registration Office; maintains the Trade Register (Kaupparekisteri) Finnish company data in the Enhanced Profile is sourced from the Trade Register (Kaupparekisteri) maintained by PRH. You get the Business ID (Y-tunnus) as the primary identifier, company name, legal form, status, registered address, share capital when available, and legal representatives. ## Company Identifiers | Identifier | Format | Example | Notes | | ---------------------- | --------------------------------- | ------------ | ----------------------------------------------------------------- | | Y-tunnus (Business ID) | 7 digits + hyphen + 1 check digit | `2552951-7` | Primary company identifier; check digit uses modulo-11 validation | | VAT Number | FI + 8 digits | `FI25529517` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ------------------------------------------- | --------- | | Search by registration number (Business ID) | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | Yes | | UBOs | No | ## Legal Forms The Enhanced Profile returns legal form as an English description. The registry uses form codes; the main types you may see are listed below. | Code | Finnish | English | | ---- | ------------------- | ---------------------- | | OY | Osakeyhtiö | Limited company | | OYJ | Julkinen osakeyhtiö | Public limited company | | Code | Finnish | English | | ---- | -------------------------------- | ------------------- | | AY | Avoin yhtiö | Partnership | | KY | Kommandiittiyhtiö | Limited partnership | | YEH | Yksityinen elinkeinonharjoittaja | Private trader | | Code | Finnish | English | | ---- | ------------ | ----------------- | | OK | Osuuskunta | Co-operative | | OP | Osuuspankki | Co-operative bank | | SP | Säästöpankki | Savings bank | | Code | Finnish | English | | ---- | ------------------------------------------- | ------------------------------------------------------- | | SE | Eurooppayhtiö | European company | | SCE | Eurooppaosuuskunta | European co-operative society | | SCP | Eurooppaosuuspankki | European co-operative bank | | ETY | Eurooppalainen taloudellinen etuyhtymä | European economic interest grouping | | ETS | ETEY:n sivuliike Suomessa | Finnish branch of a European economic interest grouping | | SL | Ulkomaisen elinkeinonharjoittajan sivuliike | Branch of a foreign trader | | Code | Finnish | English | | ---- | ---------------------------------- | ---------------------------------------------- | | SÄÄ | Säätiö | Foundation | | TYH | Taloudellinen yhdistys | Association for carrying on economic activity | | AYH | Aatteellinen yhdistys | Non-profit association | | AOY | Asunto-osakeyhtiö | Housing company | | ASY | Asumisoikeusyhdistys | Right-of-occupancy association | | KKOY | Keskinäinen kiinteistöosakeyhtiö | Limited liability joint-stock property company | | VLL | Valtion liikelaitos | State-owned company | | VOY | Vakuutusosakeyhtiö | Limited insurance company | | VOJ | Julkinen vakuutusosakeyhtiö | Public limited insurance company | | KVY | Keskinäinen vakuutusyhtiö | Mutual insurance company | | KVJ | Julkinen keskinäinen vakuutusyhtiö | Public mutual insurance company | | HY | Hypoteekkiyhdistys | Mortgage society | | VY | Vakuutusyhdistys | Insurance association | ## Status Codes The Enhanced Profile returns a status description and a normalized status (Active or Inactive). | Code | Finnish | English | Normalized Status | | ---- | ------------ | --------------- | ----------------- | | R | Rekisterissä | In the register | Active | | L | Lakannut | Dissolved | Inactive | | P | — | (other state) | Inactive | ## Address Format Addresses in the Enhanced Profile include street name, city, postcode, and country (Finland). **Example format:** ```text theme={null} Mannerheimintie 10, 00100 Helsinki, Finland ``` ### Address components in the profile | Component | Description | | ---------- | ---------------------------- | | streetName | Street address (single line) | | city | City or locality | | postcode | Postal code | | country | Finland | ## Implementation Notes The Finnish registry holds data in Finnish and Swedish. The Enhanced Profile returns English descriptions for legal form and representative roles. ### Representatives Representatives in the Enhanced Profile include role (in English), an active flag, birth date when available, and name. Roles you may see include: | Role | | ------------------------------------- | | Chairperson | | Vice-chairperson | | Ordinary member | | Deputy member | | Managing Director | | Substitute for the Managing Director | | Deputy Managing Director | | Holder of procuration | | Representative | | Substitute representative | | Director | | Auditor | | Additional auditor | | Auditor with principal responsibility | | Liquidator | | Deputy liquidator | | In charge of administration | | House Manager | | Trader | Place of residence is not included in the profile. ### Capital When share capital is available, the Enhanced Profile returns **totalCapital** with: * **totalValue**: Capital amount * **quantity**: Amount of shares * **currency**: Currency code (e.g. EUR) No per-share-class breakdown is returned; only total capital is provided. # France (FR) Source: https://developer.kyckr.com/country-guides/france Country guide for France company data including registry information, identifiers (SIREN, SIRET), legal forms, status codes, APE activities, and implementation notes. ## Overview **RNE** (Registre National des Entreprises) Official company registry of France French company data is sourced from the Registre National des Entreprises (RNE) via the Institut National de la Propriété Industrielle (INPI). The data includes the SIREN as the primary company identifier, establishments identified by SIRET, representatives with INPI role codes, capital (amount, currency, fixed or variable), and APE (NAF) activity classification. ## Company Identifiers | Identifier | Format | Example | Notes | | ---------- | ---------------------------------- | ---------------- | ------------------------------------------------------------------------------------ | | SIREN | 9-digit numeric | `325013555` | Primary company identifier; used for search and profile requests | | SIRET | 14-digit numeric (9 SIREN + 5 NIC) | `32501355500012` | Identifies each establishment (principal and secondary); NIC is establishment number | | VAT Number | FR + digits | `FR12345678901` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ------------------------------------- | --------- | | Search by registration number (SIREN) | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | Yes | | Establishments | Yes | | UBOs | No | ## Legal Forms Legal form is provided from INPI/INSEE forme juridique (numeric code), mapped to a French description in the API response. Unmapped codes may appear as "Form" followed by the code. | Code | Description | | ---- | -------------------------------------------------------------------- | | 5710 | SAS, société par actions simplifiée (Simplified Joint Stock Company) | Other numeric codes (e.g. 5202, 5499, 5599, 6220, 6540, 6565, 6599) may appear in data; the full list is maintained by INSEE. Occasionally the source may provide a text description (e.g. Société en nom collectif) instead of a code. ## Status Codes Status is derived from cessation and dissolution indicators in the registry. Normalized values are **Active**, **Distressed**, or **Inactive**. | Condition | Normalized Status | | ---------------------------------------------------------------------------------------------------------------------- | ----------------- | | No cessation details, or dissolution false and no dissolution/disappearance date | Active | | Dissolution in progress (e.g. liquidator appointed, registration maintained) | Distressed | | Effective cessation date or removal from register present; or dissolution and legal entity disappearance both complete | Inactive | Granular cessation information is available in status details: removal date, effective date, total activity cessation date, liquidation closure date, dissolution type, liquidator appointment publication (date and journal), and principal establishment formality status or closure/transfer dates when applicable. ## Activity Codes France uses **APE** (Activité Principale Exercée), aligned with **NAF rev. 2**, for business activity classification. | Field | Description | Notes | | ----------- | -------------------- | --------------------------------------------------------------------------- | | code | APE/NAF code | Company-level code is the primary activity | | description | Activity description | From company objet or establishment description | | type | Primary or Secondary | Primary = company-level; Secondary = from principal or other establishments | Activities from closed establishments (closure effective date present) or activities with an end date are excluded from the response. ## Address Format Company and establishment addresses use a component-based structure. **Example format:** ```text theme={null} 12, rue de la Paix, 75002 Paris, France ``` ### Address Components | Source Component | Maps To | Description | | -------------------------------- | ---------------- | --------------------------------------- | | numVoie | streetNumber | Street number | | typeVoie + voie (establishments) | streetName | Street type and name (e.g. rue, avenue) | | voie (company address) | streetName | Street name | | complementLocalisation | (in fullAddress) | Additional location detail | | distributionSpeciale | (in fullAddress) | Special distribution (e.g. Bâtiment A) | | commune | city | Commune/town name | | codePostal | postcode | 5-digit postal code | | pays | country | Country name | ## Implementation Notes ### Representatives Representatives are split into corporations (legal entities) and individuals. Each has a role derived from the INPI role code (roleEntreprise), mapped to a French role name. Known mappings include: | Code | Role (French) | | ---- | --------------------------------- | | 53 | Directeur Général | | 71 | Commissaire aux comptes titulaire | | 99 | Autre | Other codes (e.g. 13, 28, 29, 30, 40, 51, 65, 70, 72, 73, 75) may appear in data; unmapped codes are returned as "Role" followed by the code. Corporations include SIREN and company name; individuals include name, birth date, and place of residence (city, postcode, country). ### Establishments Each company has a principal establishment and zero or more other establishments. Each establishment includes: * **id**: SIRET (14 digits) * **isPrincipal**: true for the principal establishment * **isActive**: false if closure effective date or end-of-activity date is present * **creationDate** / **endDate**: from establishment activity or registration dates * **address**: same component structure as above (typeVoie + voie for street name) ### Capital When capital is present in the registry: * **totalCapital** includes total value, currency, and type (**Fixed** or **Variable** from the capitalVariable indicator). * The **capital** array contains nominal value and currency. It is populated only when a capital amount is present. ### Status details The status details array includes the number of open establishments and, when present, cessation-related keys (e.g. dissolution indicator, removal date, effective date, liquidation closure date, dissolution type, liquidator appointment publication, principal establishment formality status or closure/transfer dates). Use these for granular visibility into company and establishment status. # Germany (DE) Source: https://developer.kyckr.com/country-guides/germany Country guide for Germany company data including registry information and data availability. ## Overview **Bundesanzeiger Verlagsgesellschaft mbH & Common register portal of the German federal states (Handelsregister)** Official company registry of Germany ## Company Identifiers | Identifier | Format | Example | Notes | | ---------------------- | ------------ | ------------ | -------------------------- | | Handelsregisternummern | Alphanumeric | `HRB 130192` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Gibraltar (GI) Source: https://developer.kyckr.com/country-guides/gibraltar Country guide for Gibraltar company data including registry information and data availability. ## Overview **Companies House Gibraltar** Official company registry of Gibraltar ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | No | | Shareholders | No | | Share Capital | Yes | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Greece (GR) Source: https://developer.kyckr.com/country-guides/greece Country guide for Greece company data including registry information and data availability. ## Overview **General Commercial Register (G.E.M.I.)** Official company registry of Greece ## Company Identifiers | Identifier | Format | Example | Notes | | ----------- | ------- | -------------- | -------------------------- | | GEMI Number | Numeric | `157741701000` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Guernsey (GG) Source: https://developer.kyckr.com/country-guides/guernsey Country guide for Guernsey company data including registry information and data availability. ## Overview **Guernsey Registry** Official company registry of Guernsey ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Hong Kong (HK) Source: https://developer.kyckr.com/country-guides/hong-kong Country guide for Hong Kong company data including registry information, identifiers, legal forms, bilingual name handling, and data availability. ## Overview **ICRIS** (Integrated Companies Registry Information System) for companies + **BRO** (Business Registration Office) for sole proprietorships Operated by the Companies Registry of Hong Kong and the Inland Revenue Department respectively Hong Kong corporate data is sourced from ICRIS for Companies Registry entities and from the Business Registration Office for sole proprietorships. Search, Lite Profile, and Enhanced Profile are all supported across V1 and V2. Registry Documents search is supported for CR entities (94+ filing types observed in production); sole proprietorships and mutual funds are not supported on the document-search endpoint. **Data quality improvements in progress.** HK responses are being refined for richer structured data and improved standard-value mappings; release notes will follow when updates ship. ## Company identifiers The HK identifier is the **Company Registration Number**: typically an 8-digit zero-padded numeric string. Different prefixes indicate different entity types, and sole proprietorships use a hyphenated format. | Identifier | Format | Example | Notes | | ------------------- | --------------------------- | -------------- | ------------------------------------------------------------- | | Standard CR Number | 8-digit numeric (no prefix) | `03645219` | Private Ltd and Public Ltd HK-incorporated companies | | Non-HK company | `F-` prefix | `F0008739` | Registered non-Hong Kong companies (foreign) | | Guarantee company | `C-` prefix | `C0486085` | Companies limited by guarantee, charities, special categories | | Mutual Fund | `MF-` prefix | `MF001910` | Investment funds | | Sole proprietorship | `NNNNNNN-NNN` (hyphenated) | `41409990-000` | Business Registration; suffix is branch number | In V2 the CR Number is `companyNumber` and is also the registry-encoded portion of the V2 `id`. In V1 it appears as `codeField`. **Do not confuse with the Business Registration Number (BRN).** The BRN is a separate document issued by the Inland Revenue Department. The Company Registration Number (above) is the correct identifier for API requests. ## Entity types Six entity types are returned for HK. The Kyckr response shape is consistent across all six (transformation reconciles registry-specific source-data differences); the matrix at the bottom of this guide details which fields are populated per entity type. | Entity type | Coverage source | | --------------------------------------- | ---------------------------- | | Private company limited by shares | ICRIS | | Public company limited by shares | ICRIS | | Registered non-Hong Kong company | ICRIS | | Mutual Fund | ICRIS | | Company limited by guarantee | ICRIS | | Sole proprietorship (`個人 / INDIVIDUAL`) | Business Registration Office | ## Company names Hong Kong companies frequently hold both an English and a Traditional Chinese registered name. Three Kyckr fields carry HK name information: | V2 field | V1 field | Content | | --------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `companyName` | `nameField` | The **primary** registered name as held at source: for most HK-incorporated companies this is the English (Latin-script) name. For some registered non-HK companies (e.g. Bank of China subsidiaries) the source treats the **Chinese** name as primary, and `companyName` carries the Chinese name. | | `englishName` | `englishNameField` | Populated only when `companyName` is non-Latin AND a distinct Latin-script name is available at source. This is the recovery field for the registered-non-HK-company case where the English name is not in the primary slot. | | `aliases[]` (type: `Original Language`) | `aliasesField` | The source original-language name when distinct from `companyName`: for normal HK entities (English primary) this is where the Traditional Chinese name appears. Suppressed when `englishName` is populated, to avoid mislabelling an English string as "Original Language". | This means: * **Normal HK case (Latin primary):** `companyName` = English, `englishName` = `null`, `aliases[]` = Chinese (Original Language). * **Bank of China-style case (Chinese primary):** `companyName` = Chinese, `englishName` = English, `aliases[]` = `null`. In both cases the English name is reachable on a single field: `companyName` when present there, otherwise `englishName`. Some Chinese names appear in parentheses at the registry (e.g. `(中銀集團人壽保險有限公司)`); these are preserved as supplied. Previous names, including bilingual previous-name pairs, are surfaced in `previousNames`. ## Legal form HK Lite Profile populates `legalForm.normalized` only when the regulator-mandated Chinese suffix `有限公司` appears on the original-script name. This is the official suffix that signals an HK Private Limited Company; emission is rule-based, not heuristic. | Source signal | `legalForm.normalized` | Notes | | ------------------------------------------------------------- | ------------------------- | --------------------------------------------------------------------------------------- | | Chinese name contains `有限公司` | `Private Limited Company` | Regulator-mandated suffix; emitted when present | | English-only registered names (PLC, FOUNDATION, FUND, BANK …) | `null` | Source rule: emit when the source has the signal; null when it does not | | Lite payload missing the suffix entirely | `null` | E.g. HSBC BANK PLC, BOCHK CHARITABLE FOUNDATION, HSBC ASSET MANAGEMENT INVESTMENT FUNDS | HK Enhanced Profile surfaces an explicit entity-type signal and populates `legalForm.normalized` for all entity types (`Private Limited Company`, `Public Limited Company`, `Association`, `Collective Investment Vehicle`, `Foreign Registered Body`, `Sole Proprietor`, etc.). ## Status `legalStatus.original` carries the registry-source string; `legalStatus.normalized` maps to one of the standard values: | `legalStatus.original` | Meaning | `legalStatus.normalized` | | ---------------------------------------- | ------------------------------------------------------------- | ------------------------ | | `Live` | Active and in good standing | `Active` | | `Dissolved` | No longer exists (dissolution method on `legalStatus.detail`) | `Inactive` | | `Ceased place of business` | Non-HK company ceased HK operations | `Inactive` | | `Live, Commenced dormancy on YYYY-MM-DD` | Active but dormant (compound status with date) | `Active` | ### Dissolution methods For dissolved companies, the dissolution method is surfaced alongside the status: * Dissolved by Deregistration: administrative removal from register * Dissolved by Winding Up (Others): court-ordered or other winding up * Dissolved by Members' Voluntary Winding Up: solvent company, members' choice * Dissolved by Creditors' Voluntary Winding Up: insolvent company, creditors' process * Deregistration in progress: company may still be `Live` while deregistration is processed A separate non-dissolution marker, "Licence granted to dispense with `Limited` and/or `有限公司` in company name", is a special licence, not a dissolution. ## Capital structure CR entities populate the standard V2 `capital` / `totalCapital` shape. Mutual funds, sole proprietorships, and guarantee companies do not have capital data. * Issued and paid-up capital are usually identical for HK-incorporated companies. * Paid-up capital is null for registered non-HK companies. * **Multi-currency entries are common**: some entities have capital entries with different currencies (e.g. GBP + USD on the same company). Do not assume one entity = one currency. * Decimal values are returned as decimals. ### Currency distribution (observed) | Currency | Typical entity | | -------- | ------------------------------------------------------- | | HKD | Most HK-incorporated companies | | USD | Some holding companies (e.g. asset-management holdings) | | GBP | UK-incorporated companies registered in HK | | CHF | Swiss-incorporated companies registered in HK | ## Shareholders HK shareholders are returned in V2 `shareholdings[].shareholders` split by entity type: * Natural-person shareholders → `shareholdings[].shareholders.individuals[]` * Corporate shareholders → `shareholdings[].shareholders.corporations[]` Share types observed: `ORDINARY` (most common), with occasional source variant `ORDINARY SHARE`. Around half of HK fixtures have shareholder data; mutual funds, sole proprietorships, guarantee companies, and some registered non-HK companies have no shareholders. ## Representatives / directors CR entities populate V2 `representatives.individuals[]` with the role `Director`. Sole proprietorships surface the sole proprietor on the same array with a null role. ### Identity documents Identity documents are masked in HK responses (consistent with HK Identity Card / Passport privacy convention): | Type | Format | | ------------------ | ---------------------------------- | | Hong Kong ID | Letter + 3 digits + `***` (masked) | | Passport Number | Masked with `****` | | Sole-proprietor ID | Full value (not masked) | ### Nationality * HK residents: `"Hong Kong"` * Non-HK nationals: bilingual format `" "` (e.g. `"英國 UNITED KINGDOM"`, `"中國 CHINA"`) Surfaced on V2 `representatives.individuals[].nationality`. Chinese names alongside Latin names are populated for most HK-resident directors and null for most foreign nationals. Appointment / outgoing dates are populated for sole proprietorship records; an empty / sentinel date in the source means "still active" / "not departed". ## Address HK `address` is returned with the flat `fullAddress` only on Lite Profile: no component breakdown (`city`, `region`, `streetName`, etc. are null on Lite). * `country`: `"Hong Kong"`, `isoCode`: `"HK"` * `fullAddress`: flat string (e.g. `"46/F, FAR EAST FINANCE CENTRE 16 HARCOURT ROAD HONG KONG"`) * `city`, `region`, `postcode`, `streetName`, `buildingName`: null on Lite Mutual Funds have null address; sole proprietorship addresses may be in Chinese only. ## Activity / industry codes Hong Kong uses **HSIC** (Hong Kong Standard Industrial Classification, derived from ISIC Rev 4) at the registry, but activity codes are **not surfaced** for Companies Registry entities: the registry does not expose HSIC via the data interfaces Kyckr connects to. `activities[]` is empty for HK CR companies. For sole proprietorships, a single activity is mapped from the Business Registration industry field with a Chinese-language description and no code. ## Enhanced Profile: async workflow Hong Kong Enhanced Profile is ordered asynchronously, via the POST route only: registry fulfilment runs too long for a held connection, so it is not served by `GET`. **On V2:** place the order with `POST /v2/companies/{kyckrId}/enhanced`, which returns `202` with an `orderId` in the response body, then poll `GET /v2/orders/{orderId}` until `data.status` is `Success` and retrieve the profile from the order result. See the [async order pattern release note](/company-v2/developer-news/2026-08-async-order-pattern) for the full pattern. HK Lite Profile and Search are synchronous and return data immediately. ## Data Availability | Data Point | Available | | ------------------ | ------------------------------- | | Company Name | Yes (English and Chinese) | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Private and public limited only | | Share Capital | Private and public limited only | | Activities | Sole proprietorships only | | Contact Details | No | | UBOs | No | ## Registry documents Companies Registry filings are searchable for HK CR entities (production data shows 94+ distinct filing types across \~20 UAT entities). Document categories include Company Governance & Officers (FND2A, FND2B, FD2 series), Annual Returns & Accounts (FNAR1, FAR1, FNN3), Incorporation & Constitution (FNNC1, FNC1), Registered Office (FR1, FNR1), Share Capital & Charges (FNSC1, FNDB1, FNM series), Winding Up & Dissolution (FW1–FW5, FNDR1), and Non-HK Company specific filings (FNN5–FNN13, FF1–FF5). Legacy form codes (FD2, FAR1, FN3) predate the Companies Ordinance (Cap. 622) effective 2014-03-03. **Not supported for:** sole proprietorships (Business Registration) and mutual funds. ## Additional resources * [Async order pattern (V2)](/company-v2/developer-news/2026-08-async-order-pattern) * [Async order pattern (V1)](/company-v1/developer-news/2026-08-async-order-pattern) * [Normalised values guide](/documentation/useful-information/normalised-values) * [Company V2 API Reference](/company-v2/api-reference/overview) # Ireland (IE) Source: https://developer.kyckr.com/country-guides/ireland Country guide for Irish company data including registry information, identifiers, legal forms, and data availability. ## Overview **CRO** (Companies Registration Office) Official company registry of Ireland The Companies Registration Office (CRO) is the official registry for all companies and business names in Ireland. Basic company information is accessed directly from the CRO API, while enhanced data (directors, shareholders, share capital) is extracted from filed B1C Annual Return documents through automated document processing. ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------------------ | -------- | -------------------------- | | Registration Number | Numeric, variable length | `175525` | No fixed length or padding | | VAT Number | N/A | N/A | Not available from CRO | Irish company registration numbers have no fixed length or leading zeros. They are simply numeric identifiers assigned sequentially by the CRO. ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------------------- | | Search by registration number | Yes | | Search by company name | Yes (contains search) | ## Data Availability ### Companies | Data Point | LTD | DAC | ULC | PLC | CLG | External | | -------------------- | ------- | ------- | ------- | ------- | ------- | -------- | | Registration details | Yes | Yes | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | Yes | Yes | | Directors | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | | Company Secretary | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | | Shareholders | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | Limited | | Share Capital | Yes\* | Yes\* | Yes\* | Yes\* | No | No | | Group Structure | Yes\* | Yes\* | Yes\* | Yes\* | Yes\* | No | | Activity Codes | Yes\*\* | Yes\*\* | Yes\*\* | Yes\*\* | Yes\*\* | Yes\*\* | \*Extracted from B1C Annual Return filings \*\*Via separate API (not in enhanced profile response) **LTD** = Private Company Limited by Shares, **DAC** = Designated Activity Company, **ULC** = Private Unlimited Company, **PLC** = Public Limited Company, **CLG** = Company Limited by Guarantee ### Business Names | Data Point | Individual | Body Corporate | | -------------------- | ---------- | -------------- | | Registration details | Yes | Yes | | Address | Yes | Yes | | Owners | Yes\* | Yes\* | | Shareholders | No | No | | Share Capital | No | No | \*Extracted from filed documents ## Legal Forms | Code | Abbreviation | Full Name | Notes | | ---- | ------------ | --------------------------------- | ------------------------------------- | | 1153 | LTD | Private Company Limited by Shares | Most common company type | | 1150 | DAC | Designated Activity Company | Limited by shares, restricted objects | | 1157 | ULC | Private Unlimited Company | Unlimited liability | | 1155 | CLG | Company Limited by Guarantee | Non-profits, charities | | Code | Abbreviation | Full Name | Notes | | ---- | ------------ | ---------------------- | ------------------------- | | 1154 | PLC | Public Limited Company | Publicly traded companies | | Code | Type | Description | Notes | | ---- | -------------- | ------------------------------ | ------------------------------------------ | | 1130 | Individual | Business name - Individual | Sole trader trading under a different name | | 1132 | Body Corporate | Business name - Body Corporate | Company trading under a different name | | Code | Abbreviation | Full Name | Notes | | ---- | ------------ | ----------------------- | --------------------------------- | | 1177 | SE | Societas Europaea | European company form | | 1178 | External | Foreign Registered Body | Foreign company with Irish branch | | Code | Abbreviation | Full Name | Notes | | ---- | ------------ | ----------------------------------------- | ------------------- | | 1175 | ICAV | Irish Collective Asset-management Vehicle | Investment funds | | 1176 | - | Investment Company | Investment entities | ## Status Codes | Status | Description | Normalized Status | | ------------------ | ---------------------------------------- | ----------------- | | Normal | Active company | Active | | In Liquidation | Liquidation proceedings in progress | Distressed | | In Receivership | Receivership proceedings in progress | Distressed | | Strike-Off Listed | Listed for removal from register | Distressed | | Strike-Off Pending | Strike-off pending final dissolution | Distressed | | Dissolved | Company has been dissolved | Inactive | | Examinership | Court protection (similar to Chapter 11) | Distressed | ## Activity Codes Ireland uses **NACE Rev. 2** for classifying business activities. | Field | Description | Example | | ----------- | ----------------------- | ------------------------------- | | `nace_code` | NACE Rev. 2 code format | `62.01` | | `name` | Activity description | Computer programming activities | | `version` | NACE version | `2` | Activity codes are sourced via a separate CRO Open Data API and are **not included** in the main enhanced profile response. The `activities` array will be populated by a separate service. ## Address Format Irish addresses use a line-based structure from the CRO: **Example format:** ```text theme={null} SUITE 6, RINEANNA HOUSE, SHANNON FREE ZONE, CO. CLARE ``` ### Address Components | Component | Maps To | Description | | --------------- | ------------------- | ------------------------------ | | CompanyAddress1 | rawAddressLines\[0] | Primary line (building/street) | | CompanyAddress2 | rawAddressLines\[1] | Secondary line (area/locality) | | CompanyAddress3 | rawAddressLines\[2] | Region/county | | CompanyAddress4 | rawAddressLines\[3] | Additional (often empty) | | Eircode | postcode | Irish postal code | | Country | country | Always "Ireland" | Eircode (Irish postal code) is not always present, particularly for older registrations or rural addresses. ## Implementation Notes **Data Currency**: Director, secretary, and shareholder data is extracted from B1C Annual Return filings through document processing. This data reflects the **last filed annual return**, not real-time changes. Recent appointments, resignations, or share transfers may not be reflected until the next annual return is filed and processed. **Joint Shareholdings**: When shares are jointly owned, shareholder names may appear combined in the source data (e.g., "JOHN DOE & JANE DOE"). These are split into separate entries in the API response. **Foreign Registered Bodies**: Companies with type code 1178 are foreign entities with an Irish branch or presence. The `registrationType` field will be "Foreign Registered Body" and `registrationTypeDetails` will contain the country of origin. ### Representatives | Role | Description | Notes | | ------------------------- | ----------------------- | ------------------------------------ | | Director | Company director | Primary governance role | | Company Secretary | Statutory secretary | Required for all Irish companies | | Registered Business Owner | Business name owner | For business name registrations only | | Ultimate Parent | Ultimate parent company | From group structure data | | Immediate Parent | Direct parent company | From group structure data | ### Capital Types Share capital data is grouped by share class (e.g., "ORDINARY", "A ORDINARY", "PREFERENCE") with each class including: * Total nominal value * Currency (typically EUR) * Shareholdings with percentage ownership **CLG companies** (Companies Limited by Guarantee) and **External companies** (Foreign Registered Bodies) do not have share capital data, as CLGs have members rather than shareholders, and external companies' capital is registered in their home jurisdiction. # Italy (IT) Source: https://developer.kyckr.com/country-guides/italy Country guide for Italy company data including registry information, identifiers (REA, VAT, Codice Fiscale), search capabilities, and implementation notes. ## Overview **REA** (Repertorio Economico Amministrativo) Provincial trade registers maintained by Italian Chambers of Commerce (CCIA) Italian company data is sourced from the Repertorio Economico Amministrativo (REA), the provincial business register. Each Italian province has its own Chamber of Commerce (Camera di Commercio - CCIA) that maintains a register of companies within its jurisdiction. The **REA number** (province code plus registration number) is the unique primary identifier for API requests; the Codice Fiscale (national tax code) is not unique per company and must not be used for profile or filing orders. ## Company Identifiers | Identifier | Type Code | Format | Example | Notes | | --------------------------- | ----------- | --------------------- | --------------- | ------------------------------------------------------------------------------------------------------------ | | REA (Trade Register Number) | IT\_REA\_CD | 2 letters + digits | `NA0091712` | Primary identifier. Province code (e.g. NA = Naples) followed by unique registration number within that CCIA | | VAT Number | IT\_VAT\_CD | IT + 11 digits | `IT12345678912` | European VAT identifier | | Codice Fiscale (Tax Code) | IT\_TAX\_CD | 11 digits (companies) | `12345678901` | National tax identification; not unique per company | **Use REA for all profile and filing requests.** The Codice Fiscale is not unique and may be shared by related companies. Lite and Enhanced profile orders using Codice Fiscale may fail; filing search is not supported with Codice Fiscale. Always use the REA identifier from the search response. ## Search Capabilities | Search Method | Supported | Notes | | ------------------------ | --------- | ----------------------------------------------------------------------- | | Search by company name | Yes | | | Search by REA number | Yes | Use the full REA (e.g. `MI123456`) | | Search by Codice Fiscale | Yes | May return multiple entities; use REA from results for subsequent calls | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | Yes | | UBOs | No | ## Implementation Notes **Use search response data for API calls.** Use the company identifier (REA) from the search response for all Lite Profile, Enhanced Profile, and Filings Search requests. Include the registration authority code (province code) as the `RegAuth` query parameter where supported; it is optional for Italy but recommended. ### Identifier handling * The primary company identifier in API responses is the **REA number** (e.g. `MI123456`). * For secondary identifiers (Codice Fiscale, VAT), use the `otherIdentifiers` array in Lite and Enhanced profile responses, with type codes `IT_TAX_CD` and `IT_VAT_CD`. * Systems that store Italian company identifiers should store and use REA. Do not rely on Codice Fiscale for lookups or ordering. ### Province code reference REA numbers begin with a two-letter province code. Each province has its own Chamber of Commerce (CCIA). Below is the reference for province codes used in the REA format. | Province | Code | Province | Code | Province | Code | | --------------------- | ---- | ------------- | ---- | ------------- | ---- | | Agrigento | AG | Alessandria | AL | Ancona | AN | | Aosta | AO | Arezzo | AR | Ascoli Piceno | AP | | Asti | AT | Avellino | AV | Bari | BA | | Barletta-Andria-Trani | BT | Belluno | BL | Benevento | BN | | Bergamo | BG | Biella | BI | Bologna | BO | | Bolzano | BZ | Brescia | BS | Brindisi | BR | | Cagliari | CA | Caltanissetta | CL | Campobasso | CB | | Caserta | CE | Catania | CT | Catanzaro | CZ | | Chieti | CH | Como | CO | Cosenza | CS | | Cremona | CR | Crotone | KR | Cuneo | CN | | Enna | EN | Fermo | FM | Ferrara | FE | | Firenze | FI | Foggia | FG | Forlì-Cesena | FC | | Frosinone | FR | Genova | GE | Gorizia | GO | | Grosseto | GR | Imperia | IM | Isernia | IS | | Province | Code | Province | Code | Province | Code | | --------------- | ---- | --------------- | ---- | --------------- | ---- | | La Spezia | SP | L'Aquila | AQ | Latina | LT | | Lecce | LE | Lecco | LC | Livorno | LI | | Lodi | LO | Lucca | LU | Macerata | MC | | Mantova | MN | Massa-Carrara | MS | Matera | MT | | Messina | ME | Milano | MI | Modena | MO | | Monza e Brianza | MB | Napoli | NA | Novara | NO | | Nuoro | NU | Oristano | OR | Padova | PD | | Palermo | PA | Parma | PR | Pavia | PV | | Perugia | PG | Pesaro e Urbino | PU | Pescara | PE | | Piacenza | PC | Pisa | PI | Pistoia | PT | | Pordenone | PN | Potenza | PZ | Prato | PO | | Ragusa | RG | Ravenna | RA | Reggio Calabria | RC | | Reggio Emilia | RE | Rieti | RI | Rimini | RN | | Province | Code | Province | Code | Province | Code | | -------- | ---- | -------------------- | ---- | -------- | ---- | | Roma | RM | Rovigo | RO | Salerno | SA | | Sassari | SS | Savona | SV | Siena | SI | | Siracusa | SR | Sondrio | SO | Taranto | TA | | Teramo | TE | Terni | TR | Torino | TO | | Trapani | TP | Trento | TN | Treviso | TV | | Trieste | TS | Udine | UD | Varese | VA | | Venezia | VE | Verbano-Cusio-Ossola | VB | Vercelli | VC | | Verona | VR | Vibo Valentia | VV | Vicenza | VI | | Viterbo | VT | | | | | # Japan (JP) Source: https://developer.kyckr.com/country-guides/japan Country guide for Japan company data including registry information, identifiers, legal forms, bilingual name handling, and data availability. ## Overview **National Tax Agency (NTA)** corporate-number system Backed by company registrations held by the Ministry of Justice's Legal Affairs Bureaus (法務局) Japan corporate data is sourced from the National Tax Agency's corporate-number system. Search, Lite Profile, and Enhanced Profile are all supported across V1 and V2. Data quality varies by company size: listed companies expose their top 10 shareholders, and small private companies generally have no shareholder or director data. **Data quality improvements in progress.** JP responses are being refined for richer structured data and improved standard-value mappings; release notes will follow when updates ship. ## Company identifiers | Identifier | Format | Example | Notes | | ---------------- | ---------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | Corporate number | 13-digit numeric | `5010001060426` | Issued by NTA; globally unique. Consumption tax (Japan's VAT-equivalent) uses the same number — there is no separate VAT identifier. | In V2, the corporate number is the `companyNumber` and is also the registry-encoded portion of the V2 `id`. In V1, it appears as `codeField`. ## Legal form JP source data does not include a discrete legal-form field; `legalForm.normalized` is inferred from the Japanese-script company-name suffix, and `legalForm.original` carries the literal Japanese suffix where present. | Japanese suffix | `legalForm.normalized` | English equivalent | Notes | | -------------------- | ------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `株式会社` | `Private Limited Company` | Kabushiki Kaisha (K.K.) | The default Japanese corporate form; literally "stock company" by name but in practice \~99% are private. Can appear at the start (`株式会社リクルートホールディングス`) or end (`ソニーグループ株式会社`) of the name. Public / listed status is a separate axis determined by stock-exchange listing, not by the form itself. | | `合同会社` | `Private Limited Company` | Godo Kaisha (G.K.) | Japanese LLC, introduced 2006. Often used by inbound subsidiaries (e.g. Apple Japan, Google Japan). | | `有限会社` | `Private Limited Company` | Yugen Kaisha (Y.K.) | Legacy limited company. New registrations disallowed since 2006 but many existing entities remain. | | (no matching suffix) | `Other` | — | Fallback for special-purpose or imported entities. `legalForm.normalized` is never null — `Other` is used when no specific value fits, and the raw suffix remains in `legalForm.original`. | Despite 株式会社 literally translating as "stock company", it maps to `Private Limited Company` rather than `Public Limited Company`. Japan's statutory regime treats `株式会社` as a unified umbrella corporate form, with listing being a separate state — unlike China where joint-stock (`股份有限公司`) is statutorily distinct from LLC (`有限责任公司`) and only the former can be publicly traded. ## Status | Source value (Japanese) | `legalStatus.original` | `legalStatus.normalized` | | ------------------------------ | ---------------------- | ------------------------ | | `営業中` (eigyō-chū, "operating") | `Active` | `Active` | Other status values are uncommon in the observable JP sample. ## Activity / industry codes JP activities are returned as a comma-joined string of numeric industry codes (e.g. `"110,111,112,115,...,315"`) on `activities[].description`. No standardised classification scheme (NACE / NAICS) is provided for JP — `activities[].code`, `activities[].classificationScheme`, and `activities[].type` are typically null. ## Address JP `address` is returned in the standard V2 structured shape on both Lite Profile and Enhanced Profile (most other Asia-Pacific jurisdictions return only the flat `fullAddress` on Lite — JP is the exception). | V2 field | Populated | Notes | | --------------------------------- | --------------- | --------------------------------------------------- | | `fullAddress` | ✓ | E.g. `"1-9-2 Marunouchi, Chiyoda-ku, Tokyo"` | | `region` | ✓ | Prefecture, with the trailing ` Prefecture` removed | | `city` | ✓ where present | Segment ending `-shi` / containing `City` | | `municipality` | ✓ where present | Segment ending `-ku` | | `streetName`, `streetNumber` | ✓ where present | Parsed from the street segment | | `buildingName` | ✓ where present | Any building segment preceding the street segment | | `country` | `"Japan"` | | | `isoCode` | `"JP"` | | | `postcode`, `secondaryPostalCode` | — | Not surfaced for JP | Typical Latin form: `"1-9-2 Marunouchi, Chiyoda-ku, Tokyo"`. Typical Japanese form: `"東京都千代田区丸の内１丁目９番２号"`. ## Company names | V2 field | V1 field | Content | | -------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `companyName` | `nameField` | **Japanese-script** registered name (e.g. `"株式会社リクルートホールディングス"`). For JP entities the source treats the Japanese name as primary, so it occupies `companyName`. | | `englishName` | `englishNameField` | Latin-script English name (e.g. `"Recruit Holdings Co., Ltd."`) when distinct from `companyName`. | | `aliases[]` (type: `Kana`) | `aliasesField` | Phonetic Kana variant of the name where the source surfaces one. | For JP entities you should treat `englishName` (not `companyName`) as the Latin-script form for display in English-language contexts. ## Capital JP entities populate the standard V2 `capital` / `totalCapital` shape: * Currency: typically `Yen` * `totalCapital.type`: typically `Registered` — the registry reports registered-capital amount (rather than authorized or paid-in). See [Normalised values](/documentation/useful-information/normalised-values#totalcapitaltype). ## Representatives / directors JP entities expose representatives on V2 `representatives.individuals[]` with the Latin and Japanese name pair populated. Roles are free-text labels (e.g. `"President and CEO"`, `"Director"`). JP companies typically surface a single representative even for very large listed entities. ## Shareholders V2 `shareholdings[]` is populated for listed companies (and many mid-caps) but capped at the **top 10 shareholders**. For listed entities, the per-shareholder percentages typically sum to 40–60% rather than 100%. Shareholder names occasionally carry Japanese-language parentheticals such as `"(Permanent Agent: …)"` or `"(Standing Proxy: …)"` on custody-bank and foreign-institutional holders. These are returned as-is. ## Data Availability | Data Point | Available | | ------------------ | --------------------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Limited | | Status | Yes | | Representatives | Yes | | Shareholders | Listed companies only | | Share Capital | Yes | | Activities | Yes | | Contact Details | No | | UBOs | No | ## Additional resources * [Normalised values guide](/documentation/useful-information/normalised-values) * [Company V2 API Reference](/company-v2/api-reference/overview) # Jersey (JE) Source: https://developer.kyckr.com/country-guides/jersey Country guide for Jersey company data including registry information and data availability. ## Overview **Jersey Financial Service Commission (JFSC)** Official company registry of Jersey ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | No | | Shareholders | No | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Latvia (LV) Source: https://developer.kyckr.com/country-guides/latvia Country guide for Latvian company data including registry information, identifiers, legal forms, and data availability. ## Overview **UR** (Uzņēmumu reģistrs) Register of Enterprises of the Republic of Latvia Latvia's Register of Enterprises (Uzņēmumu reģistrs) is the official registry for all legal entities in Latvia. It is maintained by the Ministry of Justice and provides comprehensive company data including registration details, shareholders, and management information. ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------------------------------ | -------------------------- | --------------- | ---------------------------- | | Registration Number (Reģistrācijas numurs) | 11-digit numeric | `40103548442` | Prefix indicates entity type | | VAT Number (PVN numurs) | `LV` + registration number | `LV40103548442` | For VAT-registered companies | ### Registration Number Patterns The first two digits indicate the entity type: * **40** - Commercial companies (SIA, AS) * **50** - Non-profit organisations * **90** - State and municipal institutions ### VAT Number Details VAT data includes: * VAT number * Active status (current VAT status) * Registration date ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | SIA/AS | IK | Partnerships | Non-Profits | | -------------------- | ------ | --- | ------------ | ----------- | | Registration details | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | | Capital | Yes | No | No | No | | Shareholders | Yes | No | No | No | | Management | Yes | Yes | Yes | Yes | | Activities (NACE) | Yes | Yes | Yes | Yes | **SIA** = Limited Liability Company, **AS** = Public Limited Company, **IK** = Sole Trader ## Legal Forms | Code | Latvian | English | Notes | | ---- | ---------------------------------- | ------------------------- | ---------------------------- | | SIA | Sabiedrība ar ierobežotu atbildību | Limited Liability Company | Min capital EUR 2,800 | | AS | Akciju sabiedrība | Public Limited Company | Min capital EUR 35,000 | | PS | Pilnsabiedrība | General Partnership | Unlimited liability | | KS | Komandītsabiedrība | Limited Partnership | At least one limited partner | | Code | Latvian | English | Notes | | ---- | ------------------------ | ---------------------- | ----------------------- | | IK | Individuālais komersants | Sole Trader | Natural person business | | IND | Individuālais uzņēmums | Individual Undertaking | Legacy form | | Z/S | Zemnieku saimniecība | Farm | Agricultural business | | Code | Latvian | English | Notes | | ---- | ---------------------- | ---------------------- | ------------------ | | BDR | Biedrība | Association | Membership-based | | NOD | Nodibinājums | Foundation | Asset-based entity | | REL | Reliģiskā organizācija | Religious Organisation | Religious entities | | Code | Latvian | English | Notes | | ---- | ------------------------------ | ---------------------------- | ---------------------- | | SE | Eiropas komercsabiedrība | European Company | EU company form | | SCE | Eiropas kooperatīvā sabiedrība | European Cooperative Society | EU cooperative form | | FIL | Ārvalsts komersanta filiāle | Branch of Foreign Company | Foreign company branch | ## Status Codes | Code | Latvian | English | Normalized Status | | ---------------------------- | ------------------------ | -------------- | ----------------- | | REGISTERED | Reģistrēts | Registered | Active | | REGISTERED (IN\_LIQUIDATION) | Reģistrēts (likvidācijā) | In Liquidation | Distressed | | REMOVED | Izslēgts | Removed | Inactive | | ANNULLED | Anulēts | Annulled | Inactive | ## Activity Codes Latvia uses **NACE Rev. 2** (Saimniecisko darbību statistiskā klasifikācija) for classifying business activities. | Field | Description | Example | | ----------- | ------------------------------- | ------------------------------- | | `nace_code` | NACE Rev. 2 code format (XX.XX) | `62.01` | | `name` | Activity description in English | Computer programming activities | | `version` | NACE version | `2` | Older companies may have activity codes from NACE Rev. 1 or 1.1. These are mapped to NACE Rev. 2 where possible. ## Address Format Latvian addresses use a component-based structure. Example formats: **Standard format:** ```text theme={null} Brīvības iela 21, Rīga, LV-1010, Latvia ``` **With apartment number:** ```text theme={null} Brīvības iela 21 - 20, Rīga, LV-1010, Latvia ``` ### Address Components | Component | Maps To | Example | | ---------------------- | ------------------------ | --------------- | | Street (iela/bulvāris) | Street Name | Brīvības iela | | House number | Street Number | 21 | | Flat number | Street Number (appended) | 21 - 20 | | City (pilsēta) | City | Rīga | | Village (ciems) | City (fallback) | Mārupe | | Parish (pagasts) | Municipality | Mārupes pagasts | | Postal code | Postcode | LV-1010 | ## Implementation Notes **Currency history**: Latvia adopted the Euro (EUR) on January 1, 2014. Historical capital records may show amounts in Latvian Lats (LVL). The exchange rate was fixed at 1 EUR = 0.702804 LVL. **Founders vs Shareholders**: In Latvian company law, "founders" (dibinātāji) become shareholders (dalībnieki) upon company registration. The data returned represents current shareholdings, not founding roles. The "Founded.from/to" dates in the source data track share acquisition and disposal, not governance appointments. **Shareholder data availability**: Shareholder information is only available for commercial companies (SIA and AS). Other entity types such as sole traders (IK), partnerships, and non-profits do not have shareholder data in the registry. ### Capital Types | Code | Description | Notes | | ---- | ----------------------------------------------- | ------------------------- | | APM | Paid capital (Apmaksātais pamatkapitāls) | Most commonly returned | | REG | Registered capital (Reģistrētais pamatkapitāls) | Authorised capital amount | ### Representatives Latvian companies have officials (Valde members) who serve as the management board: | Role | Latvian | Description | | ----------------- | --------------------- | ------------------------------------ | | Board Member | Valdes loceklis | Management board member | | Board Chair | Valdes priekšsēdētājs | Chairman of the board | | Supervisory Board | Padomes loceklis | Oversight function (AS companies) | | Procurist | Prokurists | Special commercial power of attorney | # Luxembourg (LU) Source: https://developer.kyckr.com/country-guides/luxembourg Country guide for Luxembourg company data including registry information, identifiers, legal forms, and data availability. ## Overview **RCS** (Registre de Commerce et des Societes) Official company registry of Luxembourg The RCS (Registre de Commerce et des Societes) is the official business register of Luxembourg, accessed via the LBR (Luxembourg Business Registers) XML API. Unlike many jurisdictions that rely on PDF document parsing, Luxembourg provides **fully fielded structured XML data** directly from LBR, with detailed shareholding information, court ruling data, and granular status codes. Lite Profile and Search are returned synchronously. Enhanced Profile fulfilment is covered under [Enhanced Profile: async workflow](#enhanced-profile-async-workflow) below. ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ---------------------- | --------- | --------------------------------- | | Registration Number | Letter prefix + digits | `B136303` | Unique identifier assigned by RCS | | VAT Number | N/A | N/A | Not available from RCS | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Companies | Sole Traders | Partnerships | Funds | Associations | Foreign Branches | | -------------------- | --------- | ------------ | ------------ | ----- | ------------ | ---------------- | | Registration details | Yes | Yes | Yes | Yes | Yes | Yes | | Address | Yes | Yes | Yes | Yes | Yes | Yes | | Capital/Shares | Yes | No | Some | No | No | No | | Representatives | Yes | Limited | Yes | Yes | Yes | Yes | | NACE Codes | \~28% | \~28% | \~28% | \~28% | \~28% | \~28% | | Foreign Details | N/A | N/A | N/A | N/A | N/A | Yes | ## Legal Forms | Abbreviation | French | English | Notes | | ------------ | --------------------------------- | ------------------------------ | ------------------------------------- | | SA | Societe anonyme | Public Limited Company | Most common for larger companies | | SARL | Societe a responsabilite limitee | Private Limited Company | Most common company type | | SAS | Societe par actions simplifiee | Simplified Joint Stock Company | Flexible governance | | SE | Societe europeenne | European Company | EU-wide company form | | SCA | Societe en commandite par actions | Partnership Limited by Shares | Limited and general partners | | SCS | Societe en commandite simple | Limited Partnership | At least one unlimited partner | | SNC | Societe en nom collectif | General Partnership | All partners have unlimited liability | | Type | French | English | Notes | | -------------------- | ------------------------------ | -------------------- | ------------------------- | | Civil Partnership | Societe civile | Civil Partnership | Non-commercial purposes | | Cooperative | Societe cooperative | Cooperative Society | Member-owned organization | | European Cooperative | Societe cooperative europeenne | European Cooperative | EU-wide cooperative form | | Abbreviation | French | English | Notes | | ------------ | ------------------------------------------- | ---------------------------------------- | ----------------------- | | SICAV | Societe d'investissement a capital variable | Investment Company with Variable Capital | Open-ended fund | | FCP | Fonds commun de placement | Common Investment Fund | Contractual fund | | FIAR | Fonds d'investissement alternatif reserve | Reserved Alternative Investment Fund | For qualified investors | | Abbreviation | French | English | Notes | | ------------ | ----------------------------- | ---------------------- | --------------------------- | | ASBL | Association sans but lucratif | Non-profit Association | Most common non-profit form | | - | Fondation | Foundation | Charitable foundation | | - | Mutuelle | Mutual Society | Mutual benefit organization | | Type | French | English | Notes | | ---------------------- | ---------------------------------------------------------------- | ----------------------------------- | ------------------------------- | | Foreign Company Branch | Succursale d'une personne morale de droit etranger | Branch of Foreign Legal Person | Most common foreign presence | | Foreign Trader Branch | Succursale d'un commercant personne physique etabli a l'etranger | Branch of Foreign Individual Trader | Foreign sole trader | | Foreign EEIG Branch | Succursale d'un GEIE etranger | Branch of Foreign EEIG | Foreign economic interest group | | Type | French | English | Notes | | ----------------- | ---------------------------- | ----------------- | ---------------------------------- | | Individual Trader | Commercant personne physique | Individual Trader | Natural person conducting business | ## Status Codes | Status | Description | Normalized Status | | ------------------------------ | ------------------------------ | ----------------- | | (none) | Active entity | Active | | en liquidation volontaire | Voluntary liquidation | Distressed | | en liquidation judiciaire | Judicial liquidation | Distressed | | en faillite | In bankruptcy | Distressed | | radiee | Struck off | Inactive | | avec administrateur provisoire | With provisional administrator | Distressed | | en sursis de paiement | Payment suspension | Distressed | Luxembourg has 20 detailed observation codes for non-active statuses. The `statusDetailsBeta` field provides granular status information including court ruling dates, court names, and specific closure reasons. ## Activity Codes Luxembourg uses **NACE Rev. 2** for classifying business activities. | Field | Description | Example | | ------------- | -------------------- | -------- | | `code` | NACE Rev. 2 code | `96.021` | | `description` | Activity description | Coiffure | | `type` | Classification type | NACE | Only approximately 28% of Luxembourg entities have NACE codes in the registry data. The company's stated purpose (objet social) is available in `activityDeclarations`. ## Address Format Luxembourg addresses use a component-based structure: **Example format:** ```text theme={null} 10 rue du Test, 1234 Luxembourg ``` ### Address Components | Component | Maps To | Description | | -------------- | ------------------------- | --------------------------------------- | | BuildingNumber | streetNumber | Street number | | BuildingName | buildingName | Building name (if applicable) | | StreetName | streetName | Street name | | Floor | (included in fullAddress) | Floor information | | PostalCode | postcode | 4-digit postal code | | Locality | city | City/town name | | Country | country | Country name | | CountryCode | isoCode | Converted from 3-letter to 2-letter ISO | Source data uses 3-letter ISO country codes (e.g., LUX, FRA, BEL) which are converted to 2-letter codes (LU, FR, BE) in the API response. ## Implementation Notes **Fully Structured Data**: Unlike jurisdictions that rely on PDF parsing (with 1-6 hour processing delays), Luxembourg provides fully fielded XML data directly from LBR, with structured shareholding information, detailed court ruling data, and comprehensive status tracking. ### Representatives Luxembourg classifies representatives into multiple categories: | Role | French | Description | | ------------------------ | -------------------------------- | ------------------------------ | | Director/Manager | Administrateur/Gerant | Directors and managers | | Board Member | Membre | Board members | | Daily Management | Delegue a la gestion journaliere | Daily management delegates | | Permanent Representative | Representant permanent | Branch representatives | | Partner | Associe | Partners (in partnerships) | | Legal Agent | Agent legal | Liquidators, bankruptcy agents | | Management Company | Societe de gestion | Fund management company | ### Capital and Shareholding Data **Structured Shareholding**: Luxembourg provides fully fielded shareholding data including shareholder names, share counts, and share types - a significant advantage over jurisdictions where this data must be parsed from documents. Share classes commonly include: * `Parts de categorie A` / `Parts de categorie B` - Class A/B shares * `Parts sociales` - Social shares * `Actions` - Regular shares Capital type is indicated as either "Fixed" (Fixe) or "Variable". ### Foreign Entities For foreign-registered entities with a Luxembourg presence: | Field | Value | | ---------------------------- | ------------------------------- | | `registrationType` | "Foreign Registered Body" | | `registrationTypeDetails` | Source jurisdiction information | | `otherIdentifiers[].type` | "LU\_FOREIGN\_REG\_CD" | | `otherIdentifiers[].isoCode` | Source country code | | `otherIdentifiers[].value` | Foreign registration number | ## Enhanced Profile: async workflow Luxembourg Enhanced Profile is fulfilled synchronously on `GET` when the registry responds in time. A slower order is handled by the async order pattern: the request returns `202` with an `orderId` instead, and the profile is retrieved by polling `GET /v2/orders/{orderId}`. On V2, Enhanced Profile can also be ordered asynchronously from the start with `POST /v2/companies/{kyckrId}/enhanced`, polled the same way, with no held connection. See the async order pattern release notes for [V2](/company-v2/developer-news/2026-08-async-order-pattern) and [V1](/company-v1/developer-news/2026-08-async-order-pattern) for integration guidance. Lite Profile and Search remain synchronous and return data immediately. # Malaysia (MY) Source: https://developer.kyckr.com/country-guides/malaysia Country guide for Malaysia company data including registry information and data availability. ## Overview **Companies Commission of Malaysia** Official company registry of Malaysia ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ------------ | ------- | -------------------------- | | Registration Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Netherlands (NL) Source: https://developer.kyckr.com/country-guides/netherlands Country guide for Netherlands company data including registry information and data availability. ## Overview **Kamer van Koophandel** Official company registry of Netherlands ## Company Identifiers | Identifier | Format | Example | Notes | | ---------- | --------------- | ---------- | -------------------------- | | KVK-nummer | 8 digit numeral | `55114628` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # New Zealand (NZ) Source: https://developer.kyckr.com/country-guides/new-zealand Country guide for New Zealand company data including registry information and data availability. ## Overview **New Zealand Companies Register** Official company registry of New Zealand ## Company Identifiers | Identifier | Format | Example | Notes | | ---------------------- | ------------ | ------- | -------------------------- | | Source Registry Number | Alphanumeric | `N/A` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Norway (NO) Source: https://developer.kyckr.com/country-guides/norway Country guide for Norway company data including registry information and data availability. ## Overview **Brønnøysund Register Centre (BRC)** Official company registry of Norway ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | --------------- | -------------- | -------------------------- | | Organisasjonsnummer | 9 digit numeral | `977538963` | Primary company identifier | | VAT Number | NO + digits | `123456789MVA` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Singapore (SG) Source: https://developer.kyckr.com/country-guides/singapore Country guide for Singapore company data including registry information and data availability. ## Overview **Accounting and Corporate Regulatory Authority (ACRA)** Official company registry of Singapore ## Company Identifiers | Identifier | Format | Example | Notes | | -------------------------- | ------------ | ------------ | -------------------------- | | UEN (Unique Entity Number) | Aplhanumeric | `200801391M` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Spain (ES) Source: https://developer.kyckr.com/country-guides/spain Country guide for Spain company data including registry information and data availability. ## Overview **Registradores de España, Registro Mercantil Central, BORME** Official company registry of Spain ## Company Identifiers | Identifier | Format | Example | Notes | | ---------------------------------- | ------------------------------------------------------------ | ------------- | -------------------------- | | NIF (Fiscal Identification Number) | One letter followed by 8 numerals (9-character alphanumeric) | `B86007945` | Primary company identifier | | VAT Number | ES + digits | `ESX12345678` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | ------------------------------------------------ | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes - Single Shareholders only (Where available) | | Share Capital | Yes | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # Sweden (SE) Source: https://developer.kyckr.com/country-guides/sweden Country guide for Sweden company data including registry information and data availability. ## Overview **Bolagsverket** Official company registry of Sweden ## Company Identifiers | Identifier | Format | Example | Notes | | ------------------- | ---------------- | ---------------- | -------------------------- | | Organisationsnummer | 10 digit numeral | `556849-5484` | Primary company identifier | | VAT Number | SE + digits | `SE123456789123` | European VAT identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | No | | Share Capital | Yes | | UBOs | No | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update. # United Kingdom (GB) Source: https://developer.kyckr.com/country-guides/united-kingdom Country guide for United Kingdom company data including registry information and data availability. ## Overview **Companies House** Official company registry of United Kingdom ## Company Identifiers | Identifier | Format | Example | Notes | | ---------- | ---------------------- | ---------- | -------------------------- | | CRN Number | Numeric & Alphanumeric | `06388542` | Primary company identifier | ## Search Capabilities | Search Method | Supported | | ----------------------------- | --------- | | Search by registration number | Yes | | Search by company name | Yes | ## Data Availability | Data Point | Available | | ------------------ | --------- | | Company Name | Yes | | Registered Address | Yes | | Legal Form | Yes | | Registration Date | Yes | | Status | Yes | | Representatives | Yes | | Shareholders | Yes | | Share Capital | No | | UBOs | Yes | This country guide provides basic registry information and data availability. Detailed documentation including legal forms, status codes, and implementation notes will be added in a future update.