Key improvements and changes

Beta – content under developed

The following features will be implemented in the new API (version 12):

New names for APIs

In the future, OUT API will be called search API and IN API will be called import API. The purpose of this change is to ensure clear communications.

We will implement an API key in the search API (current OUT API).
A user will receive the API key after providing integration and contact information for communication purposes.

The instructions field will become required in the user interface on 3 March 2026 and in the import API (current IN API) in spring 2027.
Giving the industry-related information (specific industry or industry-independent) will be compulsory in situations where companies and organisations are specified as the service target group.
We will make it mandatory to enter a name in the name fields of web addresses and email addresses if a web address has been provided. This allows links to be displayed in an accessible way at the end that uses FSC data.

We will change the date format of the API to a standard format and implement the ISO 8601 standard.
We will add a free text field for opening hours, where additional information on opening hours – for example, “closed during the summer” – can be provided.
We will make entering service times in the user interface easier and simpler. The new search API will return service times according to the new model.
We will harmonise the types of opening hours in the user interface and the import API (current IN API), as they currently differ from each other.

We will implement a new version of the industrial classification.
We will introduce new and more detailed general description types, which will make general descriptions easier to use. New general description types: Municipal services, Wellbeing services county services, Employment area services, services of the Evangelical Lutheran Church, Other services

We are updating the implementation of subheadings and lists to comply with current standards. Going forward, formatted text fields will use a Markdown syntax. Restrictions: images and hyperlinks cannot be added.
We will increase the maximum character limits of text fields. For example, the character limit of the description field will be changed from 2,500 characters to 5,000 characters.
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.
We will enable the organisation of services and service channels in the user interface and in the API.

We will introduce an option in the search API to search for content using an external system identifier (external id, previously source id)

We will disable the automatic transfer of regional data from the service to the service channel.
During the migration, we will assign regional information to content that lacks it based on the Region in which the organisation primarily provides services, which can be found under Organisation details.

The search API of API version 12 will no longer return accessibility clauses. Going forward, the information can be retrieved directly from the City of Helsinki’s accessibility application’s API.
In the future, a link from the import API (IN API) to the accessibility application can be created, which means that import API users will no longer be required to use the FSC user interface.

Going forward, the API will return the coordinates of the service location in addition to a notification if a user has modified a coordinate.

We will ensure that, from now on, the API and schema as well as other interface documentation correspond with one another and that changes are made in a coordinated manner.
We will ensure that the functionalities of the search and import APIs will correspond in the future and that error messages will be implemented in a more intelligible format.

Updated: 24/4/2026