Visma eAccounting

Getting a token

1. Register at developer.vismaonline.com and create an application. You receive a client id and client secret.
2. Run the authorization-code flow once for the customer's company, asking for the scopes you need — ea:api, ea:sales, ea:purchase, ea:accounting. Keep the refresh token.
3. Set VISMA_CLIENT_ID, VISMA_CLIENT_SECRET and VISMA_REFRESH_TOKEN.

Sandbox and production are different hosts. This adapter targets production at eaccountingapi.vismaonline.com. The sandbox lives at eaccountingapi-sandbox.vismaonline.com with its own client registration; a production token there fails in a way that looks like a bad secret. If you want to test first, register a sandbox app and build a custom connector against that host.

One connector, one company. The token is bound to the company it was authorised for. A bookkeeper with several clients needs one connector per client.

Filtering is OData-flavoured on most collections: $filter, $top, $skip, $orderby. Dates are ISO 8601. $top is capped server-side around 1000.

Vocabulary is Nordic. CustomerInvoiceDraft is an unposted invoice; CustomerInvoice is posted and immutable. A draft is not revenue, and an agent summing both will over-report.

Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.

Cloud reachability: eaccountingapi.vismaonline.com is public with a valid certificate.