Spiris
Service ID: spiris
Spiris (formerly Visma eAccounting) is a Nordic SaaS accounting and invoicing platform for small businesses in Sweden, Norway, and the Netherlands.
Beta — this connector is in beta. Functionality and resource coverage may change.
At a Glance
- Difficulty
- ⚡MODERATESelf-service registration and free sandbox — a single vendor approval step gates production access
- Authentication
- OAuth 2.0OAuth 2.0 (authorization code) using the consumer's Visma Online login.
- Webhooks
- Native — update events for customers, suppliers, invoices, bills, payments, invoice items, ledger accounts and journal entries (no create or delete events).
- Partnership Required
- Yes(Free self-service registration returns sandbox credentials immediately; production access is not self-service — Spiris API support grants it on request.)
- Partnership Application
- Spiris Partner Programme↗
- Apideck Credentials
- AvailableAvailable for testing against a Spiris sandbox company. A sandbox client cannot reach a live company, so real companies need your own production credentials.
- Costs
- No published fee for API access. Visma's Developer Terms allow commercial terms to be added for an individual integrator by signed addendum, case by case.
- Sandbox Availability
- Available — Access Sandbox↗(One sandbox company per developer email; its region is fixed at creation, and the product's own internal integrations are mocked.)
- Account Type Required
- Active Bokföring & Fakturering (Sweden) or eAccounting (Norway, Netherlands) subscription
- Consumer Access Level
- Any Visma Online user with access to the company — Spiris documents no minimum role
- Rate Limits
- 600 requests/min, counted per client per endpoint; HTTP 429 above the limit
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 |
|---|---|---|---|
| Developer registration and application credentials | ✓ | — | — |
| Requesting production access | ✓ (to Spiris API support for your market) | — | — |
| Authorizing the connection | — | ✓ (signs in and selects the company) | — |
| OAuth flow and token refresh | — | — | ✓ |
| Webhook subscriptions | — | — | ✓ (registered and removed per connection) |
Environments
- Shared endpoint
- Sandbox and production share one API base URL and one identity server. There is no separate sandbox host — the two are told apart purely by the type of OAuth client used.
- Sandbox
- A sandbox client reaches sandbox companies only, so it can never connect a real customer company.
- Production
- A production client reaches real customer companies, and can also connect a sandbox company for testing.
🚨Important to Know About Spiris
- One product, several names, one API: Spiris is the company (renamed from Visma Spcs) and the accounting product still ships under two brand names, Bokföring & Fakturering and eAccounting — one integration reaches both.
- Refresh tokens last two years and rotate on each refresh, but they are invalidated immediately and without warning when the consumer changes their Visma Online password — the connection then fails until they reauthorise.
⚠️
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