Advanced search
Advanced search
Advanced

RFS Open API, version 2.5

Table of contents:

Introduction

Public RFS Open API provides the ability to obtain data publicly available (i.e. everything that is provided by the portal registeruz.sk) in a format suitable for processing, in particular in JSON format. Conceptual Data Model API is shown in the following figure:

Open API JSON model
Image 1: Data model shows relations between objects used by API services.

Services can be split into three groups:

  • lists of identifiers - used to download identifiers for various data types, these identifiers are subsequently used to access the details
  • detail of the entity - contains detailed attributes of the entity for given identifier
  • classifications- lists of classification data the source of which is ŠÚSR (Statistical Office of the Slovak Republic)

Data actualization

Data are accessible via API at same moment like via GUI. Data in RFS are updated, received respectively, throughout the day and are accessible immediately at the moment of receipt/update. Services can return different data throughout the day (request can return more data later in the day, but in case of correct regular incremental requests are always available all received/updated data until selected date).

Method of providing data

  • All dates are text strings formatted in compliance with ISO 8601 as YYYY-MM-DD.
  • Periods stated on the title page of the statement are text strings formatted in compliance with ISO 8601 as YYYY-MM.
  • All cross references to classification values must be set by using the code of the item (for more information see Classifications).
  • Attributes with no value (null) are not included in the response. This is true for simple attributes as well as for lists, e.g. if an accounting entity does not include idUctovnychZavierok, it means, that there are no registered financial statements for that financial entity (or they are not publicly available, see FAQ).
  • If the syntax request is incorrect (missing or incorrectly formatted parameters) an HTTP 400 Bad Request response will be returned. The body of the response may include an explanation.
  • If the requested data does not exist (non-existent id) HTTP 404 Not Found will be returned.
  • Data datumPoslednejUpravy (used for querrying zmenene-od)refers only to a particular entity and not its logical relations. Example: If a new financial statement is added, but the accounting entity has not changed, this is reflected in the list of changed financial statements (new ID will be added), but not in the list of accounting entities changed since that date. This is in no way affected by the fact that in the detail of the accounting entity given id of the financial statement will be added to the list of its financial statements (this is not considered to be a change of the attribute of an accounting entity). This applies to all relationships at the object level shown in the figure above.
  • For lists, in which zmenene-od is entered,all the data will be acquired (sequentially page by page in the order of ID), which have been modified either on a given day (in case of used format yyyy-MM-dd), or given date and time (in case of used format yyyy-MM-dd'T'hh:mm:ssZ) respectively, and any day afterward (i.e. inclusive value zmenene-od).
  • API version appears in the HTTP header "X-API-Version" (eg. "X-API-Version: 1.2"), API version attribute was omitted from JSON.

The recommended way of sequential download

  • During the first download, it is possible to obtain all data by entering old enough date in the parameter value zmenene-od, for example: zmenene-od=2000-01-01
    It is important to write down the date on which the receiving the data was initiated (which can take several days) let’s say 2014-02-14
  • For repeated data download, it is sufficient to receive only the records in which something has changed. It can therefore be requested with the parameter zmenene-od=2014-02-14 (example from the previous bullet). Again, it is important to write down the date when the updates were downloaded (eg. 2014-03-08). This date will be used in the next update (refresh) of the data. For repeated data download multiple times in a day, is possible to use parameter zmenene-od=2014-02-18T12:59:59Z in case, that you have written down exact date and time of last start of this download. In this case will be only records from this date and time returned.
  • It is the downloading mechanism implementation decision, whether it will record a common date of the beginning of data download for all the lists or separate date per each list (separately for accounting entities, and separately for the financial statements, etc.).
  • If you are interested in a small set of data on a periodic basis, the simplest way is to periodically make a request about the accounting entities based to their id (keep the record of the frequently used ones, they never change) and go deep through their data (financial statements, statements, annual reports) and find any changes.

Deleting data in RFS

  • Data in RFS are typically only added but should not be deleted, but for technical reasons data can be deleted.
  • ID of given entity appears in the list of changed records.
  • After accessing the details of the entity, entity detail is returned with the abbreviated list of attributes: id, datumPoslednejUpravy a stav 
    {"id":316853,"datumPoslednejUpravy":"2013-08-21","stav":"ZMAZANÉ"}
  • In case the entity is deleted, always all related sub-data are deleted as well (e.g. when deleting financial statement, all financial reports are deleted as well). Identifiers of sub-data can not be accessed through detail of the deleted entity but they appear in the list of changed entities of a given type (in our example in the list of financial statements).
  • Deleting the financial report will not cause the setting of the date of the financial statement change, similarly deleting financial statement will not set the accounting entity change, despite the fact that the deleted identifiers will be missing in the details of these otherwise unchanged data.
  • Deleting attachments of the statement causes setting the change of in the accounting statements in the detail of which the deleted annex will be missing. If trying to download deleted attachment directly, the system will return an HTTP 404 error.
  • Templates of the statements are never deleted.
  • In exceptional cases, it may happen that the data will disappear from the public part (and therefore from Open API as well) without a trace. These cases can not be fully eliminated, but there is an effort to minimize their occurrence.

Other notes

  • Attachments of reports are made available outside of API through URL that matches the actual web application, namely /domain/financialreport/attachment/id-attachment. In case the report contains any attachments, list of attachment IDs is part of report detail (/api/uctovny-vykaz).
  • Within the application, it is possible to download the PDF form of structured data using the following URL: /domain/financialreport/pdf/id-report. This is a generated PDF that is, in terms of data content, identical to the actual detail of the report acquired through the API. From the API point of view this URL is unimportant. (We mention it only to emphasize that for the consumer of API there is no need to download generated PDF and expecting to get some additional data. It is merely a visualization of data in PDF format.)

Services for the list of identifiers

Services are designed for inkremental requests of lists of new/updated entities by types (accounting entities, financial statements, annual reports, financial reports). These are designed for clients, to no need of repeated access/check all identifiers (after initial download), but download only new/updated ones after download date of the last inkrement.

URL of the services for lists of identifiers:

  • /api/uctovne-jednotky
  • /api/uctovne-zavierky
  • /api/uctovne-vykazy
  • /api/vyrocne-spravy

Parameters List:

All services related to the list of identifiers have the following common parameters:

  • zmenene-od - mandatory parameter, that returns a list of identifiers that have been modified on a given date or later. Valid formats are:
    • yyyy-MM-dd - returns a list of identifiers of entities that have been modified on given date or later. For example zmemene-od=2020-12-31.
    • yyyy-MM-dd'T'hh:mm:ssZ - returns a list of identifiers of entities that have been modified on given date and time or later. Intended to incremental downloading of modified entities repeatedly throughout the day. If the client saves the start date and time of the last download, it can incrementally download the identifiers of changed entities from that point on. For example zmemene-od=2020-12-31T23:59:59Z resp. zmemene-od=2020-12-31T23:59:59+0000.
  • pokracovat-za-id - optional parameter, that returns a list of identifiers that are larger than the specified identifier.
  • max-zaznamov - optional parameter, it returns the number of records, up to 10000. The preset number is 1000.

The service for showing list of identifiers of accounting entities /api/uctovne-jednotky is the only one that allows use of the following parameters:

  • ico - optional parameter
  • dic - optional parameter
  • pravna-forma - optional parameter, code of legal form (see Classifications)
Input example:

Format of the answer:

The answer format is the same for all requests about lists of identifiers.

  • id - list of identifiers that meet specified criteria. If exists no identifier belong to input parameter, empty list is returned. The identifier is an integer with a maximum length of ten digits.
  • existujeDalsieId - boolean flag - true, if there is at least one corresponding identifier for input parameter, which is not in returned list of identifiers and its value is greater than the last identifier returned in current list.

The service returns required (or default) number of records in the order of id, and next "page" of the list can be acquired by repeating of request using the pokracovat-za-id=xxx, where xxx is the last identifier of the previously retrieved list until list of identifiers is not empty. If number of remaining identifiers is needed, use one of services for the number of remaining identifiers with parameter pokracovat-za-id=xxx where xxx is the last identifier of the previously retrieved list.

Output example: 
{"id":[1001,7148,8221,8222,8223,9911,12700], "existujeDalsieId": true}

Services for the number of remaining identifiers

Services returns number of remaining identifiers for various types of entities. These can be used for time estimate of acquiring lists of identifiers, or for fine tuning of this requests. Services are not necessary for use of services for the list of identifiers.

URL of the services for number of remaining identifiers

  • /api/zostavajuce-id/uctovne-jednotky
  • /api/zostavajuce-id/uctovne-zavierky
  • /api/zostavajuce-id/uctovne-vykazy
  • /api/zostavajuce-id/vyrocne-spravy

Parameters List:

All services have the same parameters like related services for the list of identifiers (except max-zaznamov). It's because of use the same configuration of parameters of request as for list of identifiers and with use of the last returned identifier acquire number of all remaining identifiers of entity.

All services related to the number of remaining identifiers have the following common parameters:

  • zmenene-od - mandatory parameter, that returns a number of remaining identifiers that have been modified on a given date or later. Valid formats are:
    • yyyy-MM-dd - returns a number of identifiers of entities that have been modified on given date or later. For example zmemene-od=2020-12-31.
    • yyyy-MM-dd'T'hh:mm:ssZ - returns a list of identifiers of entities that have been modified on given date and time or later. For example zmemene-od=2020-12-31T23:59:59Z resp. zmemene-od=2020-12-31T23:59:59+0000.
  • pokracovat-za-id - optional parameter, that returns a number of remaining identifiers that are larger than the specified identifier.

The service for showing number of remaining identifiers of accounting entities /api/zostavajuce-id/uctovne-jednotky is the only one that allows use of the following parameters:

  • ico - optional parameter
  • dic - optional parameter
  • pravna-forma - optional parameter, code of legal form (see Classifications)
Input example:

Format of the answer:

The answer format is the same for all requests about number of remaining identifiers.

  • pocetZostavajucichId - number of remaining identifiers that also meet the specified criteria. Typically represents number of entity identifiers, which have yet to be acquired by services for the list of identifiers. Integer of virtually unlimited size.
Output example: 
{"pocetZostavajucichId":10}

Services for details

These services return the details of a single entity, all of which have only one mandatory parameter:

  • id - the identifier of the entity (accounting entity, financial statement, ...). The identifier is an integer with a maximum of ten digits.

Accounting Entity

Url: /api/uctovna-jednotka

Input example: /api/uctovna-jednotka?id=336953

Output format: (Some attributes may not be included in the response)
  • id - identifier of the accounting entity, maximum ten digits integer
  • ico - Company Identification Number (CIN) of accounting entity, eight characters string
  • dic - Tax Identification Number (TIN) of accounting entity, ten characters string
  • sid - SID of accounting entity, maximum five characters string
  • nazovUJ - title of accounting entity, string with a maximum length of 500 characters
  • mesto - address of accounting entity, the city, the string with a maximum length of 200 characters
  • ulica - address of accounting entity, street and number, string with a maximum length of 200 characters
  • psc - address of accounting entity, zip code, a string with a maximum length of 10 characters
  • datumZalozenia - date of establishment of the accounting entity, format YYYY-MM-DD
  • datumZrusenia - date of cancellation of the accounting entity, format YYYY-MM-DD
  • pravnaForma - code of the legal form (see Classifications)see Classifications), a string with a maximum length of 100 characters
  • skNace - SK NACE classification code (see Classifications), a string with a maximum length of 100 characters
  • velkostOrganizacie - code for category of the organization size (see Classifications), textový reťazec s maximálnou dĺžkou 100 znakov
  • druhVlastnictva - code for category of the organization ownership (see Classifications), a string with a maximum length of 100 characters
  • kraj - registerred office of accounting entity, region code (see Classifications), a string with a maximum length of 100 characters
  • okres - registerred office of accounting entity, district code (see Classifications), a string with a maximum length of 100 characters
  • sidlo - registerred office of accounting entity, code of village or city (see Classifications), a string with a maximum length of 100 characters
  • konsolidovana - boolean flag - true if the unit has at least one consolidated financial statement
  • idUctovnychZavierok - a list of identifiers of all associated financial statements, the identifier is the maximum ten digit integer
    • code
  • idVyrocnychSprav - a list of identifiers of all related annual reports, identifier is the maximum ten digit integer
  • zdrojDat - code of the source of data used (see Data Sources), a string with a maximum length of 30 characters
  • datumPoslednejUpravy - date of last modification that affects accounting entity API representation (e.g. changed date of establishment of the accounting entity, making accounting entity available in API (without accounting entity data change), ...), format YYYY-MM-DD
Output example: 
{
 "id":336953,"skNace":"84110","konsolidovana":true,"ico":"00603481","dic":"2020372596",
 "nazovUJ":"Hlavné mesto Slovenskej republiky Bratislava", "mesto":"Bratislava - mestská časť Staré Mesto",
 "ulica":"Primaciálne námestie 1","psc":"81499","datumPoslednejUpravy":"2012-11-14", "datumZalozenia":"1991-01-01",
 "pravnaForma":"801","velkostOrganizacie":"25","druhVlastnictva":"5","kraj":"1","okres":"SK0101", "sidlo":"528595",
 "zdrojDat":"ŠÚSR","idUctovnychZavierok":[340867,497509,1100864,726508,727630,1296603]
}

Financial Statement

Url: /api/uctovna-zavierka

Input example: /api/uctovna-zavierka?id=340867

Output format: (Some attributes may not be included in the response)
  • id - identifier of financial statement, ten digit number
  • obdobieOd - financial Statements for the year - “starting from date”, format YYYY-MM
  • obdobieDo - financial Statements for the year - “until date”, format YYYY-MM
  • datumPodania - the date of submission of the financial statement (eg. registration at FRSR) format YYYY-MM-DD
  • datumZostavenia - the date on which the financial statement was prepared, the format YYYY-MM-DD
  • datumSchvalenia -the date on which the financial statement was approved, the format YYYY-MM-DD
  • datumZostaveniaK - the date of the financial statement assembly, the format YYYY-MM-DD
  • datumPrilozeniaSpravyAuditora - the date of auditor's report attachment, the format YYYY-MM-DD
  • nazovFondu - the name of the fund, under which the financial statement was submitted (in case of fund’s financial statement), the string with a maximum length of 500 characters
  • leiKod - LEI (Legal Entity Identifier) code , under which the financial statement was submitted, the string with a length of 20 characters
  • idUJ - identifier of the accounting entity, maximum of ten digits integer
  • konsolidovana - boolean flag - true in the case of consolidated financial statement
  • konsolidovanaZavierkaUstrednejStatnejSpravy - boolean flag - true in the case of consolidated accounts of central government
  • suhrnnaUctovnaZavierkaVerejnejSpravy - boolean flag - true in the case of summary financial statement of public administration
  • typ - "Riadna” (“Ordinary"), “Mimoriadna” ("Extraordinary"), “Priebežná” ("Interim") or "Kombinovaná" ("Combined") (ordinary and extraordinary)
  • idUctovnychVykazov - a list of identifiers of all related financial reports, the identifier is the maximum ten digit integer
  • zdrojDat - code of the source of the data (see Data sources), a string with a maximum length of 30 characters
  • datumPoslednejUpravy - date of last modification that affects financial statement API representation (e.g. changed date on which the financial statement was prepared, making financial statement available in API (without financial statement data change), ...), format YYYY-MM-DD
Output example: 
{
 "id":340867,"datumPoslednejUpravy":"2011-12-08","zdrojDat":"FRSR","obdobieOd":"2009-01", "obdobieDo":"2009-12",
 "idUJ":336953,"konsolidovana":false,"typ":"Riadna","idUctovnychVykazov":[686260,680247]
}

Financial Report

Url: /api/uctovny-vykaz

Input example: /api/uctovny-vykaz?id=686260

Output format: (Some attributes may not be included in the response)
  • id - identifier of the financial report, maximum ten digits integer
  • idUctovnejZavierky - the identifier of the financial statement to which the report is related (if report is related with annual report, this element is not included), maximum ten digits integer
  • idVyrocnejSpravy - the identifier of the annual report to which the report is related (if report is related with financial statement, this element is not included), maximum ten digits integer
  • idSablony - identifier of corresponding template, maximum ten digits integer
  • mena - the currency of the statement (SKK, ...), maximum nine character text string
  • kodDanovehoUradu - code of tax office, maximum three character string
  • pristupnostDat - data availability is based on legislative or procedural reasons and affects availability of finanancial reports data (attributes obsah and prilohy) for each financial report. Values:
    • "Verejné" - all financial report data publicly available
    • "Verejné prílohy" - only attachments of the financial reports publicly available (structured data in attribute obsah not publicly available). Typically, these are financial reports for which structured data quality can not be guaranteed (e.g. historical data for 2009 - 2012). These financial reports should by contain at least one attachment, but exception may occur (mostly financial reports for 2009 - 2012).
    • "Neverejné" - no financial report data publicly available. These are financial reports stored in non-public part of RFS for legislative reasons.
  • prilohy - field of related attachments, the attachment is an object made of attributes:
    • id - the identifier of the attachment, maximum ten digits integer - it is possible to download the attachment using /domain/financialreport/attachment/id-attachment
    • meno - name of attachment, a string with a maximum length of 100 characters
    • mimeType - the attachment type, a string with a maximum length of 80 characters
    • velkostPrilohy - attachment size, integer of virtually unlimited size
    • pocetStran - the number of pages of the report, maximum six-digit integer
    • digest - hash of the attachment contents, SHA-256 algorithm is used, a string with a length of 64 characters
    • jazyk - language of the attachment, maximum three character string
  • obsah - data content of the statement consists of:
    • titulnaStrana - title page of the report (cover page) with the identification data. All data from the title page are gathered from external systems. In the RFS system the data are stored as text strings without limitation of length. In case of the times and dates, text strings of of the format YYYY-MM, respectively. YYYY-MM-DD is guarranteed.
      The object titulnaStrana is composed of the following attributes:
      • nazovUctovnejJednotky - the name of an accounting entity
      • ico - CIN of an accounting entity
      • dic - TIN of an accounting entity
      • sid - SID of an accounting entity
      • adresa - address of an accounting entity, object consisting of attributes:
        • ulica - street
        • cislo - number
        • psc - number
        • mesto - city
      • miestoPodnikania - business address of an entity of object, composed of attributes
        • ulica - street
        • cislo - number
        • psc - number
        • mesto - city
      • pravnaForma - code of legal form (see Classifications)
      • skNace - code of SK NACE classification (see Classifications)
      • typZavierky - "Riadna” (“Ordinary"), “Mimoriadna” ("Extraordinary") or "Kombinovaná" ("Combined") (ordinary and extraordinary)
      • konsolidovana - boolean flag - true in the case of consolidated financial statement
      • konsolidovanaZavierkaUstrednejStatnejSpravy - boolean flag - true in the case of consolidated financial statement of central government
      • suhrnnaUctovnaZavierkaVerejnejSpravy - boolean flag - true in the case of summary financial statement of public administration
      • typUctovnejJednotky - "malá" ("small"), "veľká" ("large")
      • oznacenieObchodnehoRegistra - Commercial Register specification and the registration number of the company
      • nazovSpravcovskehoFondu - the name of the administration company / fund (filled-in only in case of the financial statements of the fund)
      • leiKod - LEI code (filled-in only in case of the financial statements of the fund)
      • obdobieOd - financial report for the period starting, the format YYYY-MM
      • obdobieDo - financial report for the period ending, in format YYYY-MM
      • predchadzajuceObdobieOd - financial report for the previous period starting, the format YYYY-MM
      • predchadzajuceObdobieDo - financial report for the previous period ending, the format YYYY-MM
      • datumVyplnenia - date of completion of the financial statement, format YYYY-MM-DD
      • datumSchvalenia - the date of approval of the financial statement, the format YYYY-MM-DD
      • datumZostavenia - the date of preparation of financial statement, format YYYY-MM-DD
      • code">datumZostaveniaKcodeiv> - the date preparation of financial statement at (a date), format YYYY-MM-DD
      • datumPrilozeniaSpravyAuditora - date of auditor's report attachment, format YYYY-MM-DD
    • tabulky - list of tables containing data:
      • nazov - name of the table (such as "Balance Sheet") the object where key is the localization and the value is a string with maximum length of 100 characters
      • data - numerical data in tables of the statement, read line by line from left to right, the numerical data is a string of length up to 30 digits and 4 decimals. Decimal separator is a dot.
  • zdrojDat - code of the data source (see Data sources), a string with a maximum length of 30 characters
  • datumPoslednejUpravy - date of last modification that affects financial report API representation (e.g. add an attachment, making financial report available in API (without financial report data change), ...), format YYYY-MM-DD

In the cover page for the data types ENTITY_LEGAL_FORM, ENTITY_SK_NACE, ENTITY_ORGANIZATION_SIZE and ENTITY_OWNERSHIP values are represented by codes from the Classifications and the data types ENTITY_DOMICILE, ENTITY_COUNTY, ENTITY_DISTRICT values are codes from Locations classification. Services for both Classifications are discussed in the documentation below.

Output example: 
{
"id":686260,
"datumPoslednejUpravy":"2013-07-31",
"zdrojDat":"DataCentrum",
"idUctovnejZavierky":340867,
"idSablony":98,
"obsah":{
  "titulnaStrana":{
     "ico":"00603481",
     "obdobieOd":"2009-01",
     "obdobieDo":"2009-12",
     "nazovUctovnejJednotky":"Hlavné mesto Slovenskej republiky Bratislava",
     "adresa":{
        "ulica":"Primaciálne námestie 1",
        "psc":"94131",
        "mesto":"Bratislava - mestská časť Staré Mesto"
     },
     "typZavierky":"Riadna"
  },
  "tabulky":[
     {
        "nazov":"Náklady",
        "data":[
           "4248919",
           "17058",
//... kratene
           "145116521",
           "216375501"
        ]
     },
     {
        "nazov":"Výnosy",
        "data":[
           "12222937",
           "425982",
//... kratene
           "130597430",
           "51660772"
        ]
     }
  ]
},
"prilohy":[
  {
     "id":214469,
     "digest":"5c4db0a4b4af7126fe1a48aa3f51fe8deae8be9d7f8b0526f92bb4a55eee9dc2",
     "mimeType":"image/tiff",
     "meno":"POD101_2022773060_IR_2009_617_2010_501653.TIF",
     "velkostPrilohy":203499,
     "pocetStran":4
  }
],
}

Annual Report

Url: /api/vyrocna-sprava

Input example: /api/vyrocna-sprava?id=2613005

Output format: (Some attributes may not be included in the response)
  • id - the identifier of the annual report, maximum ten digits integer
  • nazovUJ - the name of the accounting entity at the time of submitting the annual report, string with a maximum length of 500 characters
  • typ - "Ročná finančná správa" ("Annual financial report"), "Individuálna výročná správa" ("Individual annual report"), "Konsolidovaná výročná správa" ("Consolidated annual report") or "Súhrnná výročná správa SR" ("Summary Annual Report of SR")
  • nazovFondu - the name of the fund of the submitted annual report (if it is an annual report of the fund) a string with a maximum length of 500 characters
  • leiKod - LEI code under which the annual report was submitted, string with a length of 20 characters
  • obdobieOd - annual report for the year - starting from date, format YYYY-MM
  • obdobieDo - annual report for the year - until date, format YYYY-MM
  • datumPodania - the date of submission of the annual report (eg. registration on FRSR) format YYYY-MM-DD
  • datumZostaveniaK - the date of the annual report assembly, the format YYYY-MM-DD
  • pristupnostDat - data availability is based on legislative or procedural reasons and affects availability of annual reports data (attribute prilohy) for each annual report. Values:
    • "Verejné" - all annual report attachments publicly available
    • "Neverejné" - no annual report attachments publicly available. These are annual reports stored in non-public part of RFS for legislative reasons.
  • prilohy - field of related attachments consisting of attributes:
    • id - the identifier of the attachment, maximum ten digit integer
    • meno - name of the attachment, a string with a maximum length of 100 characters
    • mimeType - the attachment type, string with a maximum length of 80 character
    • velkostPrilohy - attachment size, number value
    • digest - hash of the contents of the attachment, SHA-256 algorithm used, a string with a maximum length of 64 characters
  • idUctovnychVykazov - a list of identifiers of all related financial reports, the identifier is the maximum ten digit integer
  • idUJ - identifier of the accounting entity, maximum ten digits integer
  • zdrojDat - code of the data source (see Data sources)
  • datumPoslednejUpravy - date of last modification that affects annual report API representation (e.g. changed date of submission of the annual report, making annual report available in API (without annual report data change), ...), format YYYY-MM-DD
Output example: 
{
 "id":316853,"nazovUJ":"Continental Matador Rubber, s.r.o.","datumPoslednejUpravy":"2013-08-21","zdrojDat":"FRSR",
 "obdobieOd":"2011-01","obdobieDo":"2011-12","datumPodania":"2013-01-01","idUJ":635004,"typ":"Individuálna výročná správa","rok":2011,
 "prilohy":[{"id":217769,"digest":"5c4db0a4b4af7126fe1a48aa3f51fe8deae8be9d7f8b0526f92bb4a55eee9dc2","mimeType":"image/tiff",
 "meno":"POD201_4045546120_IR_2011_617_2013_538566.TIF","velkostPrilohy":296519}]
}

Services for the financial report templates

Template of the financial report provided through the API defines the content of the table section of the financial report. Data from the cover sheet are contained in the financial report along with the definition of its meaning.

Some templates do not correspond with the official reports and serve as a “pseudo-templates” for storage of financial reports that can not be classified in other way. An example is the "report", that contains only one attachment with a complete financial statement in accordance with IFRS standards. Such "reports" do not have a structured data available.

Financial report template

Url: /api/sablona

This service returns structure of a single report template, and have one mandatory parameter:

  • id - the identifier of the report template. The identifier is an integer with a maximum of ten digits.

Input example: /api/sablona?id=7

Output format: (Some attributes may not be included in the response)
  • id - identifier of financial report template, maximum ten digits integer
  • nazov - name of the template, string with a maximum length of 100 characters
  • nariadenieMF - specification of the Ministry of Finance regulation, in which the report was referred to, a text string with maximum length of 100 characters
  • platneOd - the validity of the template from the date, format YYYY-MM-DD
  • platneDo - the validity of the template until the date, (can be omitted and the statement can be updated with the same name), the format YYYY-MM-DD
  • tabulky - a list of data consisting of:
    • nazov - name of table, the object where key is the localization and the value is a string
    • hlavicka - header of the table consists of data:
      • text - description of the column, the object where key is the localization and the value is a string
      • riadok - row - position in the header, integer
      • stlpec - column - position in the header, integer
      • sirkaStlpca - number of columns, number
      • vyskaRiadku - number of rows, number
    • riadky - row of the table consisting of:
      • oznacenie - typically special code of the line
      • cisloRiadku - serial number of the line
      • text - a description of the line, the object where key is the localization and the value is a string
Output example: 
{
"id":7,
"nazov":"Úč FO 1-01",
"nariadenieMF":"MF/27076/1/2007-74/1",
"platneOd":"2009-01-01",
"tabulky":[
  {
     "nazov":{
        "sk":"Príjmy"
     },
     "hlavicka":[
        {
           "text":{
              "sk":"Príjmy"
           },
           "riadok":1,
           "stlpec":1,
           "sirkaStlpca":1,
           "vyskaRiadku":1
        },
//... kratene
     ],
     "riadky":[
        {
           "text":{
              "sk":"Predaj tovaru"
           },
           "cisloRiadku":1
        },
//... kratene
     ]
  },
  {
     "nazov":{
        "sk":"Výdavky"
     },
     "hlavicka":[
        {
           "text":{
              "sk":"Výdavky"
           },
           "riadok":1,
           "stlpec":1,
           "sirkaStlpca":1,
           "vyskaRiadku":1
        },
//... kratene
     ],
     "riadky":[
        {
           "text":{
              "sk":"Nákup materiálu"
           },
           "cisloRiadku":5
        },
//... kratene
     ]
  }
],
}

Report templates of financial reports

Url: /api/sablony

This service returns field of all existing report templates of financial reports in RFS in time of request. Service do not require any parameters. This service should be used for the bulk update of all report templates, before start of downloading details of financial reports for example, in order not to have to constantly check the existence of templates to which the details of the financial statements refer. Every report template returned in the field have a same structure as defined above in service for financial report template by its identifier.

Output example: 
{
"sablony":[
    {
        "id":7,
        "nazov":"Úč FO 1-01",
        "nariadenieMF":"MF/27076/1/2007-74/1",
        "platneOd":"2009-01-01"
    },
    {
        //... kratene
    }
]
}

Services for the classifications

Classifications are based on data available at ŠÚSR (Statistics office of Slovak Republic) on this address (valid as of May 2020). Classifications displays always in full, services do not require any parameters. The outcome is an array of objects containing following attributes:

  • kod - code of the item (assigned by ŠÚSR), a string with a maximum length of 100 characters
  • nazov - title of the item (a short version of the title registered at ŠÚSR) in all RFS supported languages
  • nadradenaLokacia (only for locations - municipalities, districts) - code of parent location, a string with a maximum length of 100 characters

URL of classification services:

Output example: 

{"klasifikacie":[
    {"nazov":{"en":"Not ascertained yet","sk":"Zatiaľ nezistené"},"kod":"0"},{"nazov":{"en":"International with preponderance of public sector","sk":"Medzinárodné s prevažujúcim verejným sektorom"},"kod":"1"},
    {"nazov":{"en":"Private inland","sk":"Súkromné tuzemské"},"kod":"2"},{"nazov":{"en":"Cooperative-owned","sk":"Družstevné"},"kod":"3"},
    {"nazov":{"en":"State-owned","sk":"Štátne"},"kod":"4"},{"nazov":{"en":"Municipality-owned","sk":"Vlastníctvo územnej samosprávy"},"kod":"5"},
    {"nazov":{"en":"Ownership of associations, political parties and churches","sk":"Vlastníctvo združení, politických strán a cirkví"},"kod":"6"},
    {"nazov":{"en":"Foreign","sk":"Zahraničné"},"kod":"7"},{"nazov":{"en":"International with preponderance of private sector","sk":"Medzinárodné s prevažujúcim súkromným sektorom"},"kod":"8"},
    {"nazov":{"en":"Mixed (a combination of 1 through 8)","sk":"Zmiešané (kombinácia 1 až 8)"},"kod":"9"}
]}

URL services for locations:

  • /api/kraje - corresponds to ŠÚSR classification 0023/RSUJ3
  • /api/okresy - corresponds to ŠÚSR classification 0024/LSUJ1
  • /api/sidla - corresponds to ŠÚSR classification 0025/LSUJ2
Output example: 

{"lokacie":[
    {"nazov":{"en":"Region of Bratislava","sk":"Bratislavský kraj"},"kod":"1"},{"nazov":{"en":"Region of Trnava","sk":"Trnavský kraj"},"kod":"2"},
    {"nazov":{"en":"Region of Trenčín","sk":"Trenčiansky kraj"},"kod":"3"},{"nazov":{"en":"Region of Nitra","sk":"Nitriansky kraj"},"kod":"4"},
    {"nazov":{"en":"Region of Žilina","sk":"Žilinský kraj"},"kod":"5"},{"nazov":{"en":"Reg.of Banská Bystrica","sk":"Banskobystrický kraj"},"kod":"6"},
    {"nazov":{"en":"Region of Prešov","sk":"Prešovský kraj"},"kod":"7"},{"nazov":{"en":"Region of Košice","sk":"Košický kraj"},"kod":"8"},
    {"nazov":{"en":"Abroad","sk":"Zahraničie"},"kod":"9"}
]}

Data Sources

For the data sources, there is no service, it is the following fixed list (after the hyphen is just an explanation which is not part of the value in JSON response)

  • SUSR - Statistical Office of the Slovak Republic
  • SP - State Treasury system
  • DC - DataCentrum
  • FRSR - The Financial Directorate of the Slovak Republic
  • JUS - Uniform Accounting State System
  • OVSR - Commercial Bulletin of the Slovak Republic
  • CKS - Central Consolidation System
  • SAM - Budgetary Information System for Municipal Authorities

License

licence_icon
All data provided by RFS Open API are published under CC0 license.

API Version changelog

  • 1.1 (01/03/2014)
    • Added support for deleted entities. Because of bug fixes (accounting statements etc. can be duplicated), may cause deletion of data.
      For more see Mazanie údajov v RÚZ
    • Version of API appears in the HTTP header "X-API-Version" (eg. "X-API-Version: 1.2"), verziaApi attribute was omitted from JSON.
  • 1.2 (05/06/2014)
    • o Added support for consolidated financial statements for state and public administration as a boolean attributes of statement konsolidovanaZavierkaUstrednejStatnejSpravy and suhrnnaUctovnaZavierkaVerejnejSpravy. These two attributes and attribute konsolidovana are mutually exclusive and only one of them may be present.
    • Changing the name of the cover sheet to title page of the financial statement and simplification of its representation.
  • 1.3 (18/05/2015)
    • o Added support for other attributes of the title page of financial statement namely typUctovnejJednotky, oznacenieObchodnehoRegistra, nazovSpravcovskehoFondu and leiKod.
    • Added new data source - Budgetary Information System for Municipal Authorities.
  • 1.4 (13/08/2015)
    • Removal of the support for the attribute krajina in the accounting entity.
    • New attribute nazovFondu added into the detail of the financial statement.
  • 1.5 (13/10/2015)
    • New type of annual report added - "Súhrnná výročná správa SR".
  • 1.6 (16/12/2015)
    • New attribute datumZostaveniaK added into the detail of the financial statement.
    • In the attributes of the detail of the financial statement obdobieOd and obdobieDo the day is no longer used.
    • In the attributes of the detail of the annual report obdobieOd and obdobieDo the day is no longer used.
  • 1.7 (15/02/2016)
    • Added new attribute leiKod into the detail of the financial statement.
    • Added new attribute leiKod into the detail of the annual report.
    • Added new attribute nazovFondu into the detail of the annual report.
  • 1.8 (09/06/2016)
    • Attribute jazyk moved within the detail of financial report to the set of attributes in the field prílohy.
  • 1.9 (23/02/2017)
    • Data sources in attribute zdrojDat within the detail of the accounting entity, the detail of the financial statement, the detail of the financial report, the detail of the annual report, are provided only in abreviated form, see Data sources.
    • Added new attribute idUctovnychVykazov into detail of the annual report. Annual reports can contain additional financial reports (Notification of Approval, Auditor's report, Report of selected data)
    • Added new attribute datumZostaveniaK into detail of the annual report.
  • 2.0 (09/05/2017)
    • Added new attribute idVyrocnejSpravy into detail of the financial report. In case of financial report is related with annual report, detail of financial report contains idVyrocnejSpravy and contains idUctovnejZavierky if this financial resport is related with financial statement.
  • 2.1 (30/08/2018)
    • Added support for displaying information on annual reports, financial statements and financial reports stored in the non-public part of the Registry of Financial Statements (RFS). For these, only the information about their presence in the RFS, respectively their general data is available, because their own data must not be disclosed in the RFS due to legislative reasons.

      There is no change on incremental download of lists of modified entities, so as part of the services fro the list of identifiers (see Services for the list of identifiers) will be possible to download a list of modified entities from a defined date (inclusive) through the
      zmenene-od
      attribute, which is evaluated by the
      datumPoslednejUpravy
      attribute. In addition, in detail of financial report and annual report is added new attribute pristupnostDat.
    • Changed attribute nazov in financial report detail (in attribute tabulky). Attribute nazov is now an object, where key is the localization and the value is a string.
  • 2.2 (12/05/2020)
    • Attribute nadradenaLokacia, in services for locations part, changed from number to string with a maximum length of 100 characters
  • 2.3 (02/03/2021)
  • 2.4 (15/03/2021)
    • Added new attribute existujeDalsieId to responses of all services for the list of identifiers. This is used for quick check, if quering another identifiers make sense, without use of of separate service for the number of remaining identifiers.
    • Attribute id in responses of all services for the list of identifiers will always be in final JSON ie. even if it is an empty list. If no matching identifier is found based on the input data, the id attribute was not in JSON so far.
    • Added new service to download whole list of report templates of financial reports in single batch - Report templates of financial reports.
    • Added new format "yyyy-MM-dd'T'hh:mm:ssZ" in which is possible write parameter zmenene-od in services for the lists of identifiers and number of remaining identifiers. Can be used to simpler incremental downloading of entities data during the day.
  • 2.5 (31.5.2024)
    • Removed attributes nazovUJ, ico a dic from response of service for financial statement detail..
    • Added the status Neverejná to those entities that are moved to the non-public part (§ 23, paragraph 8 of Act No. 431/2002 Coll. on Accounting).

May we, please, use cookies?🍪

To ensure the proper functioning of the website and to improve our services, we use cookies. Please confirm your consent or set your preferences.

Necessary cookies
Always active
They ensure the basic usability of the website. The website cannot function properly without these cookies. These cookies do not store any information about you.
Analytical cookies
They help to understand the behavior of website visitors and thereby contribute to a better functionality of this website.
Accept all
Decline
More information
Privacy statement