Skip to main content

What is RÚZ?

The RÚZ API is the public REST API for Slovakia’s register of financial statements. It exposes the same data as registeruz.sk in JSON — accounting units, financial statements, financial reports, and annual reports — updated throughout the day as records are published.

When to use RÚZ

Use RÚZ when you need to:
  • retrieve financial statements or annual reports for a specific organization
  • access structured financial report data including table contents and attachments
  • build a pipeline that stays in sync with newly published statements
  • verify financial filings or enrich company data with accounting information
RÚZ contains financial data only. For general company information — legal form, registered address, statutory bodies, shareholders — use the RPO API instead.

API endpoints

RÚZ has three types of endpoints:
TypeWhat it does
Identifier listsReturns paginated arrays of IDs filtered by zmenene-od (changed since).
Entity detailsReturns the full record for one entity by id.
CodelistsReturns reference data — legal forms, NACE, regions, districts, municipalities.

How to start

For most integrations, the fastest path is to look up an accounting unit by IČO, then follow the links to its statements and reports.
1

Get the accounting unit ID

Call the accounting units list with a zmenene-od date and an ico filter.
Request
curl "https://www.registeruz.sk/cruz-public/api/uctovne-jednotky?zmenene-od=2000-01-01&ico=00603481"
Response
{
  "id": [336953],
  "existujeDalsieId": false
}
2

Fetch the accounting unit detail

Use the ID to get the full record — including links to all its statements and annual reports.
Request
curl "https://www.registeruz.sk/cruz-public/api/uctovna-jednotka?id=336953"
Response
{
  "id": 336953,
  "ico": "00603481",
  "nazovUJ": "Hlavné mesto Slovenskej republiky Bratislava",
  "datumZalozenia": "1991-01-01",
  "idUctovnychZavierok": [340867, 497509, 1100864],
  "idVyrocnychSprav": []
}
idUctovnychZavierok is your entry point into this unit’s financial statements.
3

Fetch a financial statement

The statement detail links to its individual financial reports.
Request
curl "https://www.registeruz.sk/cruz-public/api/uctovna-zavierka?id=340867"
Response
{
  "id": 340867,
  "idUJ": 336953,
  "obdobieOd": "2009-01",
  "obdobieDo": "2009-12",
  "typ": "Riadna",
  "idUctovnychVykazov": [686260, 680247]
}
4

Fetch a financial report

The report contains structured table data (tabulky), a cover page (titulnaStrana), and downloadable attachments (prilohy).
Request
curl "https://www.registeruz.sk/cruz-public/api/uctovny-vykaz?id=686260"

Considerations

  • All dates are YYYY-MM-DD. Report periods use YYYY-MM.
  • Fields with no value are omitted — a missing key means no value.
  • Categorical values are returned as codes. Resolve them with the Codelists.
  • The current API version is returned in the X-API-Version response header.
  • Invalid or missing parameters return 400. An unknown id returns 404.

Next steps

Identifier lists

All list endpoints, parameters, and pagination for each entity type.

Entity details

Full field reference for accounting units, statements, reports, and annual reports.

Data models

How units, statements, reports, and annual reports relate to each other.

Codelists

Legal forms, NACE, ownership types, regions, districts, and municipalities.