Start here
This guide contains public integration notes for Latvia. 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.Latvia 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.
Data Sources
Latvia uses two complementary data sources: the real-time UR API for full company profiles and documents, and open data for fast batch-deduplicated search and onboarding.- Uzņēmumu reģistrs (UR) API. The Enterprise Register of the Republic of Latvia, maintained by the Register of Enterprises. This is the source for full company profiles with AI enrichment: activity codes (NACE/ISIC), legal representatives with standardized roles, supervisory board, shareholders with ownership details, UBOs with control types, and document access. Accessible at ur.gov.lv. The API uses OAuth2 with JWT client assertion (RFC 7523) for authentication.
- Latvia Open Data (data.gov.lv). CC0-licensed datasets from the Enterprise Register, updated daily. Covers ~480K entities across 7 CSV files: company register, officers, members (SIA shareholders), stockholders (AS shareholders), beneficial owners, equity capitals, and areas of activity. Used for fast search and the onboarding profile datapoint.
Dual-source model. Search queries hit the fast search index first for
fast results from batch data, then fall back to the UR API for supplementary
results. The onboarding profile serves data directly from batch staging
tables, while the full company profile uses the UR API for AI-enriched data.
Company Identifiers
Query Identifiers
Identifiers in API Response
Once you retrieve company data, theidentifiers object contains all available identifiers for that entity:
Search Capabilities
Search architecture: Search queries run all sources in parallel. Fast-index sources return first from synchronized open data. The UR API sources (by ID, by VAT, by name) provide supplementary results. Results are merged with matchType priority (ID > exact name > partial match).
Quirks & Gotchas
Company Status
Company status is determined deterministically from the UR API schema. No AI inference is involved. The API returns a finite enum of statuses with optional status details and liquidation records.When a company has
REGISTERED status with IN_LIQUIDATION details, the
insolvencyStartDate is derived from the most recent active liquidation
record’s startedOn date. The groundsForLiquidation field provides
additional context (e.g., shareholder decision). For REMOVED companies, the
closureDate comes from the removedOn field.Legal Forms
Latvia uses a finite set of 18 legal form types from the UR API. The mapping is fully deterministic, and no AI inference is used for legal form identification. ISO 20275 codes are derived via AI enrichment after the deterministic mapping.Commercial Companies
Sole Entrepreneurs & Individual Entities
Non-Profits & Civil Society
European & International Entities
Other Entity Types
Unknown legal forms not matching the 18 known types fall back to using the raw
API value as
localName without English translation. ISO 20275 codes are
always derived via AI enrichment, not from a static lookup table.Legal Representatives
Legal representatives are extracted from the UR APIofficers array. The classification of a role as legal representative vs. other key person uses a hybrid approach: known roles are mapped deterministically, while unknown free-text roles fall back to AI enrichment. Role determination uses three signals from the API: the free-text role field, the enum position field, and the enum governingBody field.
Representation Mode
The UR API provides structured representation authority data in therightsOfRepresentation field, which is mapped to representationMode:
{ mode: "sole" }: Can sign alone (type: "INDIVIDUAL"){ mode: "joint", minimumSignatories: N }: Must sign jointly (type: "COLLECTIVE"with minimum count){ mode: "joint" }: Joint signing required, count unspecifiednull: No representation rights data provided by UR
Representation mode is populated from structured UR API data when available. Not all companies have this field populated in the registry.
Legal Representative Roles (Deterministic Mapping)
By Role Name (free-text Latvian)
By Role Name (free-text Latvian)
By Position Enum (from UR API)
By Position Enum (from UR API)
By Governing Body
By Governing Body
Pattern-Based Fallbacks
Pattern-Based Fallbacks
When the free-text role does not match an exact mapping, pattern matching is used to determine if the role is a legal representative:
If a pattern matches but the exact role is not known, the role is flagged for AI enrichment to provide accurate English translation and standardization.
Procurists are mapped separately from the
procurations array (not the
officers array). Each procuration may contain multiple procurists, and the
system also extracts rightsOfRepresentation (e.g., INDIVIDUALLY,
WITH_AT_LEAST, JOINTLY) and rightsOnImmovableProperty when available. Both
individual and corporate legal representatives are supported.Other Key Persons
Other key persons (supervisory board members, auditors) are extracted from the sameofficers array, classified by role, position, or governing body.
Other Key Person Roles (Deterministic Mapping)
Officers with
governingBody = SUPERVISORY_BOARD but no explicit role or
position are defaulted to “Supervisory Board Member” and flagged for AI
verification. Both individual and corporate other key persons are supported.Shareholders
Shareholders are extracted from the UR APImembers array for commercial companies only (SIA, AS). Non-profits, foundations, sole traders, and farms do not provide shareholder data.
Extraction Logic
Both individual and corporate shareholders are supported. Corporate
shareholders include registration number and country when available. Foreign
corporate shareholders are identified with their home country registration
details.
Activity Code Mapping
Latvia uses NACE (Nomenclature of Economic Activities) codes from the Enterprise Register. The system maps activity codes across two levels, with special handling for older NACE revisions:NACE Revision Handling
Non-profit entities (associations, foundations) may have activity area codes
(
areasOfActivityOfAssociationsFoundations) instead of NACE codes. These use
a separate classification (e.g., HEALTH_AND_DISEASE_PREVENTION, EDUCATION,
CULTURE, SPORT) and are processed via AI enrichment to derive NACE/ISIC
equivalents.Data Availability Matrix
Legend: ✅ Available | ❌ Not Available | ⚠️ Conditionally Available | Async = Asynchronous processing
Documents by Company Type
Latvia provides comprehensive document access through the Enterprise Register (Uzņēmumu reģistrs). Documents are sourced from two channels: the UR website (for CTRE) and the UR API (for all other documents).Always Available
From UR API (Public Documents)
Articles of Association
Articles of Association
Financial Statements
Financial Statements
Registration & Incorporation
Registration & Incorporation
Beneficial Owners
Beneficial Owners
Corporate Governance
Corporate Governance
Legal & Administrative
Legal & Administrative
Foreign Entities & Other
Foreign Entities & Other
Insolvency Proceedings
Insolvency Proceedings
Insolvency proceeding documents are retrieved from a separate API endpoint and enriched via AI parsing to extract the proceeding type, status, and descriptive English names.
Annual Report Deduplication: The UR API may return multiple versions of
the same annual report (including DUF structured data files). The system
automatically filters out DUF files and deduplicates by year+format, keeping
only the most recent version.
Example API Responses
All examples use placeholder data. Query:POST /v2/company with { "id": "<id>", "countryCode": "LV", "dataPoints": ["company", "legalRepresentatives"] }
Closed Company (Removed from Register)
Closed Company (Removed from Register)
active: false with a closureDate and closureReason. Different removal reasons (reorganization, liquidation, administrative dissolution) are mapped to specific closure reasons.Company in Liquidation
Company in Liquidation
Likvidācijas procesā (Under Insolvency Proceeding) with the liquidation start date. The liquidator replaces board members as the legal representative.Association (Non-profit)
Association (Non-profit)
UBO Response (dedicated datapoint)
UBO Response (dedicated datapoint)
Query with Note: UBOs are available directly from the Enterprise Register, no separate retrieve required. The
"dataPoints": ["ultimateBeneficialOwners"]:natureOfControl field uses known enum values: AS_MEMBER, AS_FOUNDATION_FOUNDER, AS_OWNER, ON_GROUNDS_OF_PROPERTY_RIGHT, AS_SHAREHOLDER. Includes share and voting rights percentages when declared.Available Documents (company example)
Available Documents (company example)
Documents are returned when
"dataPoints": ["availableDocuments"] is requested.All entity types: