Integrates with
account required
Fortnox
Fortnox uses the shared OAuth framework with PKCE, refresh, revoke and reconnect. Customers, invoices, payments and credit invoices sync without creating duplicates. Tokens are encrypted and never shown after save.
Verification: test_verified. Connection: unknown. Credentials: none. Live E2E: no.
Fortnox OAuth application (client id/secret and tenant) is not configured.
What sslcertificates.io can do
Fortnox uses the shared OAuth framework with PKCE, refresh, revoke and reconnect. Customers, invoices, payments and credit invoices sync without creating duplicates. Tokens are encrypted and never shown after save. Capabilities: oauth, customers, invoices, payments, credit_invoices, idempotency. Authentication uses oauth2.
Required permissions
Fortnox OAuth app with invoice, customer and payment scopes. Redirect URI must match exactly.
Setup
Open Dashboard → Integrations → Fortnox. Enter the credentials described on this page. Values are encrypted at rest and never shown again. Run Test connection. Discovery runs only after authentication succeeds. Select a discovered resource. Do not paste opaque IDs unless the provider cannot enumerate them. Perform the certificate or notification action, then confirm the external system matches. Disconnect removes stored credentials and owned test resources created by sslcertificates.io.
Known limitations
Fortnox apps require a Fortnox developer portal application. Duplicate invoices are prevented with idempotency keys stored per billing document.
Official sources
Fact checked 2026-09-20. https://www.fortnox.se/developer/authorization https://api.fortnox.se/3/ Fortnox is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.
Capabilities
Connect
Fortnox is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.