Fortnox connector

Beta — this connector is in beta. Functionality and resource coverage may change.

At a Glance

Difficulty: ✅STRAIGHTFORWARDSelf-Service OAuth + Free Test Databases — No Partnership or App Review Required
Authentication: OAuth 2.0Authorization Code flow with 12 scopes.
Webhooks: Virtual webhooks↗ — created and updated events for invoices, customers, suppliers, bills, ledger accounts and payments.
Partnership Required: No(Publishing in the Fortnox marketplace needs an approved integration partner agreement; the free Developer Portal and its test companies need no partnership.)
Apideck Credentials: AvailableOAuth consent shows Apideck; register your own integration only for custom branding.
Costs: No documented developer or API-access fee. Your consumers pay for their own Fortnox licences.
Sandbox Availability: Available — Access Sandbox↗(Up to 30 free test databases via the Developer Portal.)
Account Type Required: Any Fortnox account with licences for the modules in the requested scopes.
Consumer Access Level: System administrator — a restricted-role user must first be granted access covering all requested scopes.
Rate Limits: 300 requests/minute per client id and tenant, enforced as a 5-second sliding window (effectively 25 requests per 5 seconds). Exceeding it returns HTTP 429.

What are Apideck credentials?

For select connectors, Apideck has established partnerships allowing you to integrate immediately without your own partnership. When using Apideck credentials, “Apideck” appears as the requesting application during OAuth. Learn more about partnership categories →

Responsibility matrix

Task	You (Customer)	Your Consumer	Apideck
Get Developer Portal access (self-service signup, or support ticket on an existing account)	✓ (only when using your own credentials)	—	—
Create & Configure Fortnox Integration	✓ (optional — Apideck credentials available)	—	Docs provided
Add Credentials to Apideck	✓ (only when using your own credentials)	—	—
Authorize Connection (OAuth)	—	✓	Handles OAuth flow
Build via Unified API	✓	—	Maintains connector
Token Refresh	—	—	✓ Automatic
Monitor Connections	✓ Via Apideck Dashboard	✓ Can revoke anytime	Logs & alerts

Environments

Testing: Test environments are created and removed in the Fortnox Developer Portal (up to 30 at a time) and are administered like any other Fortnox company. Apideck holds a single set of Fortnox credentials, so a connection is distinguished by which company the consumer authorizes rather than by a separate sandbox key.
Production: Because credentials are shared across environments, a connection points at whichever Fortnox company the consumer authorizes. Confirm the intended company before running mutations — writes reach real bookkeeping data immediately.

🚨Important to Know About Fortnox

Journal entries are immutable once posted (correct with a balancing voucher). Listing them fetches each voucher's line items individually to fill in the response, so large result sets are slower than other list endpoints. Invoices and bills are cancelled rather than deleted; suppliers and ledger accounts are deactivated.
Attachments only auto-link for bills and vouchers. For invoices, purchase orders and offers, uploaded files land in a Fortnox inbox and a Fortnox user must attach them manually from the document view.
Credit notes cannot be created standalone — each one must be raised against an already-booked customer invoice.
Ledger accounts and journal entries are scoped to a financial year — a financialyear parameter decides which year of records comes back.
A connection left completely idle for 45+ days lapses — Fortnox refresh tokens expire on that clock, and the consumer has to reauthorize to restore it.

⚠️

2 gotchas across 2 resources

Connector-specific behaviors and limitations to be aware of

📦

17 supported resources

View field mappings, supported operations, and schema details