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.
- 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 prefill 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. Prefill mode serves data from the register’s daily open-data
export, while verification mode queries the UR API live 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:
Legal Entity Identifier (LEI)
GLEIF is the supplementary data source for this identifier.company.identifiers.lei is optional. It is returned when the Latvian registration number (registrationNumber) matches exactly one LEI through a GLEIF registration or validation reference.
The Legal Entity Identifier has 20 uppercase alphanumeric characters, ending in two check digits.
Coverage varies by entity. An absent lei does not prove that the company has no LEI. Lapsed, retired or merged LEIs may be returned; annulled LEIs are excluded.
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).
Active companies only
Search can return companies that are no longer active. Each result carries the register’s status, soactiveOnly=true removes the inactive ones. A registered company in liquidation remains active until removal and can appear in both name and identifier searches.
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.Liquidation alone does not establish insolvency, so no
insolvencyStartDate is inferred from a liquidation date. statusDetails.additionalInfo retains recorded liquidation grounds where available.For a removed company, closureDate is the register’s removal date. A cancelled liquidation does not establish the cause of a later removal.Legal Forms
The 18 known verification forms below have deterministic native names, English translations and broad standardized categories. An ISO 20275 reference is included where the native form has an exact match. Prefill covers all 54 form codes observed in the register’s public data, including historical forms. See the pricing page for the complete catalogue. The standardized category is a broad grouping. Native legal form and ISO 20275 reference preserve more specific distinctions; an additional-liability company is classified as Other. The Legal basis column links the act that creates or defines each form, at its official publication. The pricing-page catalogue carries the same links for every verified form and role in alegalBasisBeta list, one entry per act. This field is in beta: its name and shape may change before it becomes legalBasis. A form whose register label does not identify a single act has no link.
Commercial Companies
Sole Entrepreneurs & Individual Entities
Non-Profits & Civil Society
European & International Entities
Other Entity Types
Unrecognized forms retain the register’s wording. Verification may enrich their translation and category. A missing ISO 20275 reference does not imply that the native form is unknown.
Legal Representatives
Legal representatives come from actual registered representation rights, executive-body appointments and known authorised offices. Structured position and governing-body fields take precedence over free-text titles. A supervisory-body record is an other key person unless the register separately records representation rights. The supervisory board’s specific statutory capacity in disputes with executive-board members does not itself establish ordinary commercial signing authority.Representation Mode
Both modes retain structured source conditions insigningPowers.localText. Pure INDIVIDUALLY means sole signing. WITH_AT_LEAST, WITH_ALL, WITH_CHAIR, WITH_DEPUTY_CHAIR and joint-only combinations mean joint signing. Conditions mixing individual and joint operation remain unspecified rather than being reduced to one mode. Missing rights remain unspecified.
A recorded withAtLeast quantity is preserved in the source condition. Its basis as co-signers or total signers has not been verified, so it is not presented as minimumSignatories.
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
Unknown and context-dependent positions
Unknown and context-dependent positions
The public officer feed currently contains 15 nonblank position codes and 10 governing-body codes. Titles are preserved from the source. Unknown titles do not establish representation through substring matching. Standalone
MANAGER, MEMBER, ESTATE_TRUSTEE and other context-dependent appointments need actual registered rights or an executive-body context. Otherwise the named officer is retained as an other key person. Oversight coverage in the open-data feed is sparse; verification has the richer register record.Procurists (Commercial Law s.34–35) are available in verification mode and returned as individuals. Recorded representation and immovable-property conditions are retained in
signingPowers.localText. representationMode is provided only when the recorded terms establish sole or joint operation. Both individual and corporate legal representatives are supported.Other Key Persons
Other key persons (supervisory board members, auditors) are drawn from the same register officers, classified by role, position or governing body.Other Key Person Roles (Deterministic Mapping)
A supervisory-body appointment without a specific title is classified as Supervisory Board Member while retaining its source label. A known chair title remains visible. Both individual and corporate other key persons are supported.
Shareholders
Shareholders are drawn from the Enterprise Register’s recorded members for capital companies and partnerships (SIA, AS, PS, KS, cooperatives). Sole entrepreneurs (IK, individual undertakings, farms) and non-profits (associations, foundations, religious organizations, political parties) have no share capital: ashareholders request for them returns an explicit not-applicable response and is not billed. In prefill mode, shareholders come from the register’s open data, which covers SIA and AS members only.
Extraction Logic
The register also records voting rights, joint ownership, ownership start dates, representatives of minors or legal entities, and paid-up amounts. These are not returned.
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
Prefill mode is served from the register’s daily open data, with about a
24-hour lag. It does not include birth dates, supervisory board members,
procurists, or activity codes. UBOs are available in verification mode only.
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. The removal date is retained when available. A coarse removal or reorganization status has closure cause Unknown; an explicit liquidation record can establish Liquidation.Company in Liquidation
Company in Liquidation
Likvidācijas procesā (Pending Dissolution) and remains active until removal. Liquidation does not itself establish insolvency. Registered liquidators are returned as legal representatives with their recorded signing conditions.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: