Back to homepage

Using Nemo

2.1 Using Nemo (API Integrations and Web User Interface)

NEMO maintains a list of supported versions. NEMO always supports the current production version (latest stable) and the two (2) previous versions.

Support for older versions ends after the transition period defined in EMSA's version management policy. NEMO is able to display data that was previously submitted, even if the corresponding version is no longer supported.

Compatibility

NEMO includes schema and business logic validation to ensure compliance with the applicable Message Implementation Guide (MIG).

Support for multiple versions is based on version identification at the metadata level (for example, the version number included in the message or the API request). Previously submitted data can also be viewed using older versions, but only the latest version provides full functionality.

Version Updates and Change Notifications

When Finland is informed of an upcoming MIG version update, Fintraffic will publish a notification announcing the new version and providing an estimated release schedule.

The implementation of a new MIG version is carried out in phases, and progress is communicated through the following channels:

The organization's contact email addresses can be managed in the Organization Management view.

Version information—including the version description, message structures, and API specifications—is published in Fintraffic's GitHub repository (JSON Schema, OpenAPI specifications, and MIG structures). A changelog is provided for every version, highlighting the key changes compared to the previous release.

The purpose of these notifications is to ensure that all third parties have sufficient time to prepare for the version update and to test their implementations before the new version is introduced into production.

Actions Required During a Version Update

When a version update is released, you or your organization's technical contact should take the following actions:

  • Compatibility testing – Verify that your system supports the new MIG version and produces valid data in accordance with the API specifications.
  • API changes – Review the published schemas and identify any changes to mandatory fields or message structures.
  • Service interruptions – Be aware of any planned maintenance windows or production outages related to the version update.
  • Version management – Document the version used in your development process and follow the transition timelines communicated by Fintraffic.
  • Acceptance testing – Test the complete message flow (submission, acknowledgements, and possible error messages) in the staging environment before moving to production.
Brand logos