Equivalences between welfare regions and welfare associations’ service classifications and classification data in the Service Data Reserve

Open data API in a single place

Provided by Myndigheten för digitalisering och befolkningsdata

Get early access to Equivalences between welfare regions and welfare associations’ service classifications and classification data in the Service Data Reserve API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
2023.01.05
Available languages
English
Keywords
JHS 200, palvelut, Palvelutietovaranto, hyvinvointialueet
Quality scoring

Dataset description

Welfare regions and welfare associations are obliged to report their financial data to the State Treasury in accordance with the service classification of welfare regions and welfare associations (formerly JHS 200). Similarly, welfare regions must describe their services in the Service Data Repository and provide service descriptions with classification information (service category, target group and keywords). The two classifications are aligned in the data. Each service in the service classification of welfare regions and welfare associations is responsible for the PTV metadata, which consists of the service category, target group and keywords. The dataset has been separated into a separate data set from the service classification of municipalities and joint municipal authorities and the classification data of the Service Data Repository, which was produced in cooperation between the Digital and Population Data Services Agency, the Association of Finnish Local and Regional Authorities and the Municipalities Tiera. The data enables welfare regions and welfare associations to utilise their PTV data as part of financial reporting, statistics or service planning.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks