This section of the documentation is a work in progress. There are sections with missing or only partial documentation. Some functionality does not represent the final production version. These are common steps that all roles (Service Owner, Senders and Recipients) need to complete in order to start using the Altinn Correspondence component.
1. Get an Altinn API Key In order to use any Altinn APIs, you need a subscription key for the APIs. »
This process will be simplified through a future update in Altinn Studio.
Particularly Steps 4-6 will be performed through GUI instead of requiring direct API Calls.
1. Get started as service owner in Altinn To get started with Altinn Correspondence, 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. »
Altinn 3 Correspondence Developer guidesHow to get started subscribing to Events from Altinn 3 Correspondence, for developers
This section of the documentation is a work in progress. There are sections with missing or only partial documentation. Since Altinn Correspondence is open source, you can access our code in our public github repo and build a local docker instance to test against.
We also welcome contributions to the solution.
See the readme file at github for an introduction to Altinn 3 Correspondenec, and how to build and run it in your dev environment. »
This section of the documentation is a work in progress, and as such currently makes extensive reference to external sources. Currently the Events for Correspondence are not ready for full-scale use, due to pending changes in Altinn Events and Authorization. This documents the expected scenario, but may be subject to change. In order to use events/webhooks for a Correspondence resource, you need to setup a subscription for the given resource. »
