How to connect to e-Boekhouden

This guide walks you through connecting your e-Boekhouden.nl administration through Apideck Vault.

Connecting to e-Boekhouden works differently from most connectors: there is no authorize-and-redirect step. Instead of being sent to e-Boekhouden to approve access, you generate a personal API access token yourself inside your own e-Boekhouden account, then paste that token into a single field in Vault. There is no app to register, no redirect URL to configure, and no scopes to grant.

Prerequisites

An e-Boekhouden.nl administration account with enough access to reach the account's management settings. No separate developer account, app registration, or approval step is required.
API access is included in the standard e-Boekhouden plans — there is no separate add-on to buy.

1. Open the API token screen in e-Boekhouden

Log in at https://secure20.e-boekhouden.nl.
Go to Beheer → API-token.

The exact menu path may vary slightly by account type — in some administrations the same screen sits under Beheer → Inrichting → Koppelingen, and in accountant environments it is reached via Accountant → Instellingen → Koppelingen. Look for the API token screen in whichever of these your account presents.

2. Generate your API access token

Create a new personal API access token.
Choose its validity period (Geldigheidsduur) — for example 12 months. The connection stops working when that period lapses, so make a note of the date: before then you will need to generate a replacement token and update it in Vault.
Copy the token immediately. e-Boekhouden shows it only once; if you navigate away without copying it, generate a new one and repeat this step.

3. Paste the token into Apideck Vault

Open the e-Boekhouden connector in Vault.
Paste the token into the API Access Token field — this is the only credential the connector needs.
Save the connection.

Apideck exchanges your long-lived access token for a short-lived session token automatically, behind the scenes. There is nothing for you to configure or refresh, and no further authorization step once the connection is saved.

Notes

The token is shown only once. Store it somewhere safe (a password manager) if you may need to re-enter it. It cannot be retrieved again from e-Boekhouden — only replaced.
Treat the token like a password. It grants access to the bookkeeping data of the administration it was created in.
Changing your e-Boekhouden password does not invalidate existing API tokens — there is no need to reconnect after a password change.
Deactivating or removing the e-Boekhouden user that created the token does invalidate it. If that user leaves your organisation, generate a replacement token under a user that will remain active and update the connection in Vault.
e-Boekhouden has a single environment. Every token is created against, and every call is made to, your real administration — there is no separate sandbox. Use a trial administration if you want to test writes without touching production books.
Apideck uses e-Boekhouden's REST API v1. e-Boekhouden also still supports its older SOAP webservice; a credential issued for that legacy service is a different kind of credential and is not what this connector uses.
To revoke Apideck's access at any time, delete the token on the same API token screen. Deleting it stops any new session from being issued, but calls that reuse an already-issued session may keep succeeding for up to about an hour before access ends.

Troubleshooting

"Token ongeldig" / the connection fails to validate. Most often the token was only partially copied — it is shown once, so a truncated paste is easy to miss. Generate a fresh token and paste it again in full, with no leading or trailing spaces.
The connection worked and then stopped. Check whether the token's validity period has lapsed, or whether the e-Boekhouden user that created it has been deactivated or removed. Both invalidate the token; a new token from an active user resolves it.
You cannot find the API token screen. If you work in an accountant environment, the screen is reached via Accountant → Instellingen → Koppelingen rather than under Beheer. Otherwise, your e-Boekhouden user may not have the management rights needed to reach it — ask an administrator of that administration to generate the token for you.

For the underlying API itself, e-Boekhouden publishes an official reference at https://api.e-boekhouden.nl/scalar/.

Still stuck? Reach out to Apideck Support.