Start here
This guide contains public integration notes for Slovakia. 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.Slovakia 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
Slovakia uses two official government databases. For a given entity, company profile data comes from the RPO, while document retrieval uses the ORSR. The RPO aggregates data from multiple source registers and provides a unified API.- RPO (Register právnických osôb, podnikateľov a orgánov verejnej moci). The Register of Legal Entities, Entrepreneurs and Public Authorities, maintained by the Statistical Office of the Slovak Republic. This is the primary and sole structured data source for all entity types (commercial companies, sole entrepreneurs, non-profits, public entities). Accessible at rpo.statistics.sk via a free, unauthenticated public API. Provides company name, legal form, status, registered address, share capital, activity descriptions, statutory bodies (legal representatives), stakeholders (shareholders, other key persons), and statistical codes.
- ORSR (Obchodný Register Slovenskej Republiky). The Commercial Register of the Slovak Republic, maintained by the Ministry of Justice. Used exclusively for Trade Register Extract (PDF) retrieval from orsr.sk. It is not a structured data source for company attributes. Requires ORSR-specific identifiers (oddiel/vlozka/sud) obtained from RPO data.
The RPO aggregates data from multiple source registers (Commercial Register, Trade Licenses Register, etc.) and provides a unified view of legal entities in Slovakia. The ORSR specifically covers commercial companies registered in the court registry system.
Company Identifiers
Query Identifiers
Slovakia uses a single primary identifier for all entity types:Identifiers in API Response
Once you retrieve company data, theidentifiers object contains:
Slovakia does not return VAT numbers or additional identifiers in the company profile response. The ICO (registrationNumber) is the sole identifier.
Search Capabilities
Search returns internal identifiers. Both search methods return ORSR identifiers (oddiel/vlozka/sud) alongside the RPO ID, which are needed for document retrieval. These are stored internally and do not appear in the public API response.
Quirks & Gotchas
Company Status
Company status is mapped deterministically from RPO legal status codes (codelist CL010108). No AI inference is involved in status determination.Status Code Mapping
Active Statuses (3 codes)
Active Statuses (3 codes)
Insolvency Statuses (6 codes)
Insolvency Statuses (6 codes)
Closed Statuses (10 codes)
Closed Statuses (10 codes)
Unknown Statuses (1 code)
Unknown Statuses (1 code)
Status priority logic: (1) If a termination date exists, the company is always mapped to Closed regardless of the status code. (2) Otherwise, the current status code determines the status. (3) If no status information is available, the system defaults to Active.
Legal Forms
Slovakia uses the official codelist CL000056 containing 90+ legal forms. The mapping from these codes to standardized forms and ISO 20275 (ELF) codes is fully deterministic — no AI inference is involved.ISO 20275 (ELF) codes are only assigned for legal forms that have registered LEI entities in the GLEIF database. Most Slovak legal forms do not have ELF codes assigned in the current GLEIF list (v1.5).
Key Business Forms
Sole Proprietorships
Cooperatives
Non-Profit Organizations
Public Law Entities
Branch Offices
European Forms
Financial Institutions
Legal Representatives
Legal representatives are extracted from two RPO data arrays, combined and deduplicated:
The classification of a role as legal representative is fully deterministic — based on codelist codes, not AI inference.
Complete Statutory Body Role List (CL010113 — 50 roles)
Executive & Management Roles
Executive & Management Roles
Partner & Signatory Roles
Partner & Signatory Roles
Administrative & Supervisory Roles
Administrative & Supervisory Roles
Government & Religious Roles
Government & Religious Roles
Legal Representatives from Stakeholders (CL010109 — 5 codes)
These are stakeholders with signing authority, extracted from the stakeholders array:Legal representatives include both individuals and corporate entities. Role translations are standardized deterministically based on the official codelist CL010113. All statutory body entries are current records only — historical records (with
validTo set) are filtered out.Other Key Persons
Other key persons are extracted from the RPOstakeholders array using codelist CL010109. These include supervisory board members, administrators, founders, and other roles that are neither legal representatives nor shareholders.
Complete Other Key Persons Role Mapping (CL010109 — 40 codes)
Supervisory & Administrative Board Members
Supervisory & Administrative Board Members
Administrators & Trustees (Insolvency/Restructuring)
Administrators & Trustees (Insolvency/Restructuring)
Founders & Establishers
Founders & Establishers
Committee & Other Members
Committee & Other Members
Executive Roles (Historical / Former Positions)
Executive Roles (Historical / Former Positions)
Codes 4-23 (marked “historical”) are executive roles that can appear in stakeholders when they represent former/historical positions rather than current statutory authority. These same codes in CL010113 represent current legal representatives. Mapping source: CL010109.
Shareholders
Shareholders are extracted from the RPOstakeholders array using codelist CL010109 (7 shareholder codes). Both individual and corporate shareholders are supported.
Shareholder Codes (CL010109)
Ownership Data
For s.r.o. (Limited Liability Companies), ownership data is calculated from RPO deposit records by matching stakeholders to deposits by name:
Example (company with 3 shareholders, 7,500 EUR total equity):
Ownership Availability by Legal Form
Ownership data is only available for s.r.o. (Limited Liability Companies). Deposit-to-stakeholder matching uses normalized names (lowercase, academic titles removed). Currency is read from the
currency.code field. Only current deposits (where validTo is null) are used.Activity Code Mapping
Business activities are extracted from the RPO and enriched with standardized codes:AI Enrichment: When NACE codes are not available from RPO statisticalCodes, the system uses an LLM to infer NACE codes from Slovak activity descriptions (predmet podnikania). ISIC codes are always AI-inferred. Every activity item includes an
isAIInferred flag to distinguish official vs. AI-derived codes. The original Slovak activity descriptions are always preserved in activityDescription.Data Availability Matrix
Legend: Yes = Available | No = Not Available | Limited = Conditionally Available | Async = Asynchronous processing
Documents by Company Type
Commercial Companies (ORSR-registered)
Sole Entrepreneurs & Non-Profits
No documents are currently available for sole entrepreneurs and non-profits, as they are not registered in the ORSR Commercial Register.eIDAS authentication: Other documents (such as financial statements and articles of association) are available via the Slovak eGovernment portal but require eIDAS electronic identification. This is not currently supported.
Example API Responses
All examples use placeholder data. Query:POST /v2/company with { "id": "<id>", "countryCode": "SK", "dataPoints": ["company", "legalRepresentatives"] }
Closed a.s. (Joint Stock Company)
Closed a.s. (Joint Stock Company)
active: false. Shareholders and other key persons may not be available for dissolved companies, as the RPO entity endpoint may return empty arrays.Company in Insolvency (In Liquidation)
Company in Insolvency (In Liquidation)
active: false with detailed status including insolvencyStartDate and additionalInfo describing the specific proceeding type.Available Documents
Available Documents
Documents are returned when
"dataPoints": ["availableDocuments"] is requested.