Start here
This guide contains public integration notes for Ukraine. Use it for identifier formats, search behavior, and country-specific caveats. The live source of truth for coverage, pricing, data sources, documents, legal forms, roles, and status values is the pricing page.Ukraine coverage, pricing, and sources
Open the current catalog for supported datapoints, documents, sources, identifiers, and availability.
Country details below are preserved as integration notes. If a table or example conflicts with the live pricing page, use the pricing page as the source of truth and contact support.
Table of Contents
- Data Sources
- Company Identifiers
- Search Capabilities
- Quirks & Gotchas
- Mappings
- Data Availability
- Example API Responses
Data Sources
Ukraine uses a single official registry with three distinct datasets. For a given entity, data comes from exactly one dataset — the system routes to the correct dataset based on the identifier format and EDRPOU overlap resolution.Unified State Register (EDR / ЄДР)
The EDR (Єдиний державний реєстр юридичних осіб, фізичних осіб-підприємців та громадських формувань) — Unified State Register of Legal Entities, Individual Entrepreneurs and Public Associations — is operated by the Ministry of Justice of Ukraine and published as open data at data.gov.ua. It contains three separate datasets:- UO (Юридичні особи) — Legal entities: LLCs, JSCs, cooperatives, nonprofits, state bodies, and all other company types. Identified by EDRPOU (8-digit code, Код ЄДРПОУ).
- FOP (Фізичні особи-підприємці) — Individual entrepreneurs (sole proprietors). Identified by RECORD (numeric internal registry ID, exposed in the API with a
FOP-prefix to avoid collision with UO EDRPOU codes). - FSU (Відокремлені підрозділи іноземних юридичних осіб) — Subdivisions of foreign legal entities: representative offices and branches of foreign companies registered in Ukraine. Identified by EDRPOU (same 8-digit format as UO, but a separate dataset).
EDR data is sourced from the government open data bulk dataset published by the Ministry of Justice of Ukraine at data.gov.ua. No live API access is provided by the Ukrainian government for EDR data — the bulk dataset is the only officially available access method.
Dataset Routing
For a given identifier, the system determines the correct dataset as follows:- If the identifier starts with
FOP-(e.g.FOP-10693269), route to FOP dataset. - If the identifier is numeric only, check FSU first — this resolves the ~40 known EDRPOU codes that appear in both FSU and UO datasets (FSU takes precedence). If not found in FSU, route to UO.
Company Identifiers
Query Identifiers
Identifiers in API Response
FOP records are stored and returned with the
FOP- prefix as the id field (e.g. FOP-10693269). The identifiers.RECORD field contains the bare numeric value (10693269). Search works with both formats.Search Capabilities
Latin-script search and the companyNameTransliterations field
Ukrainian companies are registered in Cyrillic. To make Latin queries hit them, every Ukrainian company response carries a companyNameTransliterations: string[] field with the canonical Latin forms of the legal name and any commercial name. The same array is indexed in search, so a Latin query matches even when the source name is fully in Cyrillic.
Three deterministic standards are generated per company, deduped:
Notes:
- Element
[0]is the generic-folding variant. It matches what you get from thetransliterate=trueflag (see Transliteration), so the two features stay aligned. - The diacritic ISO 9 form lets you paste copies like
Hruŝovkafrom academic sources and still match. Diacritics are folded on the query side, so the index entryHruŝovkais hit by a query forHrusovkatoo. - The field is absent for Latin-script company names where the array would be empty. For non-Latin-script countries other than Ukraine, the field is currently absent (other countries follow in later releases).
- Source-language alternates (
KyivvsKiev,LvivvsLvov,OdesavsOdessa) are not derivable from transliteration. Those forms come from transliterating different source-language Cyrillic strings and are not covered today.
Quirks & Gotchas
Mappings
Company Status
Status is determined deterministically from the EDRSTAN (стан) field — no AI inference is involved.
Closure reasons for
припинено (terminated) are parsed from the free-text termination reason field:
Legal Forms
Legal forms are mapped deterministically from the EDROPF field — no AI inference is involved. The local Ukrainian name is always preserved verbatim in legalForm.localName.
Limited Liability & Corporations
Sole Proprietorships & Family Enterprises
Cooperatives
Farm Enterprises
Nonprofits & Civil Society
Government & Public Law
Branches & Representative Offices
FSU records (foreign subdivisions) always have
legalForm.localName inferred from their name prefix: names starting with “Представництво” → Representative Office; otherwise → Branch.
Other
Legal Representatives
Roles are mapped deterministically from the EDR SIGNER role text:Shareholders
- UO: Shareholders are extracted from the FOUNDERS (ЗАСНОВНИКИ) section of the EDR record. Both individual and company shareholders are supported, with nominal capital amounts in UAH.
- FOP: Always a single self-shareholder (100%) — the individual entrepreneur themselves.
sharePercentage: 100. - FSU: The foreign parent company is represented as a single company shareholder (100%). Includes
countryCode,legalName, andidentifiers.foreignCodewhen available in the source data.
Data Availability
“Partial” for UO shareholders and legal representatives reflects the EDR open data: the structured FOUNDERS and SIGNERS sections are populated for most entities but may be empty for older records (pre-1996) or for government bodies and state enterprises that do not list individual founders.