These instructions are for organisations using the Finnish Service Catalogue's (FSC) search API (OUT API) utilising FSC data through the current OUT API and who are preparing to transfer from API version 11 to version 12. The instructions support assessing the workload and starting to use the new version. Separate instructions for import API (IN API) customers will be drawn up later to support the transfer.
What is going to change compared to the previous version?
This version switchover differs from previous ones in scope: the changes are significant and require more preparation and development work from the parties implementing the integration.
Impact of the changes on API users
Required actions
Use of API version 12 will require activating an API key. See instructions on [starting to use an API key] (coming later).
API users must update the logic of API calls and information processing to correspond to the new version's structure and response structures.
New API calls and response structures must be carefully tested. The test can be performed in a customer test environment (former training environment). More detailed testing instructions will be published later.
Note that during the transition period – i.e. when version 11 is still available for updating data to the FSC – two versions of the FSC’s data content, version 11 and version 12, will run simultaneously in the background. Data entry and updates will still be done in version 11, from where the data is transferred in the background to the version 12 side with a delay lasting about 1-1.5 hours.
The first API version that will be published in March 2026 is a beta version, so it may still undergo changes and clarifications before the final version.
When the FSC APIs for importing data become available for testing in autumn 2026, the aim is to establish the content of the search APIs. The aim is to no longer make significant changes to them.
Changes to search APIs
API version 12 has two different search methods
searching for an individual piece of content with an ID
data retrieval with search criteria using the /search method and its parameters
The search method will have versatile filters that can be used to retrieve data from the API with different perspectives. The search can be narrowed by organisation, organisation type, service class, keyword, target group and area information, for example.
Content returned by the search API
For data supplementing or classifying the searched content – such as service target groups, life events or keywords – only identifiers (IDs) are returned, not the entire data content.
The search API will only return published data. Archived content (service channel, organisation, service) can only be searched with separate calls. These calls will only return identifiers (IDs), not the whole content.
Different language data of the same content is returned in its own collection in the languageVersions structure. The example below includes a part of the service fields that are available as different language versions. The example does not include all data returned by the API.
"languageVersions": { "fi": { "name":"Osallistuva budjetointi", "alternativeName": "Osbu", "summary": "Tee ehdotuksia ja äänestä – ole mukana kunnan päätöksenteossa koskien taloutta ja resursseja.", "description": "Mitä palvelua tai asiaa kaipaat porvoolaisten iloksi ja hyödyksi? Ehdota ideaa ja äänestä suosikkiasi Porvoon kaupungin toteutettavaksi.", }, "sv": { "name": "Deltagande budgetering", "alternativeName": "Osbu", "summary": "Lämna förslag och rösta – delta i stadens beslutsfattande om ekonomi och resurser.", "description": "Vilken tjänst eller sak längtar du efter som kan vara till glädje och nytta för invånare i Borgå? Föreslå en idé och rösta din favorit att förverkligas i Borgå stad.", }, ...
The following more detailed compilation of the changes to the search APIs reflects the current V11 APIOpens in a new window..
Changes to search APIs by dataset
All current codelist searches from version 11 will be implemented in version 12, but the API has been restructured.
The search will have versatile filters that can be used to retrieve data from the API with different perspectives. Search filters include service (id) and serviceChannel (id).
The search will have versatile filters that can be used to retrieve data from the API with different perspectives. Search filters include the general description type, organisation and service class.
APIs in version 12 (GET) -archived content
/api/v12/general-description/archived
Decommissioned APIs in version 11 (GET) (no corresponding API for these in version 12)
The following searches will be implemented in version 12
APIs in version 12 (GET)
/api/v12/organization/content-id/{contentId}
/api/v12/organization/external-id/{externalId}
/api/v12/organization/search
/api/v12/organization/hierarchy/{contentId}
The search will have versatile filters that can be used to retrieve data from the API with different perspectives. Search filters include area data and organisation type.
APIs in version 12 (GET) -archived content
/api/v12/organization/archived
Decommissioned APIs in version 11 (GET) (no corresponding API for these in version 12)
The following searches will be implemented in version 12
APIs in version 12 (GET)
/api/v12/service/content-id/{contentId}
/api/v12/service/external-id/{externalId}
/api/v12/service/search
The search will have versatile filters that can be used to retrieve data from the API with different perspectives. Search filters include industrial class, service class, keyword, target group and organisation.
Note that the general description of the service is not included in the retrieved service data. The service data only returns the identifier (id) of the general description used, not its contents.
APIs in version 12 (GET) -archived content
/api/v12/service/archived
Decommissioned APIs in version 11 (GET) (no corresponding API for these in version 12)
/api/v11/Service/serviceWithGD/{id}
/api/v11/Service/list
/api/v11/Service/archived/list
/api/v11/Service/serviceWithGD/list
/api/v11/Service/active
/api/v11/Service/active/{id}
/api/v11/Service/serviceChannel/{serviceChannelId} (in the future, use the Service Channel search API instead of this)
Please note that the API calls in version 12 listed below are indicative. The up‑to‑date and detailed information is available in the FSC API Specification in the Customer Test Environment (former the Training Environment), see section Service channel. (link coming later)
The following searches will be implemented in version 12
APIs in version 12 (GET)
/api/v12/service-channel/content-id/{contentId}
/api/v12/service-channel/external-id/{externalId}
/api/v12/service-channel/search
The search will have versatile filters that can be used to retrieve data from the API with different perspectives. Search filters include area data, organisation and type of service channel.
APIs in version 12 (GET) -archived content
/api/v12/service-channel/archived
Decommissioned APIs in version 11 (GET) (no corresponding API for these in version 12)
The search will have filters that can be used to retrieve data from the API with different perspectives. One search filter is filtering by organisation.