# Fortnox — Accounting API: connection

> Canonical URL: https://developers.apideck.com/apis/accounting/fortnox/connection

# How to connect to Fortnox

Fortnox uses OAuth 2.0. You do not need to create API keys or copy any credentials: you connect by
signing in to Fortnox and approving access.

## Prerequisites

- An active [Fortnox account](https://www.fortnox.se) with access to the data you want to share
  (invoices, bookkeeping, suppliers, and so on).
- The Fortnox user who authorizes generally needs to be a **system administrator** on the Fortnox
  account, because activating an integration is a system-administrator action. If your role is
  restricted, a Fortnox system administrator can instead grant your user access to the modules
  covered by the permissions listed below: ask them to do that before you start.
- Fortnox notes that approving individual permissions can require the matching licence on your own
  Fortnox account. If a permission is unavailable to you, check your Fortnox subscription.

## Steps

### 1. Click Authorize in Vault

Open [Apideck Vault](https://vault.apideck.com) and find **Fortnox**. Before the first connection
the card shows the status badge **Unauthorized** and a button labelled **Authorize**. Click
**Authorize**.

### 2. Sign in to Fortnox

You are redirected to the Fortnox sign-in page. Sign in with your Fortnox credentials. If you are
already signed in to Fortnox in that browser, this step is skipped.

### 3. Approve access

Fortnox then shows its consent dialog, headed **Aktivering**. The dialog is in Swedish and lists
every permission being requested (see the table below).

- Click **Godkänn & aktivera** to approve and activate.
- **Avbryt** cancels without connecting.

![Fortnox Aktivering consent dialog listing permissions in Swedish](https://res.cloudinary.com/apideck/image/upload/v1785337291/docs/connectors/fortnox/apideck-give-conscent.png)

### 4. Confirm the connection

You are returned to Vault and the connection shows as **Connected**.

![Apideck Vault showing the Fortnox connection as Connected](https://res.cloudinary.com/apideck/image/upload/v1785337288/docs/connectors/fortnox/apideck-connection-successful.png)

## Permissions you will be asked to approve

The **Aktivering** dialog lists the permissions in Swedish. Here is what each one means:

| Shown in Fortnox (Swedish) | In English | What it covers |
| -------------------------- | ---------- | -------------- |
| Kund | Customer | Customer records |
| Leverantör | Supplier | Supplier records |
| Faktura | Invoice | Customer invoices |
| Leverantörsfaktura | Supplier Invoice | Supplier invoices (bills) |
| Bokföring | Bookkeeping | Vouchers, chart of accounts, financial years |
| Betalningar | Payments | Invoice payments |
| Artikel | Article | Articles (products) |
| Företagsinformation | Company Information | Company information |
| Order | Order | Purchase orders |
| Arkivplats | Archive | Attachments and inbox files |
| Projekt | Project | Projects (used for tracking categories) |
| Koppla filer | Connect Files | Attaching uploaded files to invoices, bills, and vouchers |

All twelve are requested together: Fortnox does not let you approve a subset.

## Notes

- The Fortnox consent dialog is only available in Swedish, even if the rest of your setup is in
  English.
- The connection is made against the Fortnox company you are signed in to. To connect a second
  company, sign in to that company in Fortnox and authorize again.
- Fortnox does not split these permissions into read-only and read-write variants, so approving
  them grants access to both read and write records in each of the areas above. Your Fortnox user
  needs to hold that access in each area for the connection to work.
- Fortnox refresh tokens are valid for 45 days and rotate each time they are used. Apideck renews
  them for you, so a connection that is used regularly stays live indefinitely and needs nothing
  from you. Only a connection that goes completely unused for 45 days or more falls out of that
  cycle and has to be authorized again.

## Troubleshooting

### The connection stopped working

Apideck refreshes your Fortnox tokens automatically, so a connection in regular use keeps working
on its own. Two things end that cycle:

- **The connection sat completely unused for 45 days or more.** Fortnox invalidates the refresh
  token at that point, so there is nothing left for Apideck to renew.
- The application owner changed their Fortnox credentials.

In both cases the fix is the same: return to Vault and authorize Fortnox again. It is the same
short flow as the first time, and reconnecting does not affect any of your Fortnox data.

### Authorization fails, or an area above is unavailable to your account

Fortnox notes that individual authorizations may impose licence requirements on your own Fortnox
account. If your subscription or your user role does not cover one of the areas above,
authorization can fail. Ask your Fortnox administrator to confirm that your subscription covers
those areas and that your user holds the necessary permissions, then authorize again.

### You clicked Avbryt by mistake

Nothing is connected and no data is shared. Go back to Vault and click **Authorize** again.

Need help? Contact [Apideck Support](https://help.apideck.com/en/articles/7774658).


[API reference](https://developers.apideck.com/apis/accounting/reference.md) · [Coverage matrix](https://developers.apideck.com/apis/accounting/coverage)