Slovak business register API: getting company data into your application

A company autocomplete in a form, invoice details filled in from a company ID, a customer check in a CRM — all of them need register data in machine-readable form. The Slovak commercial register does not offer it that way.

The commercial register has no public API

orsr.sk is a web application built for people. Pulling data from it programmatically means parsing HTML that can change at any time and loading a server not built for it. The trade register is in a similar position.

The data of both registers is brought together in the Register of Legal Entities (RPO), kept by the Statistical Office of the Slovak Republic, which publishes it as open data: an initial full snapshot and daily change files.

Option 1: process the RPO open data yourself

• Download and load the initial snapshot — over 2.2 million records as of August 2026.
• Process the daily change files into your own database every day.
• Build a search that tolerates typos and missing diacritics — users type "slovenska sporitelna" as well as "Slovenská sporiteľňa" and expect the same result.
• Deal with defects in the data: the register contains damaged diacritics (such as "Vy´roba"), lost spaces and a 1 January 1800 placeholder date.
• If you also need VAT, the tax reliability index or e-invoicing readiness, add the Financial Administration's sources and join them on company ID and tax number.

It can be done, and for large projects it may make sense. But it is not a one-off job: sources change format, a sync occasionally fails, and someone has to watch it.

Option 2: a ready API

Apino does exactly that and serves the result over a REST API: search by name, company ID or address with typo tolerance, company detail, Slovak RPO and Czech RES in one format, register defects corrected with the original text available, VAT status including § 7a, the tax reliability index and e-invoicing readiness.

For monitoring there is a change feed: your system asks once a day for everything that changed for your companies since its last check — or we send it by webhook.

What to watch for when integrating

• Store the company ID as an eight-character string, not a number — or you lose leading zeros.
• Do not call the API on every page view; the data changes daily, so cache it.
• Check how current the data is — responses carry an X-Data-Synced-At header with the last sync time.
• Follow changes with a cursor, not offset pagination. With offsets, changes between two polls are easily missed.
• A VAT ID is not the same as being a VAT payer — if you derive VAT on an invoice from the data, use the payer status.

• Guide: A Slovak VAT ID does not make a VAT payer
• Data status: when we last synced
• Pricing