Connecting to e-Boekhouden.nl
e-Boekhouden.nl has two entry points side by side, and the choice between them decides how long your integration lasts.
Two generations side by side
e-Boekhouden.nl offers two ways to connect. The older one is a SOAP integration, a technology in which your software first opens a session and then exchanges messages. The newer one is a REST API, the technology the rest of the market now uses.
In the e-Boekhouden.nl menu, the SOAP integration is literally labelled as the old integration. A new integration should therefore be built on the REST API, even where an existing one still runs over SOAP.
Getting access
You create the token for the REST API yourself in your e-Boekhouden.nl account settings.
If the administration sits on your accountant's subscription, your accountant creates the token or grants you the right to do so.
What to watch in the design
e-Boekhouden.nl does not publish a fixed number of calls per day, but there may still be a limit.
So design the integration as though there is a limit. Spread an initial import of thousands of rows over a longer period, and let the integration retry at intervals when the package does not respond.
Sources
Frequently asked questions
Do we have to replace our existing SOAP integration right away?
First ask e-Boekhouden.nl how long the SOAP entry point will remain available. Build new integrations on the REST API, and plan the move of the existing integration for a time that suits you.
Is API access part of our subscription?
You can check that for your own plan in your account settings, because the public documentation does not list it per plan.
How many invoices a day can an integration like this handle?
e-Boekhouden.nl does not publish a figure for that. If you give us your numbers in the intro call, we will look into what is possible in your situation.
Can you also retrieve data from e-Boekhouden.nl rather than write to it?
We can, for instance for a client portal showing outstanding invoices.