Fortnox
Service ID: fortnox
Fortnox is the leading Swedish SMB cloud accounting and ERP platform — invoicing, supplier-invoice management, bookkeeping, payments, and reporting for small and mid-sized Swedish businesses.
Beta — this connector is in beta. Functionality and resource coverage may change.
At a Glance
- Difficulty
- ⚡MODERATESelf-service developer signup, but it requires a Fortnox company with an organisation number.
- Authentication
- OAuth 2.0OAuth 2.0 (authorization code) with 12 scopes.
- Webhooks
- Virtual webhooks — created and updated events for invoices, customers, suppliers, bills, ledger accounts and payments.
- Partnership Required
- No(Optional — an unpublished integration can serve any number of customers.)
- Apideck Credentials
- AvailableAvailable — OAuth consent shows Apideck; register your own integration only for custom branding.
- Costs
- Free to build. Marketplace publishing offers commission-based or self-managed pricing.
- Sandbox Availability
- Available — Access Sandbox↗(Up to 30 free test databases via the Developer Portal.)
- Account Type Required
- Any Fortnox account with access to the data in scope.
- Consumer Access Level
- A user with access rights to the modules in the requested scopes; restricted roles need a Fortnox administrator.
- 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
- Posted vouchers (journal entries) are immutable — Fortnox supports neither update nor delete. Corrections require posting a balancing voucher instead.
- Deletes are non-destructive throughout: invoices and bills are cancelled and remain retrievable, while suppliers and ledger accounts are deactivated rather than removed.
- 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 Fortnox company with no financial year configured returns no records for either resource.
⚠️
1 gotcha across 1 resource
Connector-specific behaviors and limitations to be aware of
📦
16 supported resources
View field mappings, supported operations, and schema details