Visma eAccounting
Service ID: visma-eaccounting
Visma eAccounting is a Nordic SaaS accounting and invoicing platform for small businesses in Sweden, Norway, and the Netherlands.
At a Glance
- Difficulty
- ⚡MODERATESelf-Service Signup + Production Access Approval Required
- Authentication
- OAuth 2.0OAuth 2.0 (Authorization Code).
- Webhooks
- Native — customer, supplier, invoice, bill, payment, invoice-item, ledger-account and journal-entry events, auto-registered per connection.
- Partnership Required
- Yes(Registration is self-service; production credentials are issued on request by Spiris/Visma API support.)
- Partnership Application
- Visma Developer Self-Service Portal↗
- Apideck Credentials
- AvailableAvailable for testing — consumers see Apideck on the consent screen; use your own Spiris/Visma app for production.
- Costs
- No API usage fees documented by the vendor; developer registration and the sandbox are self-service at no stated cost.
- Sandbox Availability
- Available — Access Sandbox↗(Free and self-service.)
- Account Type Required
- An active eAccounting subscription (Norway, Netherlands) or Bokföring & Fakturering (Sweden)
- Consumer Access Level
- Any user who can sign in with the company's Visma Online login — the consumer selects the company during the OAuth flow; no specific admin role is documented.
- Rate Limits
- Not documented by the vendor. Expect HTTP 429 responses if you exceed an unpublished throttle.
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 |
|---|---|---|---|
| Register in the Visma Developer Self-Service Portal | ✓ (not needed if you use Apideck credentials) | — | Support available |
| Configure the OAuth app (redirect URI, scopes) | ✓ (not needed if you use Apideck credentials) | — | Docs provided |
| Request production access from Spiris/Visma API support | ✓ (not needed if you use Apideck credentials) | — | Support available |
| Add client credentials in the Apideck Dashboard | ✓ (not needed if you use Apideck credentials) | — | — |
| Authorize the connection (OAuth) | — | ✓ | Handles the OAuth flow |
| Build against the Unified API | ✓ | — | Maintains the connector |
| Token refresh | — | — | ✓ Automatic |
| Webhook registration | — | — | ✓ Automatic, per connection |
| Monitor connections | ✓ Via the Apideck Dashboard | ✓ Can revoke at any time | Logs and alerts |
Environments
- Sandbox
- Register at https://selfservice.developer.vismaonline.com/ — sandbox client id and secret arrive by email together with a sandbox eAccounting / Bokföring & Fakturering test company. Sandbox companies are for app development only.
- Production
- Live customer data. Production credentials are issued after a request to Spiris/Visma API support — they are not self-service.
- Both
- Sandbox and production share the same API base URL (https://eaccountingapi.vismaonline.com/v2) and the same identity server (https://identity.vismaonline.com). The two environments are distinguished ONLY by which OAuth client credentials you use.
🚨Important to Know About Visma eAccounting
- One product, several names — and two Apideck connectors: spiris (canonical) and visma-eaccounting (this legacy-name alias). Sold as eAccounting (Norway, Netherlands) and Bokföring & Fakturering (Sweden). Coverage is identical — pick the id your consumers know.
- A consumer changing their Visma Online password silently invalidates the refresh token. The connection keeps looking healthy until the next call fails, at which point the consumer must reauthorize.
⚠️
1 gotcha across 1 resource
Connector-specific behaviors and limitations to be aware of
📦
15 supported resources
View field mappings, supported operations, and schema details