SnelStart API: connect SnelStart to your webshop, CRM and payments

What you can do with the SnelStart API

• Webshop orders as a sales order or invoice in SnelStart
• Keep contacts in sync with your CRM or webshop
• Prepare payments from Mollie or the bank for reconciliation
• Items and prices from SnelStart to your webshop
• Fetch outstanding items for reminders or a dashboard

How the integration works

SnelStart works with an application process: first a development key and a free temporary test account, then the build against the documentation in the B2B portal, and only after certification a permanent key. For a production integration SnelStart requires OAuth and a webhook URL. In n8n an HTTP step talks to the API; every order gets a fixed reference, so nothing is booked twice.

Facts about the SnelStart API

Checked on 2 November 2026 against the official documentation. Limits, prices and versions change; the source is listed per row.

Fact	What the documentation says	Source
Application	Request the integration through a form at SnelStart; then access to the B2B portal with a development key.	SnelStart: API
Permanent key	Only after certification of the integration (SnelStart mentions about twelve days). A production integration requires OAuth, a webhook URL and at least five customers.	SnelStart: API
Test environment	A free temporary user account to develop with.	SnelStart: B2B API portal
Documentation	The technical documentation sits behind a login in the B2B portal. Token lifetime, limits and versioning policy are not publicly documented.	SnelStart: B2B API portal
API cost	Which plans include the API and what certification costs is not in the public documentation; I check that with you at SnelStart.	SnelStart: API
n8n	No built-in node; a community node on npm (December 2025). I connect through the API with an HTTP step.	n8n documentation

What you need on your side

• An API application with SnelStart in your company's name, plus the test account and the development key
• The VAT rates and ledger accounts per item or service, aligned with your accountant
• A fixed reference per order and per contact, so nothing is booked twice
• Access to the webshop, CRM or payment service on the other side

Where it often goes wrong, and how I prevent it

• Underestimating the application process: a permanent key only comes after certification, which SnelStart estimates at about twelve days. I plan for that up front.
• VAT and ledger: every item must land on the right VAT rate and the right ledger account. I agree that mapping with you or your accountant.
• Duplicate contacts: without a fixed key you get duplicate contacts. I match on a fixed number, not on name.
• Documentation behind a login: the technical details are not public. What I list here is what SnelStart publishes itself; the rest I check in the portal.

In practice

A SnelStart integration is not yet listed as In production with me. The route is the same as for Moneybird and Exact Online: first against a test account, a fixed reference per order and contact, and a plain-language notification when a booking fails.

What it costs

I build a SnelStart integration as one scoped process for a fixed price, from €750. Maintenance and monitoring are a monthly fee: n8n management from €250 per month, server management €145 per server. Any SnelStart costs for the API and certification come on top; we check those up front. All prices and what is included →

What I do not do

• I do not do your bookkeeping; the VAT and ledger mapping comes from you or your accountant.
• I do not build a production integration outside SnelStart's certification process.
• I do not quote limits or token lifetimes that SnelStart does not publish.

Frequently asked questions about the SnelStart API

Does n8n have a SnelStart node?

No, not built in. There is a community node on npm (December 2025), but I connect through the official B2B API with an HTTP step in n8n. That is readable, exportable and runs on your own server.

What do I need to arrange with SnelStart?

An application for the API with SnelStart. You then get a development key and a free temporary test account. For a permanent key SnelStart requires certification of the integration; that takes about twelve days.

Is OAuth mandatory?

For a production integration it is: SnelStart requires OAuth and a webhook URL. I build the integration that way from the start, so certification does not stall on that point.

Which SnelStart plans include an API?

That is not in SnelStart's public documentation. In the assessment I check your plan with SnelStart before we build anything.

What happens when a booking in SnelStart fails?

The order goes to a queue and you get an error email with the order number and what went wrong. Temporary errors are retried automatically.