Exact Online | Operate As Docs

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

Website: exactonline.com
Connects by: Signing in with Exact Online
Category: Accounting
Services: 1
Tools: Pass-through only

Service	Key	Base URL
Exact Online	`exact-online`	`https://start.exactonline.{region}/api/v1/{division}`

Your client also types their exact online country (The ending of your Exact Online address: nl, be, de, co.uk, fr, es or com) and division (Your administration's number, in Exact Online under Settings > Company).

Connecting

Your client presses Connect on their link and approves on Exact Online'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": [
      "exact-online"
    ]
  }
]

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

Permissions

What the client reads	Permission it asks for
See and change the administrations you can reach in Exact Online	Chosen on the provider's screen

Pass-through

Exact Online 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 Exact Online. Then send them their link.

Your client connects

They sign in with Exact Online and approve.

Find the endpoint

Pick the call from Exact Online's own API docs. Your path is everything after https://start.exactonline.{region}/api/v1/{division}, with the parts in braces filled in from your client's account.

Send it through Operate As

Use the client's ID, the service key exact-online 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-.../exact-online/crm/Accounts" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../exact-online/crm/Accounts" \  -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 Exact Online 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 Exact Online access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Exact Online 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": "exact-online",
    "services": [
      "exact-online"
    ],
    "reconnectUrl": "https://…"
  }
}

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