Skip to main content

​
Choose a method

RÚZ supports local copies through list endpoints, detail endpoints, and incremental updates with zmenene-od. Use this approach when you need the full dataset in your own system or want to keep a local copy up to date.
Use caseBest choice
Fetch one entity on demandREST API
Fetch recently changed entitiesREST API
Build a full local copy of the entire registerLocal storage
Keep your local copy of the register up to dateLocal storage

​
Build your local copy

1

Start with an early date

Use an early zmenene-od value such as 2000-01-01 to retrieve the full dataset through the list endpoints.
List accounting unit IDs
curl "https://www.registeruz.sk/cruz-public/api/uctovne-jednotky?zmenene-od=2000-01-01&max-zaznamov=100"
Response
{
  "id": [336953, 412071, 598204],
  "existujeDalsieId": true
}
2

Page through all IDs

Continue paging until existujeDalsieId is false. To get the next page, repeat the same request and set pokracovat-za-id to the last returned ID.
Get the next page
curl "https://www.registeruz.sk/cruz-public/api/uctovne-jednotky?zmenene-od=2000-01-01&max-zaznamov=100&pokracovat-za-id=598204"
3

Fetch full records

For each returned ID, call the matching detail endpoint and store the full record in your database, warehouse, or other local storage.
Get accounting unit detail
curl "https://www.registeruz.sk/cruz-public/api/uctovna-jednotka?id=336953"
Response
{
  "id": 336953,
  "ico": "00603481",
  "nazovUJ": "Hlavné mesto Slovenskej republiky Bratislava",
  "idUctovnychZavierok": [340867, 497509, 1100864],
  "idVyrocnychSprav": []
}
4

Repeat for each entity type

To keep a complete local copy, repeat the same flow for accounting units, financial statements, financial reports, and annual reports.
To understand the pattern used to retrieve financial statements, financial reports, and annual reports, see the Data access guide.
5

Keep it up to date

After the initial load, store the date or timestamp from the start of the run and reuse it as zmenene-od on the next run. This returns only entities whose datumPoslednejUpravy is on or after that specific date.
  • Date only: YYYY-MM-DD
  • Date and time: YYYY-MM-DDThh:mm:ssZ
Use the timestamp form when you need sub-day precision, for example if you sync multiple times per day.
Example requests
# All changes from 2025-07-01 onward
curl "https://www.registeruz.sk/cruz-public/api/uctovne-jednotky?zmenene-od=2025-07-01"

# Changes from a specific time
curl "https://www.registeruz.sk/cruz-public/api/uctovne-jednotky?zmenene-od=2025-07-01T14:30:00Z"

​
Review limits

  • The zmenene-od is tracked per entity type
  • Any changes to a financial report do not update the accounting unit’s modified date
  • For multiple syncs per day, use the timestamp form of zmenene-od
  • If you need financial reports or annual reports, you must sync those entity lists separately.

​
See more

Pagination

Learn how to page through identifier list results.

Data access

See how accounting units, statements, reports, and annual reports link together.

Identifier lists

Review all list endpoints, filters, and response formats.

Entity details

Fetch full records for accounting units, statements, reports, and annual reports.