Suomi.fi for Service Developers
Go directly to contents.

API and architecture reform

The Digital and Population Data Services Agency is reforming the architecture of the FSC. The reform clarifies and simplifies the technical implementation of the FSC, makes the APIs easier to use and implements many development proposals received from customers over the years.

The reform does not involve changing the FSC data model except for a few additional fields.

Recordings of information events related to the architecture reform (in Finnish)Opens in a new window..

All integration customers using OUT or IN API must switch to API version 12 by spring 2027, the latest. This requires measures from all integration customers.

Timetable

01/2026

  • Version 12 OUT interface methods have been published in the Customer Test Environment (formerly known as the training environment) and will be available for testing.
  • The current data in the Customer Test Environment is available, and additional content can be created within existing organisations.
  • All different content types can be retrieved, for example, it is possible to create a complete set combining a service and its service channels.
  • Version 11 OUT and IN interfaces are still available.

03–04/2026

  • The new version 12 OUT interface methods have been published in the Production Environment as a beta. Changes may still occur in production before autumn 2026.

Autumn 2026 / To be specified

  • The new version 12 IN interface methods will be released in the Customer Test Environment and will be available for testing.
  • Version 11 OUT and IN interfaces are still available.

Autumn 2026 / To be specified

  • The final versions of the version 12 OUT interface methods will be released in the Production Environment, and no breaking changes will be made after that.
  • All data can be retrieved from the Production Environment, API-key is introduced.
  • Version 11 OUT and IN interfaces are still available.

06/2026

  • Version 12 IN interface methods are published in the Customer Test Environment and can be tested.
  • Version 11 OUT and IN interfaces are still available.

Spring 2027 / To be specified

  • Version 12 IN interface methods are published in the Production Environment. All IN interface users switch to version 12 at the same time.
  • V11 interfaces (OUT and IN) are disabled.
  • The user interface switches to the UI interfaces of the new application.

We will notify the exact date of launch in production one year beforehand and provide more specific information on the progress in each quarter.

New features planned for API version 12

The following features are initially planned for the new API (version 12):

  • An APIkey and the requirement to provide contact information will be implemented for the OUT interface. (This will facilitate communication about service disruptions and customer relationship management and enhance risk management.)
  • From now on, it will be ensured that the API and schema and other interface documentation correspond with one another and that changes are made in a coordinated manner.
  • The functionalities and error messages of the OUT and IN interfaces will correspond with each other, and error messages will be in a more understandable format.
  • In the new API, data in language versions will be returned as a separate collection, not as individual records one after another for each language, as currently.
  • The organisation of services and service channels in the user interface and API will be enabled.
  • The API’s date format will be changed to the standard format. The ISO 8601 standard will be implemented.
  • The implementation of subheadings and lists will be reformed to comply with current standards.
  • It will be made mandatory to enter names in the name fields of web addresses and email addresses if a web address has been entered, so that links can be presented in an accessible manner at the receiving end. In some cases, this has not been mandatory so far.
  • A free text field will be added for opening hours for providing additional information on opening hours, e.g. “closed in the summer” (500 characters, “Additional information” + help text +tooltip).

Updated: 22/4/2026

Are you satisfied with the content on this page?