If you are using FSC data in a customer-facing service, such as a website, we recommend caching the data in your own system. Caching makes your service more reliable and reduces dependence on real-time API calls.
Update your data cache regularly, such as every 24 hours, by retrieving only the data that has changed.
Instructions for using the search API
Study the search API calls and their usage in the environment-specific API documentation:
Example instructions for the most common use cases
Retrieves data from the FSC that has changed after your previous export.
You can retrieve:
published content that has been changed on or after a specified timestamp. Use the publishedAtOrAfter parameter, e.g. 2024-03-20T13:45:30Z.
archived content that was archived on or after a specified timestamp. Use the archivedAtOrAfter parameter.
The following example retrieves changed organisation data. You can use a similar method to retrieve services, service channels, service collections and general descriptions that have changed.
Up-to-date connection data can be retrieved by using the search API call for all connection data. You can also retrieve new and updated connection data with the publishedAtOrAfter parameter, similarly to the example on organisations.
Details of organisations
1. Retrieve new and updated organisations
GET /api/v12/organization/search?page=1&pageSize=100&publishedAtOrAfter=2026-03-31T12%253A29%253A51.540Z
page=1 indicates how many pages you are retrieving, pageSize=100 indicates how many results are returned on one page, and publishedAtOrAfter contains the restricting timestamp
You will receive the details of the organisations as a reply (items table).
Repeat for as long as the API returns search results (the items table is not blank).
Add the new organisations to your own database and update the details of the changed organisations.
2. Retrieve archived organisations
GET api/v12/organization/archived?page=1&pageSize=100&archivedAtOrAfter=2026-01-30T12%3A29%3A51.540Z
You will receive a list of the organisations’ content-ids as a reply.
If accessibility information is available for a service location, the FSC search API will return the ID required to retrieve them in the accessibilityRegisterServicePointId field.
Retrieve the accessibility information directly through the API provided by the accessibility application of the City of Helsinki.
Read the current instructions: TPR interfacesOpens in a new window. (in Finnish) Replace the {accessibilityRegisterServicePointId} of your following calls with the accessibilityRegisterServicePointId data returned by the FSC.
