NOTE: Before you start to migrate, the integration needs to be set to use OAuth 2.0 flow.
POST https://apps.fortnox.se/oauth-v1/migrateHeaders example
ClientId: 8VurtMGDTeAI
ClientSecret: yFKwme8LEQ
Credentials: OFZ1cnRNR0RUZUFJOnlGS3dtZThMRVE=
Credentials is the Base64 encoding of ClientId and Client-Secret, separated with a colon.
Content-type: application/x-www-form-urlencoded
Authorization: Basic {Credentials}Body example
The body shall be sent by using the "application/x-www-form-urlencoded" format, with a character encoding of UTF-8.
access_token (required) - The legacy token you want to migrate to JWT
access_token={legacy-token}{
"access_token": "xyz...",
"refresh_token": "a7302e6b-b1cb-4508-b884-cf9abd9a51de",
"scope": "companyinformation",
"expires_in": 3600,
"token_type": "bearer"
}Status: 404
Message: Access-token not found
Status: 401
Message: Invalid authorization
Status: 400
Message: Could not create JWT
Status: 403
Message: Not allowed to create JWT for given access-token
See our comprehensive documentation regarding the Fortnox API.
Approximately half a million customers are waiting for your integration at our Integrations page.