Translations of this page:

Catalogue of public administration services

The VS Service Catalogue is part of the Register of Rights and Obligations (RPP) and as such contains a set of data on VS services, actions and their service channels.

The VS Service Catalogue can be viewed in two ways - as a client application publishing data for clients and as a clerical application used to collect and edit data.

The VS Service Catalogue will be continuously developed to fulfil the following functions:

  • information - to provide an overview of existing VS services and how they are processed,
  • publication - to provide the data necessary for the correct display of VS services on portals (sorting, categories, you might also be interested in, etc.),
  • managing - enabled the management of the delivery of VS services (setting a plan for digitisation, information on the responsibility for the service will facilitate the coordination of the transition to a digital service, etc.),
  • automation - enabled the collection of data necessary for automation.

Represents a function (activity) of an authority that is knowingly provided by a particular OVM to a particular recipient of a service under the relevant legislation in such a way that it delivers a perceived value to the recipient, whether in the form of a benefit or the fulfilment of a legal obligation. Only VS services during which there is an interaction between the OVM and the client or vice versa are recorded, not an interaction between the OVM and the OVM. A VS service can also be seen as the achievement of a right or fulfilment of an obligation of the client that cannot be fulfilled except through an interaction or series of interactions between the client and the OVM. A service is distinguished according to whether it is initiated by the client or performed ex officio. Each service consists of at least one act.

When recording VS services, sequentially review the legislation and identify VS services using the definitional features listed below. For each VS service, describe its attributes according to the methodology

The publication process consists of two main steps:

  1. Registration of services in ZR RPP
  2. Filling in the detailed service description

The public part of the catalogue is available on the public administration portal here

Approved detailed descriptions are automatically published from RPP via the RPP API (GraphQL, Azure). The GraphQL endpoint of RPP runs here:

Options for working with service catalog data

  1. Working with XLS of individual agendas
  2. API to service catalogue
    • no access restrictions for now, in the future an API key will be required and the address will change
    • primary purpose is for detailed service descriptions = texts to sites according to the detailed descriptions methodology -
    • daily updates
    • advantages
      • Standardized API
      • GraphQL (output definition already at query)
    • disadvantages
      • only service data (no actions and service channels)
      • no documentation yet
  3. open data
Enter your comment: