Service Owner System Integration

How to get started sending notifications from a Service Owner System

1. Get started as service owner in Altinn

To get started with Altinn Notifications, your enterprise must be registered as a service owner in Altinn. For a step-by-step guide, see the Get started with Altinn guide (Norwegian language only).

This step is only necessary for new enterprises that have not yet established themselves as service owners on the Altinn platform. As an existing service owner, you can proceed directly with the next steps to start using Altinn Notifications.

2. Register your Maskinporten Client with correct scopes

The scope altinn:serviceowner/notifications.create is required for clients to access the Notifications API.

All registered service owners have been delegated this scope by Digdir and should be able to find it in their list of scopes in Samarbeidsportalen.

Register your Maskinporten client(s) to authenticate with the Notifications API, assigning them this scope.

Guides on how to set up a new Maskinporten client is available in our user guide section.

3. Review policy for relevant resources in Altinn Resource Registry

Associating a notification with a resource results in the policy of said resource being used to identify the correct recipients of the notification. All intended recipients must be granted read through the policy of the resource.

A resource in this case can be both an Altinn App or a resource (tjenesteeierressurs).

For Altinn Apps, you must also ensure that the access-subject has read granted for all relevant tasks and events.

A new Altinn Resources can be registered in Altinn Studio or through an API. Please reference Altinn Resource Registry for instructions on how to create a new resource.

The policy for both Altinn Apps and other Altinn Resources can be managed in Altinn Studio. Please reference the Altinn Studio documentation on how to do this.

4. Familiarize yourself with the guidelines and best practice for sending notifications

To ensure effective communication, it is essential to strictly define what qualifies as a notification and avoid overwhelming users with too many messages.

Familiarize yourself with our guidelines to understand what notifications should and should not contain, promoting digital safety and preventing notification fatigue.

For comprehensive details, please refer to our extensive documentation.

5. Integrate against Notifications API

You are now ready to start integrating against the Notifications APIs, see the developer guides for next steps.