Suomi.fi Messages old APIs will be shut down on 31 December 2026 – ensure your organisation takes the necessary action

Does your organisation send Suomi.fi Messages?

If so, it is important to determine which APIs are used to send those messages. The old WS, SFTP and SMTP APIs will be discontinued on 31 December 2026.

Every service that sends Suomi.fi Messages uses an API. Your organisation must identify all services that send messages and determine whether they use any of the old APIs.

If a service uses an old API, it must be migrated to the REST API. Alternatively, the service should be decommissioned if it is no longer needed. Any required measures must be completed by the end of December 2026.

Your organisation may have one or more services connected to Suomi.fi Messages. Different services may use different APIs.

What should your organisation do now?

Review all services in your organisation that use Suomi.fi Messages and verify the following for each service:

• Whether the service is still in use
• Which API the service uses
• What actions will be taken for the service before 31.12.2026
• Whether the required measures have already been initiated
• Who is responsible for ensuring that the required measures are completed within your organisation

If the necessary measures have not yet been started, they should be initiated without delay.

Determine whether the service is still in use

In practice, each service connected to Suomi.fi Messages falls into one of the following situations.

Scenario 1: The service is actively in use

If the service is actively in use and will continue to be needed after 2026, the required measures must be completed before 31 December 2026. The measures required depend on which API the service uses.

If the service uses the WS or SFTP API

If you wish to continue using a service that relies on the WS or SFTP API, it must be migrated to the REST API and brought into production use by the end of December 2026.

If you use Suomi.fi Messages through a solution provided by a system supplier, contact your supplier as soon as possible to confirm:

• Whether the system supports the Suomi.fi Messages REST API
• When the REST API will be available in the system
• When the migration can be carried out
• What actions are required from your organisation
• Whether the migration can be completed and moved to production use by the end of December 2026

Although the technical migration itself may be relatively straightforward, a range of administrative measures will also be required from your organisation as part of the transition. For this reason, you should allow sufficient time for the migration and begin the necessary preparations as soon as possible.

If the service uses the SMTP API (email integration)

The SMTP API cannot be migrated or converted to the REST API. Use of the SMTP API will end when the old APIs are shut down on 31.12.2026. After that date, it will no longer be possible to send or receive messages through your organisation’s email system.

If your organisation has an active service that relies on the SMTP API, first determine how it is currently being used. You will then need to decide how the same business need will be addressed in the future.

Possible options include:

• Continuing to use Suomi.fi Messages by implementing a REST API integration in an existing system
• Migrating to a system or off-the-shelf solution that already supports the REST API
• Adopting another electronic communication solution used by your organisation
• Discontinuing the current service if it is no longer needed

For services using the SMTP API, this is not a technical migration to the REST API. Instead, your organisation must decide how the current use case will be handled once the SMTP API is discontinued.

If the service will be discontinued when the SMTP API is withdrawn, please notify the Digital and Population Data Services Agency in advance. Any follow-up actions and potential replacement solutions can be planned according to your organisation’s own schedule.

Scenario 2: The service is no longer actively used or is no longer needed

Not all Suomi.fi Messages services that have been enabled for your organisation may still be in use.

For example, a service may:

• Be associated with a system that has been decommissioned
• Be related to a service that is no longer provided
• Have been enabled in production but never actually used
• Have become unnecessary due to changes in your organisation’s operations
• Be a service whose closure would have no impact on your organisation’s operations

In such cases, there is no need to migrate the service to the REST API or to implement a replacement solution.

Please notify the Digital and Population Data Services Agency of any unused services so that they can be closed before the deadline. Notifications can be sent to viestit-kayttoonotot@dvv.fi.

Why should you notify the Digital and Population Data Services Agency about an unused service?

Keeping an unused service active “just in case” is generally not advisable.

Maintaining an unused service does not reduce the effort required if your organisation later decides to implement Suomi.fi Messages in a system via the REST API. The necessary deployment measures will need to be completed regardless.

Notifying the Digital and Population Data Services Agency is important because it enables unused services to be decommissioned in a controlled manner before the deadline. It also helps both your organisation and the Digital and Population Data Services Agency maintain an up-to-date understanding of the current situation.

This allows the Digital and Population Data Services Agency to focus its communications on services that still require action, while helping your organisation avoid unnecessary follow-up enquiries regarding a connection that is no longer in use or whose future status has already been determined.

If you already know that a particular connection can be discontinued, please inform the Digital and Population Data Services Agency by email at viestit-kayttoonotot@dvv.fi.

How to proceed

Review your organisation’s Suomi.fi Messages services using the following questions.

1. Is the service still actively in use?

If the service is no longer in use, notify the Digital and Population Data Services Agency so that it can be decommissioned.

If the service is still in use, continue to the next question.

2. Which API does the service use?

If the connection uses the WS or SFTP API, it must be migrated to the REST API before 31 December 2026.

If the connection uses the SMTP API, it cannot be migrated to the REST API. Determine whether the current use case will be addressed through a REST API integration in a system, another electronic communication solution, or by discontinuing the service altogether.

3. Have the required measures already been initiated within your organisation?

If the necessary changes are already under way, confirm the timetable, responsible persons, required actions and planned production deployment date. Complete the service information form and deployment checklist carefully and submit them to the Digital and Population Data Services Agency to ensure that the REST API deployment progresses according to schedule.

If the required measures have not yet been started, begin them as soon as possible.

4. Has the system supplier’s timetable been confirmed?

If you use a solution provided by a system supplier, confirm with the supplier that the required changes will be completed in time. Not all system suppliers may yet have a REST API implementation available. For this reason, it is important to confirm the timetable as early as possible.

Checklist for organisations

• We have reviewed all of our organisation’s Suomi.fi Messages connections.
• We know which connections are still in use.
• We know which API each active connection uses.
• Migration of WS and SFTP connections to the REST API has been initiated.
• A future solution has been identified for connections using the SMTP API.
• The system supplier’s timetable has been confirmed.
• We have informed the Digital and Population Data Services Agency of any connections that are no longer used or required.
• All required measures will be completed by 31 December 2026.

By following this checklist, you can ensure that the Suomi.fi Messages connections your organisation requires will continue to function after the end of 2026, and that any unnecessary connections can be decommissioned in a controlled manner before the deadline.

Please also take other API modernisation projects into account

The guidance above applies only to the APIs used by the Suomi.fi Messages service.

Other services provided by the Digital and Population Data Services Agency are also undergoing API modernisation projects, some of which may likewise involve a migration to REST APIs. Please ensure that you follow the correct measures and implementation schedules for each service separately.

For example, information about the deployment schedule for the maintenance APIs of the Population Information System is available on the Digital and Population Data Services Agency website (dvv.fi, in finnish)Opens in a new window..