v1
OAS 3.0.1
Consents API
Use the Consents API to create Consent, and then use the Consent ID to invite Your Customer to onboard through the Onboarding Flow.
Client Libraries
Use the Consents API to create Consent, and then use the Consent ID to invite Your Customer to onboard through the Onboarding Flow.
Consents are the link between your Customer in your System and their connection to a System in API.1.
The Consent can exist in one of the statuses defined below:
| Status | Value | Description |
|---|---|---|
| CREATED | 0 | The Consent has this status as soon as it is created via the API. |
| ACCEPTED | 1 | The Consent has this status as soon as Your Customer successfully connects their Accounting System. |
| REVOKED | 2 | The Consent has this status if you update it, for example, by allowing Your Customer to revoke their Consent. |
| INACTIVE | 3 | The Consent has this status if the underlying connection is no longer able to connect to the Accounting System. |
The Accounting System is one of the systems that we have mapped to, as defined below.
| System Name | System Identifier |
|---|---|
| Fortnox | fortnox |
| Visma eAccounting | vismaeaccounting |
| Bjorn Lunden | bjornlunden |
| Procountor | procountor |
| Visma e‑conomic | vismaeconomic |
| Test.1 | testone |
| Visma Dinero | vismadinero |
| Billy | billy |
| File.1 | fileone |