Visma eAccounting | Operate As Docs

Connect your client's Visma eAccounting with a sign-in, and call its API through Operate As.

Website: visma.com
Connects by: Signing in with Visma eAccounting
Category: Accounting
Services: 1
Tools: Pass-through only

Service	Key	Base URL
Visma eAccounting	`visma-eaccounting`	`https://eaccountingapi.vismaonline.com/v2`

Connecting

Your client presses Connect on their link and approves on Visma eAccounting's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "visma-eaccounting"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "visma-eaccounting"    ]  }]

Permissions

What the client reads	Permission it asks for
See and change your customers, articles and invoices	`ea:sales`
See and change your accounts, vouchers and fiscal years	`ea:accounting`
See and change your suppliers and supplier invoices	`ea:purchase`

Pass-through

Visma eAccounting has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.

Add the client

In Clients, add your client and select Visma eAccounting. Then send them their link.

Your client connects

They sign in with Visma eAccounting and approve.

Find the endpoint

Pick the call from Visma eAccounting's own API docs. Your path is everything after https://eaccountingapi.vismaonline.com/v2.

Send it through Operate As

Use the client's ID, the service key visma-eaccounting and that path. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../visma-eaccounting/companysettings" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../visma-eaccounting/companysettings" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Visma eAccounting refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Visma eAccounting access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Visma eAccounting access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "visma-eaccounting",
    "services": [
      "visma-eaccounting"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "visma-eaccounting",    "services": [      "visma-eaccounting"    ],    "reconnectUrl": "https://…"  }}