Custom integrations. Your software finally talks to each other.
Webshop, POS, accounting, ERP, CRM, payments, shipping and Peppol: we get them exchanging data, in both directions. We work with their APIs. And if a package doesn’t have one, we build one.
Demo: an online order from Koffiebranderij Vennegem runs automatically through the Brisk integration layer to the webshop, Mollie, the POS, Exact Online, Sendcloud, Teamleader and Slack; then a B2B invoice goes out via Peppol. With the buttons below, you can read for each system what goes in and what comes out.
koffievennegem.be/afrekenen
Koffiebranderij VennegemCoffeeGearSubscription
Checkout#10482
2× Huismelange 1 kg
Only 42 left in stock
€53.80
1× Ethiopië Guji 250 g
Only 7 left in stock
€11.90
Shipping with bpost€4.95
Total incl. VAT€70.65
Pay with Bancontact
Mollie
Paymentstr_…
Paid€33.90tr_Bv3Xe9Kd2M09:11
Paid€47.35tr_Fj8Ny4Ta6Q08:30
POS · Vennegem store09:42
Huismelange
1 kg
€26.9042 pcs
Espresso Donker
1 kg
€28.5018 pcs
Ethiopië Guji
250 g
€11.907 pcs
Decafé Zacht
500 g
€15.5023 pcs
Handmolen Staal
1 st
€64.005 pcs
StockUpdated at 09:42
Exact Online
›Sales invoices
VF-2026-0317Jens Wouters€33.90
VF-2026-0316Brasserie VennegemB2B · via Peppol
Sales invoice
Sendcloud
›Shipments
No shipments yet today
Teamleader Focus
T
Contacts ›Sarah Peeters
SP
Sarah Peeters
Consumer · 3600 Genk
TimelineDealsSales invoices
Order #10211 · €53.80Sep 14
Signed up for the newsletterMar 2
Peppol
›E-invoiceBIS Billing 3.0
—
To
Brasserie Vennegem
Peppol ID
0208:0798765406
Document
UBL 2.1 · EN 16931
0208:0712345631
UBL created
Validated
Sent via access point
Delivered via Peppol
Slack
orders
No messages yet today
Message #orders
Brisk integration layerLiveEuropean servers
Events today
1,288
Queue
0
Errors
0
Event streamSimplified
11:04.744order.created#10481webshoplayer
11:05.312webhookid=tr_Bv3Xe9Kd2Mmollielayer
11:05.559invoice.createdVF-2026-0317201layerexact
30:00.000stock.sync5 SKUOKkassalayer
P8 / 8 OK
Brisk integration layerLive
09:11:05invoice.createdVF-2026-0317
09:30:00stock.sync5 SKU
koffievennegem.be/afrekenen
Koffiebranderij VennegemCoffeeGearSubscription
Checkout#10482
2× Huismelange 1 kg
Only 42 left in stock
€53.80
1× Ethiopië Guji 250 g
Only 7 left in stock
€11.90
Shipping with bpost€4.95
Total incl. VAT€70.65
Pay with Bancontact
Webshop
Your own webshop
What goes in
The stock the POS sells, so you never sell online what’s no longer there.
What comes out
Every new order, instantly: customer, products, shipping costs and payment method.
For your IT teamREST API · webhook on a new order, signed with HMAC-SHA256
Demo · Koffiebranderij Vennegem
Click a system to see what goes in and what comes out. Or place an order yourself.
We integrate with, among others
Brand names and logos belong to their owners; they show which systems we integrate with.
What is an integration? Simply: no more retyping.
An integration lets two programs exchange data automatically, so nobody has to retype it. Your webshop, POS and accounting software stay what they are. They just talk to each other.
A computer screen with four windows: Lotte’s inbox with a new webshop order, an Excel sheet with the inventory, a sales invoice in the accounting software and the product page of Ethiopië Guji in the webshop. Without an integration, Lotte retypes everything and makes a typo. With an integration, it all happens on its own.
Time lost to retyping0:00(demo, sped up)
Demo · Koffiebranderij Vennegem
MailFileEditViewWindowHelpTue Oct 6 09:42
Inbox
1 unread
Search
Yusuf08:57Parcels todayI’m taking everything to bpost at 4 p.m. Are there any…
Brasserie VennegemyesterdayOrder for next weekCould we get 6 kg of Huismelange again? And the invoice…
WebshopyesterdayNew order #10481Tom Claes · 1 item · €33.45
WebshopyesterdayNew order #10480An Wouters · 2 items · €47.35
Parcels today
From: Yusuf
I’m taking everything to bpost at 4 p.m. Are there any…
Inventory 2026.xlsx
FileHomeInsertFormulasData
A1fxSKU
ABCD
1SKUProductStockUpdated
2KV-HUIS-1000Huismelange 1 kg42Fri Oct 2
3KV-ESP-1000Espresso Donker 1 kg18Fri Oct 2
4KV-ETH-0250Ethiopië Guji 250 g1Fri Oct 2
5KV-DEC-0500Decafé Zacht 500 g23Fri Oct 2
6KV-MOL-0001Handmolen Staal 1 st5Fri Oct 2
7
8
9
10
InventoryOrdersSheet3Ready
koffievennegem.be
Koffiebranderij VennegemCoffee · Single origin
Ethiopië Guji
Light roast · floral, citrus, jasmine
€11.90
250 g · incl. 6% VAT
In stock
Add to cart
SalesPurchasesBankReportsKoffiebranderij
Sales invoice
Invoice number VF-2026-0318
Draft
CustomerInvoice datePayment method
DescriptionQtyPriceVATAmount
Total excl. VAT–
VAT 6%–
Total incl. VAT–
Still to post
23 orders
Post
Sept. invoices
to Els!!
Inbox
1 unread
Search
Yusuf08:57Parcels todayI’m taking everything to bpost at 4 p.m. Are there any…
Brasserie VennegemyesterdayOrder for next weekCould we get 6 kg of Huismelange again? And the invoice…
WebshopyesterdayNew order #10481Tom Claes · 1 item · €33.45
WebshopyesterdayNew order #10480An Wouters · 2 items · €47.35
Parcels today
From: Yusuf
I’m taking everything to bpost at 4 p.m. Are there any…
Lotte retypes every order: into the inventory sheet and into the accounting software. One wrong key and the invoice is off. Meanwhile, the webshop shows a coffee that’s already sold out.
Switch between without and with integration yourself.
And what’s an API?
An API is a program’s service entrance. Other programs ring the bell there to ask for something or drop something off, following fixed rules. An integration uses that entrance, so nobody has to go through the screen.
Front door
The screen. For people: clicking, reading and typing.
Service entrance
The API. For programs: fast, day and night, without typos.
The questionHow many bags of Huismelange do you have left?
GET /v1/products/KV-HUIS-1000/stock
Authorization: Bearer eyJhbGciOi…
The answer40 one-kilo bags left.
200 OK
{ "sku": "KV-HUIS-1000", "stock": 40 }
For your IT team: a REST API over HTTPS with JSON, secured with a token.
Simplified
Four kinds of integrations
Every integration is a combination: one or two directions, instantly or at a set time.
WebshopAccounting
One-way
Every webshop order automatically becomes a sales invoice in the accounting software. Nothing goes back.
Technical: A → B · the webshop reports, the accounting software receives
POSWebshop
Two-way
POS and webshop share one inventory. For each piece of data, we agree which system is the boss: the source of truth.
Technical: A ↔ B · stock: the POS is the source · product copy: the webshop
PaymentPOSTWebshop
Real-time
When Sarah pays with Bancontact, the webshop hears about it instantly and her confirmation goes out.
Technical: Webhook · HTTP POST on every status change
POS02:00Accounting
Batch
Every night at 02:00, the POS sends the day’s sales to the accounting software as one file.
Technical: Every night 02:00 · CSV file via SFTP
What does retyping cost you?
Fill in your own numbers. It’s an estimate, not a promise.
15
4
€35
We count 21 workdays a month and only the time spent retyping. Fixing mistakes and phone calls from your accountant aren’t included.
Every system, explained.
Pick a category, or search by name or by a word like VAT, inventory or invoice. For each logo, you read in plain language what it is and what an integration gets you. Click Technical for your IT person: which API, how to sign in, whether there are webhooks, and a bit of real data.
Online accounting software for small businesses. Your accountant can work in it directly, and you also use it to send and receive e-invoices via Peppol.
Who is it for?
Small businesses that do their accounting online, together with their accounting firm.
What does an integration get you?
Every paid order shows up in Exact right away as a sales invoice, with the right VAT code. Payments are reconciled, and your accountant has nothing left to ask.
What do we connect?
sales invoices
customers
products
inventory
payments
journal entries
VAT codes
API
REST · JSON · OData
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time or in batches
REST API with OData queries ($filter, $select), per administration (division). Sign-in with OAuth 2.0 (authorization code); the access token is valid for only 10 minutes and is renewed with the refresh token. Webhooks (WebhookSubscriptions) report a change per topic; we then fetch the record ourselves.
What we watch out for: Exact counts requests per minute and per day per administration and answers with HTTP 429 if you go over. We only request what has changed, bundle write operations and schedule large imports at night.
Online accounting software where you and your accountant work together. Purchase invoices and receipts are scanned and processed in it, and Peppol is built in.
Who is it for?
Small businesses and freelancers whose accounting firm works with Yuki, in Belgium and the Netherlands.
What does an integration get you?
Sales invoices from your webshop or software land in Yuki automatically, with customer, VAT and amount. No more exports and uploads at the end of the month.
SOAP web services (.asmx) per domain: Sales, Accounting, Archive, Contact… You sign in with a Web Service access key (Authenticate), get a session ID valid for 24 hours, and send it with the administration ID on every call.
What we watch out for: No webhooks, and the number of calls per day is limited (above that, you pay per tier). We send invoices bundled in a single XML message and poll for changes on a fixed schedule.
Octopus
What is it?
Belgian accounting and invoicing software, widely used by accounting firms and their clients.
Who is it for?
Small businesses whose accountant works in Octopus.
What does an integration get you?
Your invoices and customers land in the right file automatically. Octopus sends sales invoices via Peppol when the customer can be reached there.
REST API with an OpenAPI description (there is also a SOAP version). Sign-in in two steps: first a JWT for the user (with Octopus’s software house UUID), then a dossier token; both are valid for 10 minutes.
What we watch out for: No webhooks, and a limit per endpoint per day. We only fetch the changes via the /modified endpoints and keep the number of calls well below the limit.
Billit
What is it?
Belgian invoicing platform and accredited Peppol access point. You create invoices in it, and receive purchase invoices through it via Peppol.
Who is it for?
Small businesses and freelancers who want simple invoicing, and software that needs a Peppol access point.
What does an integration get you?
A B2B order becomes a Peppol invoice that arrives at your customer without retyping. Purchase invoices come in automatically too.
REST API with a separate sandbox. Sign-in with OAuth 2.0 (an API key is only allowed for non-commercial integrations). Webhooks on invoices and messages, signed with a secret.
What we watch out for: Billit calls invoices “orders”, and credit notes are a separate type. We test in the sandbox first and only then request production access.
Exact WinBooks
Exact WinBooks
What is it?
Belgian accounting software, very common at accounting firms. Available as WinBooks Classic and WinBooks on Web; Peppol via a module.
Who is it for?
Small businesses whose accounting firm works in WinBooks.
What does an integration get you?
Your sales invoices and customers land in the right file at your accountant automatically, with the right accounts.
WinBooks on Web has a REST API (JSON or XML) per dossier (folder). Sign-in via OAuth 2.0: you create a token in WinBooks that we exchange for an access token. There is also WinBooks Connect, with its own API.
What we watch out for: We found no webhooks for WinBooks on Web, so we work on a fixed schedule. We agree on accounts and VAT codes with your accountant up front.
QuickBooks
Intuit QuickBooks Online
What is it?
Online accounting software from Intuit, mainly used in English-speaking countries. You see it less in Belgium.
Who is it for?
Companies with a branch or accountant in the United Kingdom or the US.
What does an integration get you?
Orders and payments show up in QuickBooks automatically as invoices and receipts.
What do we connect?
sales invoices, customers, products, payments
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time or in batches
REST API v3 per company (realmId), sign-in with OAuth 2.0 (authorization code). Webhooks only report which record changed, signed with an intuit-signature header; we then fetch it. There are sandbox companies for testing.
What we watch out for: There is a limit per company per minute, and Intuit is moving its webhooks to the CloudEvents format. We follow their announcements and update the integration in time.
Xero
What is it?
Online accounting software, big in Australia, New Zealand and the United Kingdom.
Who is it for?
Small businesses with international accounting, or an accountant who works with Xero.
What does an integration get you?
Sales, payments and payouts from your payment provider show up in Xero automatically, ready to reconcile.
What do we connect?
sales invoices, customers, products, payments, bank transactions
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time or in batches
REST API (JSON or XML), sign-in with OAuth 2.0 per organization (tenant). Webhooks report the event type and the ID, signed with x-xero-signature (HMAC-SHA256). You can test in the free demo company.
What we watch out for: Xero limits the number of calls per minute and per day per organization. We use filters (If-Modified-Since, where) and bundle invoices per call.
Odoo
What is it?
A modular ERP from Belgium: sales, inventory, accounting, webshop, POS and more in one package. Odoo is also a Peppol access point itself.
Who is it for?
Small businesses that want several departments in one system.
What does an integration get you?
Your webshop, shipping and Odoo stay in sync: orders, inventory and invoices without retyping.
External API: from Odoo 19, the JSON-2 API (POST /json/2/<model>/<method>) with an API key as bearer token; the older XML-RPC and JSON-RPC keep working until they are removed in Odoo 22. Outgoing webhooks via automation rules. The external API is only included in the Custom plan.
What we watch out for: Custom fields and modules differ per installation and change with every Odoo version. We read the actual data model of your Odoo and test every upgrade beforehand.
SAP
SAP S/4HANA and SAP Business One
What is it?
ERP for mid-sized and large companies (S/4HANA) and for small businesses (Business One). Often the heart of production, inventory and finance.
Who is it for?
Companies with a larger ERP, often with their own IT department or SAP partner.
What does an integration get you?
Your webshop or app works with the real prices, inventory and customer data from SAP, and orders go into it without retyping.
S/4HANA: OData APIs (V2/V4) from the SAP Business Accelerator Hub, via a communication user (basic, OAuth 2.0 or certificate); events via SAP Event Mesh. Business One: the Service Layer (REST/OData) with a session via /Login, and recently webhooks too. On older systems: IDoc and BAPI/RFC.
What we watch out for: Every SAP is set up differently. We work with your SAP administrator on the standard APIs, so SAP itself needs as little customization as possible.
Microsoft Dynamics 365 Business Central
What is it?
Microsoft’s ERP for small businesses: finance, sales, purchasing and inventory, in the cloud and woven into Microsoft 365.
Who is it for?
Small businesses that work with Microsoft and have an ERP through a Microsoft partner.
What does an integration get you?
Orders from your webshop become sales orders or invoices in Business Central, and your webshop shows the real inventory and prices.
REST API v2.0 (OData v4) per company. Sign-in via Microsoft Entra ID with OAuth 2.0, including server-to-server (client credentials). Webhooks are called subscriptions here: they expire after three days and only report which record changed.
What we watch out for: There is a limit per user per five minutes, and subscriptions have to be renewed in time. Our integration renews them itself and sends an alert if that fails.
AFAS Software
AFAS Profit
What is it?
Dutch software for ERP, HR and payroll, also used in Belgium. Peppol is built in.
Who is it for?
Mid-sized organizations that want finance, HR and projects in one package.
What does an integration get you?
Orders, customers and employees stay in sync with your webshop, app or other software, with no double entry.
Profit REST (or SOAP) via connectors: GetConnectors to read, UpdateConnectors to write. Sign-in with an app connector token in the header (AfasToken, base64). Webhooks exist since Profit 8, but only for dossier items and workflows, with an HMAC signature.
What we watch out for: Which fields you can read is determined by the GetConnector set up in AFAS. We build it with your AFAS administrator and test in the test or acceptance environment first.
Teamleader
Teamleader Focus
What is it?
Belgian CRM with quotes, invoicing, projects and planning in one. Widely used by small businesses and agencies.
Who is it for?
Small businesses that want their customers, deals and invoices in one place.
What does an integration get you?
A won deal becomes a customer in your accounting, and a website form becomes a contact in Teamleader. Nobody retypes anything anymore.
Its own API style: actions over HTTPS, such as POST /invoices.list or /contacts.add, with JSON in the body. Sign-in with OAuth 2.0 (authorization code) via the Teamleader Marketplace. Webhooks via webhooks.register, e.g. on deal.won or invoice.booked.
What we watch out for: There is a per-minute limit (HTTP 429 if you go over). We read in pages, buffer write operations and let webhooks do the work instead of polling constantly.
HubSpot
What is it?
CRM and marketing platform: contacts, companies, deals, tickets and emails.
Who is it for?
Small businesses with a sales or marketing team that follows up on leads.
What does an integration get you?
Customers and orders from your webshop are in HubSpot, and won deals go to your accounting automatically.
What do we connect?
contacts, companies, deals, tickets, emails
API
REST · JSON
Sign-in
OAuth 2.0 · Token
Webhooks
Yes
Timing
Real time
REST API (CRM objects), since 2026 with date-based versions like /2026-03/. Sign-in with OAuth 2.0 for apps or a private app token. Webhooks via the app configuration, signed (X-HubSpot-Signature-v3).
What we watch out for: The limit depends on your plan: a number of calls per ten seconds and per day. We use batch endpoints and search smartly instead of fetching everything.
Salesforce
What is it?
Enterprise CRM for sales, service and marketing, customizable almost without limits.
Who is it for?
Mid-sized and large companies with their own Salesforce administrator.
What does an integration get you?
Salesforce and your ERP share the same customers and orders; your sales reps see invoices and deliveries without switching screens.
What do we connect?
contacts, companies, deals, quotes, orders
API
REST · JSON · SOAP · XML
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time or in batches
REST API per version, plus SOAP, Bulk API 2.0 for large volumes, and Pub/Sub. Sign-in with OAuth 2.0 via an External Client App (e.g. JWT bearer for server-to-server). We follow changes via Change Data Capture or Platform Events.
What we watch out for: There is a daily limit per organization, depending on your edition and licenses. Large volumes go through the Bulk API, and we always test in a sandbox first.
Pipedrive
What is it?
A clear, simple CRM built around your sales pipeline: deals, people, organizations and tasks.
Who is it for?
Small sales teams that want to track their deals visually.
What does an integration get you?
A won deal becomes a customer in your accounting or a project in your planning, without retyping.
What do we connect?
deals, contacts, companies, tasks
API
REST · JSON
Sign-in
API key · OAuth 2.0
Webhooks
Yes
Timing
Real time
REST API (deals on v2, some endpoints still v1) with an OpenAPI description. Sign-in with an API token or OAuth 2.0. Webhooks per object and action, e.g. create.deal.
What we watch out for: Pipedrive works with a daily budget and a burst limit per two seconds, both depending on your plan. We spread calls evenly and use webhooks instead of polling.
Zoho
Zoho CRM
What is it?
CRM from the large Zoho family (accounting, help desk, email…), affordable and feature-rich.
Who is it for?
Small businesses that already use other Zoho apps or want an affordable CRM.
What does an integration get you?
Leads, customers and deals stay in sync with your website, webshop and accounting.
What do we connect?
contacts, companies, deals, tasks
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time
REST API v8, sign-in with OAuth 2.0 (Zoho-oauthtoken header) via your account’s data center (.eu for Europe). Notifications via the Notifications API (watch), which you renew at least weekly.
What we watch out for: Zoho counts credits per day and limits concurrent calls. We use bulk endpoints and keep the notification channels alive ourselves.
Peppol
What is it?
The European network for e-invoices. Since January 1, 2026, Belgian VAT-registered businesses send each other structured e-invoices, and by default that goes via Peppol.
Who is it for?
Every Belgian VAT-registered business that invoices other businesses or receives invoices from them.
What does an integration get you?
Your invoices arrive as data straight in your customer’s accounting, and purchase invoices land in yours automatically. No more retyping PDFs.
What do we connect?
sales invoices, credit notes, purchase invoices
API
AS4 via an access point
Sign-in
Certificate
Webhooks
Not applicable
Timing
Real time
Four-corner model: you (C1) → your access point (C2) → the recipient’s access point (C3) → the recipient (C4). Access points find each other via SML/SMP using the Peppol ID (in Belgium 0208 + company number) and talk AS4. The format is Peppol BIS Billing 3.0: UBL XML according to EN 16931.
What we watch out for: An invoice that fails the validation rules is rejected. We validate before sending and feed the responses (delivered, rejected) back into your system.
Hermes
Shut down end of 2025
What is it?
The free transitional platform from the federal government (FPS BOSA) for sending and reading e-invoices via Peppol. It shut down at the end of 2025.
Who is it for?
Businesses that temporarily didn’t have their own Peppol solution yet.
What does an integration get you?
Did you use Hermes? Then you now need your own Peppol access point: through your accounting software, through an invoicing platform, or through an integration from your webshop or software. We build that integration.
What do we connect?
sales invoices
API
Web portal
Sign-in
Not applicable
Webhooks
Not applicable
Timing
In batches
Hermes was a web portal, not an API for your own software. It converted structured invoices into a readable form for those who didn’t have Peppol tools yet. Today, sending and receiving goes through an accredited Peppol service provider.
What we watch out for: Check that you can still receive e-invoices: a company number that isn’t registered anywhere as a Peppol recipient won’t receive any e-invoices.
Mollie
What is it?
A payment provider from the Netherlands, widely used in Belgium. One integration for Bancontact, cards, Apple Pay, iDEAL, Klarna and more.
Who is it for?
Webshops, apps and platforms that want to accept online payments.
What does an integration get you?
A payment marks your order as paid, creates the invoice and reconciles it in your accounting. Refunds are handled too.
What do we connect?
payments, refunds, payouts, customers, mandates
API
REST · JSON
Sign-in
API key · OAuth 2.0
Webhooks
Yes
Timing
Real time
REST API v2 with an API key (test_ or live_) or OAuth for platforms. The classic webhook only sends the payment ID, without a signature; we then fetch the payment ourselves, so you know for sure the status is correct. Mollie retries up to 10 times.
What we watch out for: A webhook can arrive twice or late. We process every payment idempotently: receiving the same payment twice never creates two invoices.
Stripe
What is it?
An international payment platform with payments, subscriptions and invoices, including Bancontact and iDEAL.
Who is it for?
Webshops, SaaS and platforms, especially with subscriptions or international customers.
What does an integration get you?
Payments and subscriptions flow through to your accounting and your customer records automatically.
REST API (form-encoded in, JSON out) with a secret key and date-based versions. Webhooks signed with Stripe-Signature (HMAC-SHA256 over timestamp and payload); Stripe retries for up to three days.
What we watch out for: Amounts are in cents (7065 = €70.65) and there is a per-second limit. We check every signature and timestamp and process each event only once.
Bancontact
What is it?
The Belgian payment scheme: with your bank card or with the Bancontact app via a QR code. Online, it’s the payment method Belgians know best.
Who is it for?
Every webshop or app with Belgian customers.
What does an integration get you?
Bancontact is in your checkout, and payments land in your orders and accounting automatically.
What do we connect?
payments, refunds
API
Via your payment provider
Sign-in
Via your payment provider
Webhooks
Not applicable
Timing
Real time
Online, you accept Bancontact via a payment provider such as Mollie or Stripe (method: bancontact); so you integrate with your provider’s API. Bancontact Pro (formerly Payconiq) also has its own API for QR and invoice payments.
What we watch out for: Euro only. We choose the provider together with you and put Bancontact at the top of your checkout.
PayPal
What is it?
A global digital wallet and checkout button.
Who is it for?
Webshops with international customers.
What does an integration get you?
PayPal payments become regular paid orders, neatly reconciled in your accounting.
What do we connect?
orders, payments, refunds
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time
REST API (Orders v2). Sign-in with OAuth 2.0 client credentials (client ID and secret). We verify webhooks via a certificate or via PayPal’s verify endpoint. There is a sandbox.
What we watch out for: Approving an order isn’t a payment yet: the money is only there after the capture. Our integration only marks the order as paid at that point.
Klarna
What is it?
Pay later or pay in installments. The customer pays later, you get your money from Klarna.
Who is it for?
Webshops with higher order values, often fashion, home decor or electronics.
What does an integration get you?
Klarna is in your checkout, and deliveries, cancellations and returns go to Klarna automatically.
What do we connect?
orders, payments, refunds
API
REST · JSON · Via your payment provider
Sign-in
Basic auth
Webhooks
Limited
Timing
Real time
REST API with basic auth (username and password from the Merchant Portal) and a separate test environment (Playground). Often offered through a payment provider such as Mollie.
What we watch out for: A Klarna order is only authorized at first. The amount is only collected once you report the delivery (capture). We tie that to your shipping.
Apple Pay
What is it?
Paying with Face ID or Touch ID on iPhone, iPad and Mac, in Safari or in an app.
Who is it for?
Webshops and apps with many mobile customers.
What does an integration get you?
Checkout in two taps, and the payment lands in your orders and accounting like any other.
What do we connect?
payments
API
JavaScript in the browser · Via your payment provider
Sign-in
Via your payment provider
Webhooks
Not applicable
Timing
Real time
No server API of its own for merchants: Apple Pay JS or the Payment Request API runs in the browser, and processing goes through your payment provider. Requires a verified domain and HTTPS.
What we watch out for: Without domain verification, the button doesn’t appear. We place your payment provider’s verification file and test on real Apple devices.
Google Pay
What is it?
Paying with a card stored in your Google account or on your Android device.
Who is it for?
Webshops and apps with many Android and Chrome users.
What does an integration get you?
Fast checkout without typing a card number; the payment flows into your orders and accounting.
What do we connect?
payments
API
JavaScript in the browser · Via your payment provider
Sign-in
Via your payment provider
Webhooks
Not applicable
Timing
Real time
Google Pay API in the browser or app (PaymentDataRequest, apiVersion 2). Card details go encrypted to your payment provider (PAYMENT_GATEWAY tokenization). For production, you request access in the Google Pay & Wallet Console.
What we watch out for: The test environment shows test cards, not your real ones. We test in TEST and only switch to PRODUCTION after approval.
Visa
What is it?
The global card scheme behind Visa credit and debit cards.
Who is it for?
Every webshop or app that accepts card payments.
What does an integration get you?
Card payments land in your orders and accounting as regular payments, with the card type included.
What do we connect?
payments, refunds
API
Via your payment provider
Sign-in
Via your payment provider
Webhooks
Not applicable
Timing
Real time
You don’t integrate with Visa directly: card payments go through a payment provider or acquirer. The extra check (strong customer authentication under PSD2) uses 3-D Secure, called “Visa Secure” at Visa.
What we watch out for: Card details never touch your own server: the payment provider processes them. That keeps your webshop out of the heaviest PCI DSS requirements.
Mastercard
What is it?
The global card scheme behind Mastercard and Maestro cards.
Who is it for?
Every webshop or app that accepts card payments.
What does an integration get you?
Card payments land in your orders and accounting as regular payments.
What do we connect?
payments, refunds
API
Via your payment provider
Sign-in
Via your payment provider
Webhooks
Not applicable
Timing
Real time
Just like Visa, via a payment provider or acquirer. Strong customer authentication is called Mastercard Identity Check here (EMV 3-D Secure); the provider handles the check in the bank’s app.
What we watch out for: A payment that fails 3-D Secure has failed, it isn’t “pending”. Our integration then doesn’t create an invoice and sends the customer back to checkout.
iDEAL
iDEAL | Wero
What is it?
The most popular online payment method in the Netherlands: paying through your own bank. Gradually becoming Wero.
Who is it for?
Belgian webshops with Dutch customers.
What does an integration get you?
Dutch customers pay the way they’re used to, and the payment lands in your orders and accounting automatically.
What do we connect?
payments, refunds
API
Via your payment provider
Sign-in
Via your payment provider
Webhooks
Not applicable
Timing
Real time
Via a payment provider such as Mollie or Stripe (method: ideal), euro only. Since 2025, there’s a single iDEAL button without a bank list; the move to Wero goes through your provider.
What we watch out for: Names and logos change with the move to Wero. We keep your checkout in line with what your provider and iDEAL require.
Shopify
What is it?
A popular cloud webshop platform: you rent the webshop, Shopify manages the technology.
Who is it for?
Webshops, small to large, that want to launch quickly.
What does an integration get you?
Orders go to your accounting and shipping automatically, and inventory stays in sync with your POS.
What do we connect?
orders, products, inventory, customers, refunds
API
GraphQL
Sign-in
OAuth 2.0 · Token
Webhooks
Yes
Timing
Real time
The Admin API is GraphQL, with a version per quarter (e.g. 2026-07); the REST Admin API is legacy. Sign-in with an access token (X-Shopify-Access-Token) via OAuth or a custom app. Webhooks with X-Shopify-Hmac-SHA256, respond within 5 seconds.
What we watch out for: GraphQL counts points per second (depending on your plan), and each version is replaced after a year. We only request the fields we need and schedule version updates.
WooCommerce
What is it?
The webshop plugin for WordPress: open source, on your own hosting.
Who is it for?
Webshops that want full control and a WordPress site.
What does an integration get you?
Orders to your accounting and shipping, and inventory in sync with your POS or ERP.
What do we connect?
orders, products, inventory, customers, refunds
API
REST · JSON
Sign-in
API key
Webhooks
Yes
Timing
Real time
REST API (wc/v3 under /wp-json/) with a consumer key and secret (as basic auth over HTTPS). Webhooks with X-WC-Webhook-Signature (base64 HMAC-SHA256).
What we watch out for: Speed depends on your hosting and plugins. With many products, we use batch endpoints and pagination, and we watch for plugins that add fields.
Adobe Commerce (Magento)
Adobe Commerce
What is it?
An extensive e-commerce platform for large catalogs, B2B and multiple stores. Magento Open Source is the free version.
Who is it for?
Larger webshops and B2B portals, often with an ERP behind them.
What does an integration get you?
Prices, inventory and orders stay in sync with your ERP, per store and per customer group.
What do we connect?
orders, products, prices, inventory, customers
API
REST · JSON · GraphQL · SOAP · XML
Sign-in
OAuth 2.0 · Token
Webhooks
Limited
Timing
Real time or in batches
REST, GraphQL and SOAP. Sign-in via an integration (OAuth) or an admin token. Adobe Commerce has signed webhooks and events via Adobe I/O Events.
What we watch out for: Price rules, customer groups and multiple stores make mapping complex. For each field, we define which system is the source of truth.
PrestaShop
What is it?
Open-source webshop software from France, popular in Europe.
Who is it for?
Webshops that want a self-hosted, extensible store.
What does an integration get you?
Orders and inventory stay in sync with your ERP or accounting, and shipments go out automatically.
What do we connect?
orders, products, inventory, customers
API
REST · JSON
Sign-in
API key · OAuth 2.0
Webhooks
No, we poll
Timing
In batches
The Webservice under /api/ (XML by default) with a webservice key as the basic auth user. PrestaShop 9 also has an Admin API with OAuth 2.0 (client credentials).
What we watch out for: No built-in webhooks: we poll for changes on a fixed schedule, or add a small module that sends a signal.
WordPress
What is it?
The most widely used system for managing websites (a CMS). Also the foundation under WooCommerce.
Who is it for?
Organizations with a WordPress website.
What does an integration get you?
Forms become contacts in your CRM, sign-ups land in your mailing list, and content from other systems appears on your site automatically.
What do we connect?
pages, forms, users, files
API
REST · JSON
Sign-in
Basic auth · Session
Webhooks
No, we poll
Timing
Real time or in batches
REST API (wp/v2 under /wp-json/). Sign-in with a cookie plus nonce, or with an Application Password over HTTPS. No webhooks in core; they come from plugins or from us.
What we watch out for: Plugins add their own fields and endpoints. We use a dedicated, locked-down user with only the permissions the integration needs.
Lightspeed
What is it?
POS system for retail (Retail) and hospitality (Restaurant), with its own webshop (eCom).
Who is it for?
Stores, cafés and restaurants with a Lightspeed POS.
What does an integration get you?
What you sell in the store comes off the online inventory, and vice versa. POS sales land in your accounting automatically.
What do we connect?
orders, products, inventory, customers, payments
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time
Each series has its own API: Retail X-Series and R-Series (REST, OAuth 2.0), Restaurant K-Series (OAuth 2.0 with scopes) and eCom C-Series (API key and secret). X-Series sends signed webhooks, e.g. on a sale or inventory change.
What we watch out for: Which Lightspeed do you have? That determines the API. R-Series uses a leaky bucket limit; we follow the headers and adjust our pace.
bol
bol.com
What is it?
The largest online store in the Netherlands and Belgium, where you sell your products as a partner.
Who is it for?
Webshops and brands that also sell through bol.
What does an integration get you?
Your inventory is correct on your webshop and on bol, and bol orders land in your shipping and accounting.
What do we connect?
orders, offers, inventory, shipments, returns
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time or in batches
Retailer API (v10) with JSON and a version in the Accept header. Sign-in with OAuth 2.0 client credentials; the token is valid for about 5 minutes. Push notifications via webhook or a queue, signed with RSA.
What we watch out for: Every endpoint has its own limit, and many actions run asynchronously (you get a process ID). We track the status until bol confirms.
Amazon
Amazon Seller Central
What is it?
The global marketplace where you offer your products as a seller, and ship them yourself or let Amazon ship them.
Who is it for?
Brands and webshops that want to sell in other European countries.
What does an integration get you?
Inventory and orders stay in sync between your webshop and Amazon, and invoices go to your accounting automatically.
What do we connect?
orders, offers, inventory, shipments, reports
API
REST · JSON
Sign-in
Login with Amazon
Webhooks
Yes
Timing
Real time or in batches
Selling Partner API (SP-API): REST with Login with Amazon tokens (x-amz-access-token), with its own host per region. Notifications via Amazon SQS or EventBridge. Personal data requires a Restricted Data Token.
What we watch out for: Amazon updates its APIs regularly (the old Orders API v0 has been phased out). We follow the announcements and build on the current version.
Sendcloud
What is it?
A shipping platform for webshops: labels from bpost, PostNL, DHL, DPD and more from one screen, with returns and tracking.
Who is it for?
Webshops that ship with multiple carriers.
What does an integration get you?
A paid order becomes a label automatically, and the customer gets the tracking link. No more retyping addresses.
What do we connect?
shipments, shipping labels, tracking, returns
API
REST · JSON
Sign-in
Basic auth · OAuth 2.0
Webhooks
Yes
Timing
Real time
REST API v3 (v2 is in maintenance mode). Sign-in with basic auth (public and secret key) or OAuth 2.0. Webhooks with Sendcloud-Signature (HMAC-SHA256), e.g. on a new status.
What we watch out for: Write operations are more limited than reads (per minute). We create labels in batches and retry after an error without creating duplicate labels.
bpost
What is it?
The Belgian postal service: parcels delivered to the door, to a pickup point or to a parcel locker.
Who is it for?
Webshops that ship within Belgium and abroad.
What does an integration get you?
Orders become bpost labels without retyping, and the customer gets the tracking link.
What do we connect?
shipments, shipping labels, tracking
API
XML over HTTPS
Sign-in
Account ID + passphrase
Webhooks
No, we poll
Timing
Real time or in batches
The Shipping Manager web services with XML (per bpost’s XSDs). Sign-in with your account ID and a passphrase from the Shipping Manager portal. Many webshops use bpost via Sendcloud.
What we watch out for: Integrating directly requires a bpost contract and a configured Shipping Manager account. Together we look at whether direct or via a shipping platform fits best.
PostNL
What is it?
The Dutch postal service, also active in Belgium, with parcels and pickup points.
Who is it for?
Webshops with customers in the Netherlands and Belgium.
What does an integration get you?
Labels and tracking without retyping, for Dutch customers too.
What do we connect?
shipments, shipping labels, tracking
API
REST · JSON
Sign-in
API key
Webhooks
No, we poll
Timing
Real time or in batches
REST API with an API key in the header (apikey) and a separate sandbox. The Labelling and Shipping APIs create the shipment, barcode and label in one step.
What we watch out for: PostNL updates its API regularly (maximum shipments per call, old options being retired). We follow the changelog and update the integration in time.
DHL
DHL eCommerce Benelux and DHL Express
What is it?
Parcels in the Benelux (DHL eCommerce) and worldwide express (DHL Express).
Who is it for?
Webshops that ship within the Benelux or fast internationally.
What does an integration get you?
Labels and tracking without retyping, and status updates that land in your system automatically.
What do we connect?
shipments, shipping labels, tracking
API
REST · JSON
Sign-in
API key · Token
Webhooks
Yes
Timing
Real time
DHL eCommerce Benelux: REST, you exchange a user ID and key for a bearer token; status updates via the Track and Trace Pusher. DHL Express: the MyDHL API with basic auth and a test environment.
What we watch out for: Two DHLs, two APIs and two contracts. First we check which DHL you use.
DPD
What is it?
Parcel service with a large network of pickup points across Europe.
Who is it for?
Webshops that ship with DPD.
What does an integration get you?
Orders become DPD labels, and the status comes back into your system.
What do we connect?
shipments, shipping labels, tracking
API
SOAP · XML
Sign-in
Token
Webhooks
No, we poll
Timing
Real time or in batches
DPD Belgium: the Shipper Webservices, SOAP only. You sign in with a delisId and password and get an authToken valid for one business day. There is a test environment with separate access.
What we watch out for: You can only sign in a few times per day, and there are per-minute limits. We store the token securely and reuse it instead of signing in again every time.
GLS
What is it?
Parcel service with a strong European network.
Who is it for?
Webshops that ship with GLS.
What does an integration get you?
Labels and tracking without retyping.
What do we connect?
shipments, shipping labels, tracking
API
REST · JSON
Sign-in
Basic auth
Webhooks
No, we poll
Timing
Real time or in batches
GLS ShipIT: REST (POST /backend/rs/shipments) with basic auth; you get the host from your GLS contact. GLS is rolling out a new developer portal.
What we watch out for: The documentation is moving to the new portal. We work with the details GLS gives you with your contract and test in their test environment first.
UPS
What is it?
Worldwide parcel and express service.
Who is it for?
Webshops that ship internationally, including outside the EU.
What does an integration get you?
Labels, customs documents and tracking without retyping.
What do we connect?
shipments, shipping labels, tracking
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time or in batches
REST API with OAuth 2.0 (client credentials) and a version in the path (e.g. v2409). There is a test environment (CIE). Status updates via the Track Alert webhooks.
What we watch out for: Outside the EU, customs data is required (HS codes, value, origin). We make sure it’s in your system for each product before we create labels.
Mailchimp
What is it?
Email marketing: newsletters, automated emails and audiences.
Who is it for?
Companies that send newsletters and automated emails.
What does an integration get you?
Customers and subscribers land in the right list automatically, with their purchases, so you can send targeted emails.
What do we connect?
subscribers, audiences, campaigns, orders
API
REST · JSON
Sign-in
API key · OAuth 2.0
Webhooks
Yes
Timing
Real time
Marketing API v3 per data center (e.g. us21.api.mailchimp.com). Sign-in with an API key or OAuth 2.0. Webhooks per list, optionally signed.
What we watch out for: Only 10 connections may be open at the same time. We sync in batches and respect the choice of anyone who unsubscribed (GDPR).
Brevo
formerly Sendinblue
What is it?
Email and SMS marketing and transactional emails, from Europe.
Who is it for?
Small businesses that want to send newsletters and automated emails.
What does an integration get you?
Customers, orders and sign-ups flow into Brevo automatically, and confirmation emails go out from your own systems.
What do we connect?
subscribers, audiences, campaigns, emails
API
REST · JSON
Sign-in
API key · OAuth 2.0
Webhooks
Yes
Timing
Real time
REST API v3 with an api-key header or OAuth 2.0. Webhooks for transactional and marketing emails; they aren’t signed, so we secure them with a token or IP list.
What we watch out for: Contact attributes (like FIRSTNAME) have to be created in Brevo first. We define them together before we sync.
Klaviyo
What is it?
Email and SMS marketing for webshops, strong in automated flows based on purchases.
Who is it for?
Webshops that rely heavily on personalized emails.
What does an integration get you?
Purchases, visits and customer data flow into Klaviyo automatically, so your flows run on real data.
What do we connect?
subscribers, events, audiences, campaigns
API
REST · JSON:API
Sign-in
API key · OAuth 2.0
Webhooks
Limited
Timing
Real time
REST API following the JSON:API standard, with a private API key (Klaviyo-API-Key) and a date-based revision header. Webhooks are only available on certain plans and for app partners.
What we watch out for: Each revision is stable for a year and then phased out. We record the revision in the integration and plan the upgrade.
Meta
Facebook and Instagram
What is it?
The advertising and sales channels of Facebook and Instagram, and the product catalog for your ads.
Who is it for?
Companies that advertise on Facebook or Instagram.
What does an integration get you?
Purchases are measured reliably, even without cookies in the browser, and your product catalog stays up to date automatically.
What do we connect?
conversions, products, audiences, messages
API
Graph API
Sign-in
Token
Webhooks
Yes
Timing
Real time or in batches
Graph API with versions (e.g. v26.0). The Conversions API receives events from your server, with email and phone hashed (SHA-256). Catalog via items_batch. Sign-in with a system user token.
What we watch out for: The same purchase can come in via both the pixel and the server. We send an event_id so Meta merges them, and only with the visitor’s consent.
Google Ads
What is it?
Advertising on Google Search, YouTube and the Display Network.
Who is it for?
Companies that advertise on Google.
What does an integration get you?
Your campaign results land in your own reports, and offline sales can go back to Google.
What do we connect?
campaigns, conversions, reports
API
REST · JSON · gRPC
Sign-in
OAuth 2.0
Webhooks
No, we poll
Timing
In batches
Google Ads API via gRPC or REST, with OAuth 2.0 and queries in GAQL. New versions come out regularly and old ones expire. For new integrations that upload offline conversions, Google recommends the Data Manager API.
What we watch out for: Every API version has an end date. We keep track of it and migrate in time.
Google Analytics
Google Analytics 4
What is it?
Website analytics: visitors, sources and conversions.
Who is it for?
Every organization with a website or webshop.
What does an integration get you?
Even purchases that don’t happen in the browser (a payment confirmed later, a sale in the store) show up in your numbers.
What do we connect?
events, conversions, reports
API
REST · JSON
Sign-in
API key · OAuth 2.0
Webhooks
No, we poll
Timing
Real time or in batches
Measurement Protocol: events from your server to /mp/collect with a measurement_id and api_secret (which stays on the server). Fetch the numbers via the Data API with OAuth 2.0.
What we watch out for: Server events have to be tied to the right visitor (client_id). We store it with the order and only send what the visitor consented to.
Slack
What is it?
Chat for teams, with channels per topic.
Who is it for?
Teams that work together in Slack.
What does an integration get you?
An alert in the right channel for a large order, a failed payment or low inventory.
What do we connect?
messages, notifications
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time
Web API (e.g. chat.postMessage) with a bot token via OAuth and scopes, the Events API for what happens in Slack, and incoming webhooks. Requests from Slack are signed (X-Slack-Signature).
What we watch out for: About one message per second per channel. We bundle notifications and only send what really needs action.
Microsoft Teams
Microsoft Teams
What is it?
Chat, meetings and collaboration within Microsoft 365.
Who is it for?
Organizations that work with Microsoft 365.
What does an integration get you?
Alerts in the right channel: a new large order, an invoice that didn’t go out, an integration that’s briefly hiccuping.
What do we connect?
messages, notifications
API
Graph API
Sign-in
Microsoft Entra ID
Webhooks
Yes
Timing
Real time
Microsoft Graph for messages and channels, sign-in via Entra ID. For simple notifications, you use a webhook from the Workflows app (Power Automate). The old Office 365 connectors no longer work.
What we watch out for: Posting messages via Graph requires a signed-in user. That’s why we choose a Workflows webhook or a bot for automated notifications.
WhatsApp
WhatsApp Business Platform
What is it?
Messages via WhatsApp from your business to customers: confirmations, shipping updates and customer service.
Who is it for?
Businesses whose customers would rather text than email.
What does an integration get you?
A shipping update or appointment reminder via WhatsApp, sent automatically from your own systems.
What do we connect?
messages, notifications, tracking
API
Graph API
Sign-in
Token
Webhooks
Yes
Timing
Real time
Cloud API via Meta’s Graph API with a system user token. Outside the 24-hour customer service window, you can only send approved templates. Webhooks with X-Hub-Signature-256 for incoming messages and statuses.
What we watch out for: Templates have to be approved by Meta in advance. We create them with you and keep them short and useful.
Twilio
What is it?
A platform for SMS, voice and messaging via an API.
Who is it for?
Companies that want SMS notifications or telephony in their software.
What does an integration get you?
SMS reminders and confirmations from your own system, with no manual work.
What do we connect?
messages, notifications
API
REST · JSON
Sign-in
Basic auth
Webhooks
Yes
Timing
Real time
REST API (form-encoded) with basic auth: your Account SID and Auth Token, or better, an API key. Webhooks signed with X-Twilio-Signature. Test credentials and test numbers for safe testing.
What we watch out for: Sender names and numbers have rules per country. We check what’s allowed in Belgium and your target countries before we go live.
Microsoft Outlook
Microsoft Outlook
What is it?
Email, calendar and contacts from Microsoft 365.
Who is it for?
Organizations that work with Microsoft 365.
What does an integration get you?
Invoices go out from your own mailbox, appointments appear in your calendar, and incoming emails become tasks or tickets.
What do we connect?
emails, appointments, contacts
API
Graph API
Sign-in
Microsoft Entra ID
Webhooks
Yes
Timing
Real time
Microsoft Graph (/sendMail, /messages, /events), sign-in via Entra ID with OAuth 2.0. Changes via Graph subscriptions with a validation step and a clientState secret; subscriptions expire and are renewed.
What we watch out for: We request the narrowest possible permissions (e.g. only Mail.Send) and limit access to the mailboxes that need it.
Gmail
What is it?
Email from Google, also as business email in Google Workspace.
Who is it for?
Organizations that work with Google Workspace.
What does an integration get you?
Incoming orders or purchase invoices by email are processed automatically, and emails go out from your own address.
What do we connect?
emails, files
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time
Gmail API with OAuth 2.0. Push notifications via Google Cloud Pub/Sub (users.watch), which you renew at least every seven days; you then fetch the changes with the historyId.
What we watch out for: Broad Gmail permissions are “restricted” and require a security assessment by Google. That’s why we only request the permissions the integration really needs.
itsme
What is it?
The Belgian app for confirming your identity: signing in, sharing your details and signing.
Who is it for?
Companies that want customers to sign in securely or need to verify their identity.
What does an integration get you?
Customers sign in or sign with itsme, without a password, and you know for sure who they are.
What do we connect?
sign-ins, users, signatures
API
OpenID Connect
Sign-in
OIDC · Certificate
Webhooks
Not applicable
Timing
Real time
OpenID Connect (authorization code flow) with signed and optionally encrypted request objects (private_key_jwt, RS256). The ID token and userinfo come back signed and encrypted. You first sign a contract via the itsme partner portal.
What we watch out for: Keys and certificates need to be managed properly (JWKS with keys for signing and encryption). We build in the rotation of those keys.
CSAM
What is it?
The way you sign in to online government services, with eID, itsme or another digital key. The federal sign-in service is called FAS.
Who is it for?
Government bodies and organizations that offer a secure online government application.
What does an integration get you?
Citizens and businesses sign in with the keys they already know, and you know who they are.
What do we connect?
sign-ins, users
API
OpenID Connect · SAML 2.0
Sign-in
OIDC
Webhooks
Not applicable
Timing
Real time
FAS from FPS BOSA supports OpenID Connect (recommended) and SAML. You request access from BOSA, which decides per request; it’s intended for government-related applications. For regular business apps, itsme is the more obvious choice.
What we watch out for: The application and the contract with BOSA take time. We factor that into the planning and test in the test environment first.
Microsoft Entra ID
formerly Azure AD
What is it?
The user accounts of Microsoft 365: who works at your company and what they can access.
Who is it for?
Organizations that work with Microsoft 365.
What does an integration get you?
Your team signs in to your own software with their Microsoft account (single sign-on), and anyone who leaves instantly loses access everywhere.
What do we connect?
sign-ins, users, groups
API
OpenID Connect · SAML 2.0 · SCIM 2.0
Sign-in
OAuth 2.0 · OIDC
Webhooks
Yes
Timing
Real time
OpenID Connect and OAuth 2.0 (or SAML 2.0) for sign-in, SCIM 2.0 to automatically create and block users and groups. Entra then calls your /Users and /Groups endpoints.
What we watch out for: Roles and groups have to be mapped correctly to the permissions in your software, once. We document that and test it with real accounts.
Sign in with Google
Sign in with Google
What is it?
Signing in with your Google account, in one click.
Who is it for?
Webshops and apps that want to make signing in easy, and teams using Google Workspace.
What does an integration get you?
Customers don’t create yet another password, and your team signs in with their Google Workspace account.
What do we connect?
sign-ins, users
API
OpenID Connect
Sign-in
OIDC
Webhooks
Not applicable
Timing
Real time
Google Identity Services, built on OpenID Connect: you get a signed ID token (JWT). We check the signature, aud, iss and exp, and use sub as the stable key.
What we watch out for: An email address can change, sub can’t. That’s why we link accounts to sub and not to the email address.
Microsoft 365
What is it?
Office in the cloud: Outlook, Teams, OneDrive, SharePoint, Excel and your team’s accounts.
Who is it for?
Organizations that work with Microsoft.
What does an integration get you?
Emails, calendars, files and users from Microsoft 365 work together with your own software.
What do we connect?
emails, appointments, files, users
API
Graph API
Sign-in
Microsoft Entra ID
Webhooks
Yes
Timing
Real time
Everything via one API: Microsoft Graph (REST, OData), sign-in via Entra ID with OAuth 2.0 (on behalf of a user or as an application). Changes via subscriptions (change notifications).
What we watch out for: Application permissions apply to the whole organization by default. We limit them to the mailboxes or sites that are needed.
Microsoft SharePoint
Microsoft SharePoint
What is it?
The document libraries and lists of Microsoft 365, often a company’s intranet.
Who is it for?
Organizations that store documents centrally in Microsoft 365.
What does an integration get you?
Invoices, contracts and reports land in the right folder automatically, and lists stay in sync with your other systems.
What do we connect?
files, documents, rows
API
Graph API
Sign-in
Microsoft Entra ID
Webhooks
Yes
Timing
Real time or in batches
Via Microsoft Graph: sites, lists (list items with fields) and document libraries (drives). Sign-in via Entra ID; permissions can be limited per site (Sites.Selected).
What we watch out for: Filtering works best on indexed columns. For large lists, we set up the right indexes first.
Microsoft Excel
Microsoft Excel
What is it?
The spreadsheet every business uses, often as an inventory list, price list or schedule.
Who is it for?
Anyone who still copies numbers between Excel and other programs.
What does an integration get you?
Your Excel stays in sync with your webshop or accounting automatically, until you’re ready to replace the sheet with real software.
What do we connect?
rows, inventory, prices, reports
API
Graph API
Sign-in
Microsoft Entra ID
Webhooks
Limited
Timing
In batches
Microsoft Graph Excel API on files in OneDrive for Business or SharePoint (.xlsx only): read and write ranges, tables and rows, with a workbook session.
What we watch out for: Someone might move a column or rename a sheet. We work with named tables and check the columns before every sync.
Google Sheets
What is it?
Google’s spreadsheet, online and editable together.
Who is it for?
Teams that work with Google Workspace.
What does an integration get you?
Orders, leads or inventory land in your sheet as rows automatically, and changes in the sheet can flow back.
What do we connect?
rows, orders, reports
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Limited
Timing
Real time or in batches
Sheets API v4 (REST) with OAuth 2.0: read and update values and append rows (values.append). For notifications on a change, you use the Drive API.
What we watch out for: There is a limit per minute, per project and per user. We write in batches and retry after a 429 with exponential backoff.
Google Workspace
What is it?
Gmail, Calendar, Drive, Docs and your team’s accounts at Google.
Who is it for?
Organizations that work with Google.
What does an integration get you?
New employees get access automatically, anyone who leaves loses it, and calendars and email work together with your software.
What do we connect?
users, groups, emails, appointments
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time or in batches
A separate REST API per service (Gmail, Calendar, Drive…) and the Admin SDK Directory API for users and groups, all with OAuth 2.0. Organization-wide access via a service account with domain-wide delegation.
What we watch out for: Domain-wide delegation is powerful. We limit it to the strictly necessary scopes, and your administrator approves them.
Google Drive
What is it?
File storage from Google, with shared folders for your team.
Who is it for?
Teams that work with Google Workspace.
What does an integration get you?
Invoices and documents land in the right folder automatically, and new files in a folder start a process (e.g. a purchase invoice to accounting).
What do we connect?
files, documents
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time
Drive API v3 with OAuth 2.0. Push notifications via watch channels (web_hook) that expire after a day or a week; the notification only says that something changed, then we fetch the changes.
What we watch out for: Channels expire silently. Our integration renews them in time and, when in doubt, fetches the changes via the changes list.
Microsoft OneDrive
Microsoft OneDrive
What is it?
File storage from Microsoft 365, personal and shared.
Who is it for?
Organizations that work with Microsoft 365.
What does an integration get you?
Documents land in the right folder automatically, and a new file can start a process.
What do we connect?
files, documents
API
Graph API
Sign-in
Microsoft Entra ID
Webhooks
Yes
Timing
Real time or in batches
Microsoft Graph (driveItem). With delta queries, we only fetch what changed since last time; a notification via a Graph subscription gives the signal.
What we watch out for: A delta token can expire (HTTP 410). We then do one full comparison and continue with a new token.
Dropbox
What is it?
File storage and sharing, popular with creative teams and accounting firms.
Who is it for?
Teams that keep their documents in Dropbox.
What does an integration get you?
A purchase invoice in a Dropbox folder lands in your accounting automatically, and documents from your software go into the right folder.
What do we connect?
files, documents
API
RPC over HTTPS
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time or in batches
API v2 in RPC style (POST with JSON), OAuth 2.0 with short-lived tokens and a refresh token. Webhooks only report which account changed, signed with X-Dropbox-Signature; we fetch the changes with a cursor.
What we watch out for: File names and folders change. We track files by their ID, not by their path.
Docusign
What is it?
Getting documents signed digitally: contracts, quotes, forms.
Who is it for?
Companies that have lots of contracts or quotes signed.
What does an integration get you?
A quote goes out for signature automatically, and a signed contract comes back into your CRM and document folder.
What do we connect?
documents, signatures, quotes
API
REST · JSON
Sign-in
OAuth 2.0
Webhooks
Yes
Timing
Real time
eSignature REST API v2.1 with OAuth 2.0 (authorization code or JWT). Status updates via Connect webhooks, signed with HMAC-SHA256 (X-DocuSign-Signature-1).
What we watch out for: There is a limit per hour per account. We use Connect webhooks instead of repeatedly polling the status.
Notion
What is it?
A workspace for notes, wikis and databases (lists with properties).
Who is it for?
Teams that organize their processes and knowledge in Notion.
What does an integration get you?
New customers, tasks or projects appear in your Notion database automatically, and changes flow back to your other tools.
What do we connect?
pages, rows, tasks
API
REST · JSON
Sign-in
Token · OAuth 2.0
Webhooks
Yes
Timing
Real time
REST API with a Notion-Version header and an integration token or OAuth. Webhooks report changes, signed (X-Notion-Signature). Since version 2025-09-03, databases work with data sources.
What we watch out for: The limit is around three requests per second (higher on Business). We spread out requests and retry cleanly after a 429.
Airtable
What is it?
A spreadsheet that’s a database: tables with links, views and forms.
Who is it for?
Teams that build their own lightweight tools without coding.
What does an integration get you?
Your Airtable base stays in sync with your webshop, CRM or accounting, without copying.
What do we connect?
rows, products, inventory
API
REST · JSON
Sign-in
Token · OAuth 2.0
Webhooks
Yes
Timing
Real time or in batches
REST API with personal access tokens or OAuth and scopes. Webhooks report that something changed (signed with X-Airtable-Content-MAC); we then fetch the changes. Webhooks expire after seven days unless you renew them.
What we watch out for: Five requests per second per base, and at most 10 records per write. We write in chunks and respect the wait time after a 429.
Zapier
What is it?
A no-code tool that lets apps talk to each other: “if this happens, do that”.
Who is it for?
Small businesses with simple flows between two or three apps.
What does an integration get you?
A simple flow, fast, without coding. Hitting the limits (high volume, complex rules, error handling)? Then we turn your Zaps into a custom integration.
What do we connect?
events, rows, notifications
API
REST · JSON
Sign-in
API key · OAuth 2.0
Webhooks
Yes
Timing
Real time
Zaps with triggers and actions; Webhooks by Zapier gives you a URL that receives data. You pay per task (every successful action). We can also build a dedicated Zapier integration for your software.
What we watch out for: At high volume, tasks and costs add up fast, and errors only surface when someone notices. Together we look at when custom work is cheaper and more reliable.
Make
formerly Integromat
What is it?
A visual no-code tool for automations (scenarios) between apps.
Who is it for?
Teams that want to draw their flows without coding.
What does an integration get you?
Build and adjust a flow quickly. Getting complex or critical? Then we take over the scenarios in a custom integration.
What do we connect?
events, rows, notifications
API
REST · JSON
Sign-in
Token
Webhooks
Yes
Timing
Real time
Scenarios with modules, custom webhooks per region (e.g. hook.eu1.make.com) and its own API. You pay in credits: most actions cost one credit.
What we watch out for: Scenarios often grow into something nobody can oversee anymore. We document what’s running before we take anything over or replace it.
n8n
What is it?
An automation tool you can also run on your own server.
Who is it for?
Technical teams that want to host their data themselves.
What does an integration get you?
Flows running on your own server, with your data in-house. We can build them for you, host them, or later replace them with custom work.
What do we connect?
events, rows, notifications
API
REST · JSON
Sign-in
API key
Webhooks
Yes
Timing
Real time or in batches
Workflows with nodes, webhook triggers and a REST API. Self-hosting falls under the Sustainable Use License: allowed for internal use, not for selling as a service to your own customers.
What we watch out for: Self-hosting means updating, backing up and monitoring yourself. We include that in maintenance.
Microsoft Power Automate
Microsoft Power Automate
What is it?
Microsoft 365’s automation tool: flows in the cloud and on the desktop.
Who is it for?
Organizations that work with Microsoft 365.
What does an integration get you?
Simple flows within Microsoft 365 without coding. For heavy or critical integrations, we build custom work that calls or replaces Power Automate.
What do we connect?
events, files, notifications
API
REST · JSON
Sign-in
Microsoft Entra ID
Webhooks
Yes
Timing
Real time or in batches
Cloud flows with connectors; the “When an HTTP request is received” trigger can be secured with Entra ID (OAuth), instead of an open URL with a secret key.
What we watch out for: Premium connectors require an extra license. We check up front which licenses you need.
Power BI
Microsoft Power BI
What is it?
Reports and dashboards from Microsoft, on your own numbers.
Who is it for?
Business owners and teams who want their numbers in one overview.
What does an integration get you?
Sales, margins and inventory from all your systems in one dashboard, updated automatically.
What do we connect?
datasets, reports, rows
API
REST · JSON
Sign-in
Microsoft Entra ID
Webhooks
No, we poll
Timing
In batches
Power BI REST API with Entra ID (or a service principal). Push data into a push semantic model (rows via POST), or let Power BI read from a database or view that we set up.
What we watch out for: Push models have limits per hour and per table. For larger volumes, we set up a database or view that Power BI reads from itself.
Looker Studio
Google Looker Studio
What is it?
Free reports and dashboards from Google.
Who is it for?
Small businesses that want to visualize their numbers, often together with Google Analytics and Google Ads.
What does an integration get you?
Webshop, accounting and marketing numbers in one free dashboard.
What do we connect?
datasets, reports
API
Connectors
Sign-in
OAuth 2.0
Webhooks
No, we poll
Timing
In batches
Looker Studio reads via connectors (Google Sheets, BigQuery, databases such as PostgreSQL) or a custom community connector in Apps Script. The Looker Studio API only manages reports; it doesn’t read data.
What we watch out for: Reading directly from a busy database can be slow. We set up a separate view or table with the numbers the report needs.
PostgreSQL
What is it?
A reliable open-source database, under a lot of custom software.
Who is it for?
Companies with their own software or their own database.
What does an integration get you?
Your software has no API? Then we read safely straight from the database, or build an API on top of it.
What do we connect?
rows, datasets, events
API
SQL
Sign-in
Database user
Webhooks
Limited
Timing
Real time or in batches
SQL over PostgreSQL’s own protocol, via a user with read-only permissions (e.g. the pg_read_all_data role). Changes can be passed on with LISTEN/NOTIFY or with logical replication.
What we watch out for: Writing to another package’s database can break that package. We only read, or write via an API or a separate table that the package processes itself.
CODA
Coded Statement of Account
What is it?
The Belgian file format for bank statements, agreed between the banks (Febelfin). Your accountant receives them every day.
Who is it for?
Every Belgian company with a business bank account.
What does an integration get you?
Payments are reconciled against your invoices automatically, without retyping statements.
What do we connect?
bank transactions, balances, payments
API
Files
Sign-in
Not applicable
Webhooks
Not applicable
Timing
In batches
A text file with fixed-width lines (128 characters), version 2: header (0), old balance (1), transactions (2.1–2.3), extra information (3.1–3.3), new balance (8), free message (4) and trailer (9). You get it via your bank, Isabel or your accounting software.
What we watch out for: The structured communication (+++…+++) is the key to matching a payment to an invoice. We make sure your invoices actually include that communication.
Ponto
Isabel Group
What is it?
A Belgian open banking service: you give software permission to read your accounts or prepare payments, under the European PSD2 rules.
Who is it for?
Small businesses and software that want to process bank transactions automatically.
What does an integration get you?
Payments land in your software the same day and are matched to invoices automatically.
What do we connect?
bank transactions, balances, payments
API
REST · JSON:API
Sign-in
OAuth 2.0 · Certificate
Webhooks
Yes
Timing
Real time or in batches
REST API following JSON:API. OAuth 2.0 with PKCE for the customer’s consent, and on every call mutual TLS with a client certificate plus an HTTP signature. Webhooks on new transactions. There is a sandbox.
What we watch out for: The customer’s consent has to be renewed periodically. We send a reminder in time and show the status clearly.
Isabel
Isabel 6 and Isabel Connect
What is it?
Belgian software for managing all your accounts at different banks in one place.
Who is it for?
Small businesses and larger companies with accounts at multiple banks.
What does an integration get you?
Statements (CODA) and balances land in your accounting or ERP automatically, and payment files go to the bank without uploading.
What do we connect?
bank transactions, balances, payments
API
REST · JSON · Files
Sign-in
OAuth 2.0 · Certificate
Webhooks
Limited
Timing
In batches
Isabel Connect: REST API with OAuth 2.0 and a client certificate (mutual TLS). You read balances, transactions and account reports (CODA, camt.053, MT940) and send payment files (PAIN XML). Requires an Isabel 6 license with the Connect option.
What we watch out for: Payments are still signed by you in Isabel: the integration prepares them, it doesn’t execute them itself.
Don’t see your system? If it has an API, we’ll connect it. If it doesn’t, we’ll find another way (an export, a file via SFTP, an integration on your own server) or build the API.
Brand names and logos belong to their owners; they show which systems we connect to, not that we are their partner. Technical details checked against each vendor’s documentation (September 2026); vendors change their APIs regularly.
API, OAuth, EDI, idempotency? The jargon, translated.
Your IT team, your accountant and every vendor throw acronyms around. Here they all are, each explained two ways: in plain words for you, and precisely for your IT team. Every term comes with a small example that really works: click it.
1In plain words
One sentence, often with a comparison from everyday life. And why it matters to you.
2Technical
Just enough for your IT team: the standard, the protocol, the pitfall.
3Try it
A small, working example with the data of a coffee roaster.
Connecting6
Formats4
Security4
Reliability4
Standards3
How we work5
Swipe for more terms
API
Application Programming Interface
HTTPS
JSON
200 · 404
In plain words
A program’s service entrance. Other software rings the bell, asks for something by fixed rules and gets a clean answer back, without anyone retyping anything.
For you: If your software has an API, we can integrate it. If it doesn’t, we find another way.
Technical</>
A defined interface through which programs use each other’s data and functions. For web integrations, almost always HTTPS requests with a method, a path, headers and a body; the response has a status code (200, 404…) and usually JSON.
You’ll find it in
Exact
Mollie
Shopify
Sendcloud
1 of 26
Try it · The webshop API
Demo · Koffiebranderij VennegemSimplified
Loading example…
REST
Representational State Transfer
In plain words
An agreement on how to build an API neatly: everything has its own address (like an order), and a handful of fixed verbs say what you do with it: read, create, replace, change or delete.
For you: Most modern software (Exact Online, Teamleader, Mollie…) works this way. That makes an integration predictable.
Technical
An architectural style on top of HTTP: resources with a URL, manipulated with methods (GET, POST, PUT, PATCH, DELETE) and status codes. Per RFC 9110, GET is safe (changes nothing) and GET, PUT and DELETE are idempotent (twice = same effect); POST is not, and PATCH (RFC 5789) isn’t inherently either.
SOAP
Simple Object Access Protocol
In plain words
The older, formal way to talk to a program: every message sits in a fixed XML ‘envelope’, with a prescribed form for request, response and error.
For you: Many older ERP, logistics and government systems still speak SOAP. No problem: we speak it too.
Technical
An XML messaging protocol, usually over HTTP POST. Every message is an Envelope with an optional Header and a required Body; errors come back as a Fault. A WSDL file describes the operations and types. SOAP 1.2 uses the namespace http://www.w3.org/2003/05/soap-envelope and the media type application/soap+xml.
GraphQL
In plain words
An API where you choose what you get back, like an order form where you only check what you need. No more, no less.
For you: Shopify works this way. Less unnecessary data means faster, leaner integrations.
Technical
A query language for APIs with a single endpoint (usually POST /graphql) and a typed schema. The client describes the fields it wants; the response has exactly that shape, under "data" (and any "errors"). Changes are called mutations.
Webhook
In plain words
A doorbell instead of going to check every time. One system rings the other as soon as something happens, like a new order.
For you: Your invoice, shipping label and stock follow right away, not at the next check.
Technical
An HTTP POST callback a system sends to a URL of yours when an event occurs. The receiver verifies the signature, responds quickly with 2xx and handles the work in a queue. Senders retry on failure, so processing must be idempotent. The alternative is polling: asking over and over whether there’s anything new.
SFTP
SSH File Transfer Protocol
In plain words
A secure mailbox for files. Systems without an API drop a file in it at night and pick up a reply.
For you: That’s how we also integrate older software, wholesalers and logistics partners that don’t have an API (yet).
Technical
File transfer over an encrypted SSH connection, port 22 by default, with sign-in via a key pair (e.g. ed25519). Not to be confused with FTPS (FTP over TLS). Typically: CSV or XML in an agreed folder, at a set time, with archive and error folders.
JSON
JavaScript Object Notation
In plain words
A list in a fixed shape: always a name and a value, neatly between brackets. Readable for people, and unambiguous for computers.
For you: It’s the language in which almost every modern API passes on your orders, customers and invoices.
Technical
A text format (RFC 8259) with objects, lists (arrays), strings, numbers, true, false and null. Always UTF-8 between systems. Numbers have no currency or fixed decimals, so we agree on amounts explicitly (e.g. "70.65" as a string, or in cents).
XML
Extensible Markup Language
In plain words
A format in which every piece of data sits between an opening and a closing tag, like <price>26.90</price>. A bit longer, but very strict to check.
For you: E-invoices (Peppol), bank files and many older systems use XML.
Technical
A markup language with nested elements, attributes and namespaces. A schema (XSD) defines the structure; rules on top (like Schematron for Peppol) check the content. The basis of SOAP and UBL.
CSV
Comma-Separated Values
In plain words
A table as plain text: one line per row, the columns separated by a character. Excel opens it right away.
For you: Handy for exports and imports, but the delimiter and the comma in amounts often cause errors. We agree on the format up front.
Technical
A simple table format (RFC 4180: comma as delimiter; fields containing a comma, quote or line break go between double quotes). In Belgium, Excel often uses the semicolon, because the comma is the decimal separator. No types: everything is text until you agree otherwise.
CODA
Coded Statement of Account
In plain words
The Belgian format for your bank statements as a file. Every payment sits on a fixed line, with every piece of data in a fixed place.
For you: Your accountant uses it to match payments to invoices automatically, especially with a structured communication (+++…+++).
Technical
The Febelfin standard format for Belgian bank statements: text lines of exactly 128 characters, with a record type up front (0 = header, 1 = old balance, 2.x = movement, 3.x = extra info, 4 = free communication, 8 = new balance, 9 = trailer). Every field has a fixed position.
API key
In plain words
A secret code a program sends along to prove it may come in. Like a badge: whoever has it gets in, so you keep it safe.
For you: We store your keys encrypted, never in emails or in the code, and replace them when needed.
Technical
A long, random secret, usually in a header (Authorization: Bearer … or X-API-Key). Simple, but without an expiry date or limited rights, unless the vendor provides them. Hence: a separate key per environment, minimal rights, rotation, and revocation when in doubt.
OAuth 2.0
In plain words
Granting access without handing over your password. You sign in to your own software, click ‘Allow’, and the integration gets a temporary key with only the rights you approved.
For you: You can revoke that access at any time, and none of us knows your password.
Technical
An authorization standard (RFC 6749). In the authorization code flow with PKCE (RFC 7636), the integration sends you to the authorization server, receives a one-time code after your consent and exchanges it for a short-lived access token and a refresh token, limited to the requested scopes. We store tokens encrypted.
HMAC signature
In plain words
A digital seal on a message. Only someone who knows the secret can make the right seal; if a single character changes on the way, the seal no longer matches.
For you: That’s how we know for sure a ‘paid’ notification really comes from your payment provider, and not from a scammer.
Technical
A hash-based message authentication code (RFC 2104), usually HMAC-SHA256 over the raw body (sometimes prefixed with a timestamp, against replay). The receiver recomputes the HMAC with the shared secret and compares in constant time. Stripe sends it in Stripe-Signature, Shopify in X-Shopify-Hmac-SHA256.
SSO
Single sign-on: OpenID Connect and SAML
In plain words
Sign in once with your work account (Microsoft, Google…) and you’re in everywhere. No separate password per program.
For you: When someone leaves, you disable one account and all their access is gone.
Technical
OpenID Connect (OIDC) is an identity layer on OAuth 2.0: the identity provider issues a signed ID token (a JWT) with claims such as iss, sub, aud, exp and iat. SAML 2.0 is the older XML variant: a signed Assertion with Issuer, Subject, Conditions and attributes. We build both.
Rate limit
In plain words
A maximum number of requests per unit of time. Like a counter that only serves so many customers a minute: if you’re too fast, you wait a moment.
For you: An integration that ignores the limit gets refused. Ours waits politely and bundles requests.
Technical
An API limits the number of requests (often a token bucket or a window per second or minute). Go over it and you get HTTP 429 Too Many Requests, often with a Retry-After header. Good clients track the remaining room, spread their requests and wait out the Retry-After.
Idempotency
In plain words
Asking the same thing twice gives the result only once. Like an elevator button: pressing it ten times still brings one elevator.
For you: A double click or a flaky connection never results in a double payment or a double invoice.
Technical
An operation is idempotent if repeating it has the same effect as running it once. For POST, you send a unique Idempotency-Key header; the server stores the response per key and returns the same response on a repeat instead of booking again. Stripe and Mollie support this.
Queue
In plain words
A line in which tasks wait their turn. If the accounting software is unreachable for a bit, the invoices simply stay in line.
For you: Nothing gets lost, not even when one of your systems is down for a while.
Technical
A message queue (e.g. RabbitMQ, Amazon SQS, or a table in PostgreSQL) decouples receiving from processing. A worker picks up messages, acknowledges (ack) only after success, and moves messages that keep failing to a dead-letter queue for review.
Retry with exponential backoff
In plain words
Try again, but wait a little longer each time: 1 second, then 2, then 4. That gives a struggling system room to breathe.
For you: A brief outage at your accounting software resolves itself, without anyone having to do anything.
Technical
On temporary errors (timeouts, 429, 503), the client repeats the request with a wait time that grows exponentially: min(cap, base × 2^attempt). Jitter (random spread) keeps all clients from coming back at once. After a maximum number of attempts, the message goes to the dead-letter queue.
OpenAPI (Swagger)
In plain words
An API’s manual, in a fixed form that computers can read too. It says which questions you can ask and what the answer looks like.
For you: We integrate an API with a good OpenAPI description faster, and the API we build for you gets one too.
Technical
The OpenAPI Specification (formerly Swagger) describes an HTTP API in YAML or JSON: paths, methods, parameters, schemas, security. From it you generate documentation, test calls, validation and typed clients. Current versions: 3.1 and 3.2.
EDI (EDIFACT)
Electronic Data Interchange
In plain words
The oldest form of integration, still the standard at supermarkets, wholesalers and carriers. Orders, delivery notes and invoices travel from system to system as short coded lines.
For you: If you want to supply a large retail chain, it will often ask for EDI. We translate it to and from your own software.
Technical
UN/EDIFACT is the UN standard for structured trade messages, such as ORDERS (order), DESADV (despatch advice) and INVOIC (invoice). A message consists of segments (UNH, BGM, DTM, NAD, LIN, QTY… UNT), separated by an apostrophe; + separates data elements, : the components. Transport is often via AS2 or SFTP; GS1 EANCOM is the common subset in retail.
UBL and Peppol BIS
Universal Business Language
In plain words
The fixed format of an e-invoice. Since 2026, Belgian businesses no longer send each other PDFs but a UBL file over the Peppol network, which any accounting software reads in without retyping.
For you: Your invoices land in your customer’s accounting automatically and error-free, and your suppliers’ invoices land in yours.
Technical
UBL 2.1 is an OASIS standard in XML. Peppol BIS Billing 3.0 defines which UBL fields are required, in line with the European standard EN 16931; the CustomizationID and ProfileID say which rules apply. Validation uses XSD and Schematron rules (BR-…, PEPPOL-…).
Middleware and iPaaS
Integration Platform as a Service
In plain words
A central switchboard between all your programs. Instead of connecting every program to every other one, they all talk to one hub.
For you: Adding or replacing a system affects only one connection, not all the others.
Technical
Software that sits between systems and receives, transforms, routes and retries messages. An iPaaS is that layer as a cloud service (e.g. Make, Zapier, Power Automate); custom middleware runs on your own server. Point-to-point with n systems takes up to n(n−1)/2 connections; via a hub, n.
ETL
Extract, Transform, Load
In plain words
Fetching data from different sources, cleaning it up and combining it, then putting it in one place for reports. Usually at night.
For you: That’s how you see your revenue per channel (store, webshop, cafés) in one overview every morning, without copying and pasting in Excel.
Technical
A batch process: extract from sources (APIs, databases, files), transform (types, currencies, VAT, duplicates, keys) and load into a target system such as a data warehouse or BI tool. With ELT, you load raw data first and transform it in the warehouse.
Sandbox (test environment)
In plain words
A practice version of a piece of software, with fake customers and fake money. We test everything there, so nothing goes wrong in your real accounting.
For you: No test invoices to your real customers, no trial payments from your account.
Technical
A separate vendor environment with its own URLs, keys (e.g. test_… versus live_…) and data. We build and test there with your real scenarios, and at go-live we only switch the configuration; never test data in production.
Mapping
In plain words
The translation table between two programs: which field here goes with which field there, and how to convert it. ‘Price incl. VAT’ in the webshop becomes ‘amount excl. VAT’ in the accounting software.
For you: This is where the real work is. A good mapping is why your accountant no longer has to correct anything.
Technical
A field-by-field specification from source to target, with transformations (VAT codes, units, rounding per line or per total, date formats), lookups (customer by VAT number or email) and default values. We record them in a mapping document that you approve and that belongs to you.
Source of truth
In plain words
For each piece of data, one system is the boss. You set the price in your accounting software and the stock in your POS; the other systems follow.
For you: No more arguing over which price or which stock level is right.
Technical
In a two-way integration, one system is the master (system of record) for each field. Changes there are passed on; changes elsewhere are overwritten at the next sync or reported as a conflict. Without that agreement, you get sync loops and ‘last write wins’ surprises.
Brand names and logos belong to their owners. Missing a word? Just ask us, even if you’re not a customer (yet).
·E-invoicing
Peppol: e-invoices, mandatory since January 1, 2026.
Between Belgian businesses, a PDF sent by email is no longer a valid invoice. An invoice now travels as structured data over the Peppol network, straight from your software to your customer’s. We connect your webshop, software or invoicing to Peppol, so it all happens on its own.
Between VAT-registered Belgian businesses, only an e-invoice counts now: data that software can read, not a document to look at.
2Sending and receiving
You have to be able to send e-invoices, but also to receive them. So your purchase invoices come in via Peppol too.
3One network, like email
Peppol is a European network of certified access points. You pick one (it’s often built into your accounting software) and can then reach every business on Peppol.
Demo · Koffiebranderij Vennegem
Example: invoice VF-2026-0319 from Koffiebranderij Vennegem to Brasserie Vennegem travels in seven steps across the four corners of Peppol.
SML + SMPPeppol’s address book
Peppol network· AS4
C1
Sender
Sender
Koffiebranderij Vennegem
0208:0712345631
C2
Access point
Access point
of the sender
Peppol certificate
C3
Access point
Access point
of the recipient
Peppol certificate
C4
Recipient
Recipient
Brasserie Vennegem
0208:0798765406
VF-2026-0319VF
C1Step 1 of 7
Lotte creates the invoice, as always
In the accounting software or in your own software. Nothing new to learn: one click on send.
Why it matters
You work the way you’re used to. The integration does the rest.
Sales invoices10/06/2026
VF-2026-0319
Customer: Brasserie Vennegem · BE0798765406
Ready to sendSent via Peppol
DescriptionQtyAmount
Espresso Donker 1 kg6 × €26.89€161.34
Huismelange 1 kg4 × €25.38€101.52
Decafé Zacht 500 g2 × €14.62€29.24
Total excl. VAT€292.10VAT 6%€17.53Total€309.63
Send via Peppol
Click a step, or browse with Previous and Next.
What you need to do
Make sure you’re on Peppol with your company number (Peppol ID 0208:…), through your accounting software or an access point.
Send invoices and credit notes to Belgian businesses as e-invoices, not as PDFs anymore.
Check whether your suppliers can send you their invoices via Peppol, and whether you process them automatically.
Ask your business customers for their VAT number and Peppol ID, so every invoice finds its way.
What we do
We connect your webshop, POS or software to Peppol: through your accounting software, or directly through an access point.
We convert your invoice data to Peppol BIS Billing 3.0 and check it before it goes out.
Incoming e-invoices land automatically in your accounting or software, with an alert if something doesn’t add up.
We keep the integration up to date when the rules or your software change.
The timeline
January 1, 2026
E-invoices via Peppol mandatory between VAT-registered Belgian businesses, credit notes included.
January to March 2026
Grace period without fines for anyone who could show they had started on time. That period is over.
2028, planned
E-reporting: your invoice data will then also go to the FPS Finance almost immediately. The law is still being drafted.
Good to know
Fines
If you can’t send and receive e-invoices, you risk €1,500, €3,000 for a second offense and €5,000 after that.
Hermes no longer exists
The government’s free Peppol platform shut down at the end of 2025. You now need your own access to Peppol: through your accounting software or a service provider.
Tax benefit
From 2024 through 2027, small businesses and self-employed people can deduct 120% of their invoicing software subscription and advisory costs, under certain conditions.
Exceptions
Among others, for businesses that only carry out exempt transactions (Article 44). If you only sell to consumers, you still have to be able to receive e-invoices from your suppliers.
For your IT team
Peppol BIS Billing 3.0 (UBL 2.1, compliant with EN 16931; no national CIUS in Belgium). Four-corner model: C2 looks up the recipient’s SMP via the SML and sends over AS4 (peppol-transport-as4-v2_0, SBDH required) to C3. Peppol ID in Belgium: at least scheme 0208 with the company number. Before sending, we validate against the UBL schema and the EN 16931 and Peppol schematron rules.
Connecting two systems is the easy part. The work is in the details: which VAT code goes with 6%, is this an existing customer or a new one, where do you post the shipping costs? That’s called mapping. We define every field, test with your real cases and stop anything that doesn’t add up.
Demo · Koffiebranderij Vennegem
On the left, the fields of a webshop order; on the right, the fields of a sales invoice in Exact Online; in between, the rules that convert each field. Pick a test case and test the mapping: the result appears field by field, and anything that doesn’t add up is stopped with a clear message.
Mapping studio — Webshop → Exact Online
Webshopkoffievennegem.beExact OnlineSales invoicesMapping v7Approved by Lotte on Oct 2Test environment
Base VK06 (6%)66.65 · VAT 4.00Total€70.65Matches payment tr_7UhSN1zuXS of €70.65VAT return: box 01
Pick a test case yourself and click a rule in the middle: you’ll get it explained, in plain words and technically.
WebshopPOS
KV-HUIS-1000matchKV-HUIS-1000
KV-ESP-1000matchKV-ESP-1000
KV-ETH-0250no matchKV-ETH-250
KV-DEC-0500matchKV-DEC-0500
Suggestion: KV-ETH-0250
Discipline in item numbers
One item number (SKU) per product, the same everywhere. Before we build, we put your lists side by side and show you what doesn’t match.
Example
Trial import · invoices 2024–2026--dry-run
Read2,418
Duplicate3
No VAT code12
Ready to import2,403
Bring your history along
We bring over old customers, items and invoices if you want. First a trial import that shows what’s duplicated or incomplete, and only then the real thing.
TestLiveTest order #T-0007
Mollietest_•••••••••
Exact OnlineTest company
Live stays off until you approve
First in a test environment
We build and test with test keys and a test company, using your real cases. Nobody touches your live accounting until you say: go.
One source of truth per piece of data
Demo · Koffiebranderij Vennegem
With a two-way integration, we agree for each piece of data which system is the boss. That’s where you change it; the other systems follow. That way they never overwrite each other.
Source of truth per piece of data, and a stock conflict
Data
Source
Follows
Prices and items
Accounting · ExactWebshop, POS
WebshopPOS
Stock
POSWebshop
Webshop
Address of web customers
WebshopAccounting
Accounting
VAT number and payment terms (B2B)
Accounting · ExactWebshop
Webshop
Payment status
Payments · MollieWebshop, Accounting
WebshopAccounting
Conflict: two sales in the same second
Ethiopië Guji 250 g: 7 left in stock
POS7Source
Webshop7Follows
09:42:07.000POS · Webshop= 7
How to sync?
Mapping documentv7
FieldRule
customer.vat_number→ OrderedBy
line_items[].tax_rate→ VATCode
shipping.price→ GLAccount 700100
LotteApproved · Oct 2
The mapping document is yours
Every field, every rule and every exception on paper. You approve it before we build, and you keep it. Even if you later move on with someone else.
For your IT team
Schema validation on every message before it moves on
Idempotent upserts on an external id: never duplicated
Amounts as decimals, never as floats
Times stored in UTC, converted per country
Mapping as version-controlled configuration, with tests
This is how an integration talks to Exact, Mollie, Shopify and the rest: real requests, real responses. Pick one and press Send. Each request comes with one sentence on what it does for you.
Sample console of an integration for Koffiebranderij Vennegem (a demo business): real API requests to Exact Online, Mollie, Shopify, Odoo, SAP Business One, bol, Teamleader and Sendcloud with their responses, a webhook being checked, the OAuth 2.0 sign-in and files via SFTP and EDI.
connectedTLS 1.3hosted in the EUTue, Oct 6, 09:42 AM
An API is a program’s service entrance.
Through that entrance, our integration requests data or passes something on: an invoice, a payment, a shipment. Every system has its own rules. We know them and follow them, down to the field.
For your IT team
REST · GraphQL · OData · RPC
OAuth 2.0, API keys, sessions
Pinned API version per request
Only the fields we need
How we work with APIs
Documentation first
Every vendor has its own rules and limits. We read them before we write a line of code.
OpenAPI · changelogs · limits
First in a test environment
We build and test with test keys and in a sandbox, not in your real accounting.
test_ keys · demo environments
We respect the limits
A system only accepts so many requests per minute. We bundle them and politely wait our turn.
429 · Retry-After · backoff
Pinned versions
We pick a fixed version of every API. So an update at the vendor doesn’t quietly break your integration; we schedule the switch ourselves.
Shopify 2026-07 · bol v10 · Mollie v2
Large volumes in chunks
We fetch a thousand invoices in pages, and only what changed since last time.
$top · __next · cursors · updated_since
No API? Then we build one.
If your own system doesn’t have an API, we build one, with documentation your IT team can read right away.
REST · OpenAPI 3.1 · webhooks
The requests in the console are shortened but follow each vendor’s documentation (September 2026); the link is next to every request. Keys and tokens are truncated. Brand names and logos belong to their owners; they show which systems we integrate with.
// 02 · RELIABILITY
An integration that doesn’t stall. And if something goes wrong, we’re the first to know.
Every system goes down now and then, hits its limit or gets a new version. A good integration absorbs that: it waits, tries again, remembers everything and alerts us. You barely notice, and no order gets lost.
Demo · Koffiebranderij Vennegem
Monitor of the Koffiebranderij Vennegem integrations, with five integrations, a log and the selected failure.
Simulate a failure
Integrations · Koffiebranderij VennegemproductionAll systems go09:42:50
shop→exactPOST /api/v1/{division}/salesinvoice/SalesInvoices → 201 · 202 ms
In plain words
An ordinary Tuesday morning
Orders, payments, labels, stock and e-invoices flow between the systems on their own. Every step goes into the log, with time and result. Pick a failure above to see what happens when things go wrong.
For your IT team
Webhooks and polling per integration
Durable queue per target system
Structured logs with time and result
Pick a failure and watch what the integration does. The demo plays once; after that, everything works by hand.
How we keep your integrations running
We monitor your integrations
Every integration has a monitor with status, queue and error rate. If something gets stuck, we get an alert, not your customer.
Health checks · metrics per flow · alerts
Nothing gets lost
Every message is stored safely first and only then processed. If a system is down, it simply waits its turn.
Durable queue · retries · dead-letter queue
Logs you can read
For each order, you see what happened and when, in plain words. Without personal data in the logs.
Structured logging · correlation id
Again, with one click
Was a piece of data wrong, like a missing item? Fix it and send the message through again. Nobody has to retype anything.
Replay · processed idempotently
Maintenance: APIs change, we keep up
Vendors change their APIs, switch off old versions and let keys expire. With a maintenance plan, we keep your integrations up to date and roll out those updates for you.
Basic€25/month
Hosting on European servers, SSL, daily backups and updates.
Growth€69/month
Basic + uptime monitoring, 2 hours of changes per month and a monthly report.
Partner€179/month
Growth + 6 hours of development per month and priority support.
That someone else’s system will never go down. Nobody can promise that. What we do: build every integration so that a failure doesn’t cost you an order, a payment or an invoice.
// 03 · SECURITY
Securely connected. And everything stays yours.
An integration touches your invoices, your customers and your payments. That’s why it only gets the permissions it needs, its keys sit in a vault and there’s no personal data in the logs. That’s how we build every integration.
Example of how an integration is secured for Koffiebranderij Vennegem (a demo business): the permissions of the Exact Online integration per area, a vault with encrypted keys and an audit log, a log in which the customer’s email address, name and account number are masked, and the roles with two-factor authentication.
Try it yourself: raise or lower a permission, or revoke access.
Demo · Koffiebranderij Vennegem
Only the permissions it needs
The integration with your accounting can create invoices, but can’t look at your bank details. Here you see live what it can and can’t do. Revoke access and it stops cleanly, with nothing lost.
Keys and tokens are never in the code or in an email. They’re stored encrypted in a vault, replaced on time, and every use goes into an audit log.
Encrypted at rest · rotation · audit log
Vaultencrypted
Access token · Exact Online
••••••••••••••••
refreshes in 0:04
Valid for 10 minutes
Refresh token · Exact Online
••••••••••••••••
active
Single use
API key · Mollie
live_•••••••••••
active
Only for the integration
Webhook secret · Webshop
••••••••••••••••
new in 12 days
Verifies every ping
Audit log09:42:08
09:42:07integrationExact token used
POST /api/v1/{division}/salesinvoice/SalesInvoices
09:41:58integrationMollie key used
GET /v2/payments/tr_7UhSN1zuXS
09:32:21integrationExact token refreshed
POST /api/oauth2/token
08:12:44LotteSigned in with two-factor authentication
European, GDPR compliant
Your integrations run on European servers. If we process personal data for you, we put that in a data processing agreement. The monitor is protected with two-factor authentication, roles and permissions.
EU hosting · GDPR Art. 28 · 2FA · roles
European serversEU
Data processing agreementGDPR
Only the fields that are neededmin.
Who can do what in the monitor
LLotte · OwnerEverything, except showing keys2FA
EEls · AccountantRead only2FA
YYusuf · WarehouseShipments only2FA
BBrisk · MaintenanceMonitor and logs2FA
19Sign in to the monitorCode from your authenticator app482913
Logs without personal data
The logs show what happened, not who your customer is. We mask email addresses, names and account numbers before they’re written. What we don’t need, we don’t keep.
Masked before writing. The real data stays only in Exact and Mollie.
Code, mapping and documentation are yours.
No lock-in. You get the integration’s source code, the mapping document and the technical documentation. Want to take it further yourself later, or with someone else? No problem.
Plugin, Zapier or custom? Choose what fits, not what we sell.
Not every integration needs to be custom. Sometimes a plugin or a no-code tool like Zapier or Make does the job just fine, and then we’ll tell you so. Here you can see where each approach is strong and where it gets stuck.
Explained in
Strong
Possible, with limits
Weak spot
Show
Getting started and costs
Quick start
How fast the first piece of data comes across on its own.
What happens when a system briefly doesn’t respond.
Ownership and maintenance
Owner of code and data
What’s yours, and what you take with you if you leave.
When a vendor changes its API
It happens regularly. Who keeps track?
When should you choose this?
The best choice if…
Our honest advice, per approach.
Off-the-shelf plugin or app
A connector you install from the app store or marketplace of your webshop or software.
Getting started and costs
Quick start
Strong: Install, log in, done. Often the same day.Install and grant access (usually via OAuth). The mapping is fixed in the plugin.
Costs
Strong: A small monthly subscription, sometimes depending on your number of orders.License per shop or per volume. No development costs.
What it can handle
Complex rules
Weak spot: Does what its maker planned for. If you work differently, you get stuck.Fixed field mapping and a few settings. Adding your own logic usually isn’t possible.
Volume and speed
Possible, with limits: Usually fine for normal volumes.Depends on the plugin. Often syncs at fixed times.
Error handling and follow-up
Weak spot: Varies per plugin. An error often sits in a log nobody reads.Error handling is a black box, with few logs or alerts.
Ownership and maintenance
Owner of code and data
Weak spot: The code belongs to the maker. If they stop, your integration stops.Closed code under license. Your data passes through the maker’s servers.
When a vendor changes its API
Possible, with limits: The maker updates the plugin, as long as they keep maintaining it.You depend on the maker’s updates and schedule.
When should you choose this?
The best choice if…
…you use standard software and there’s a well-maintained plugin that does what you need.
You click flows together yourself: when this happens, do that.
Getting started and costs
Quick start
Strong: A simple flow is up in an afternoon.Trigger and actions in a visual editor, with ready-made connectors for many apps.
Costs
Possible, with limits: A monthly subscription. The more happens, the pricier the plan you need.You pay per executed step: tasks at Zapier, credits at Make, executions at n8n Cloud. Premium connectors in Power Automate need a separate license.
What it can handle
Complex rules
Possible, with limits: Possible with filters and branches, but a big flow quickly gets hard to follow.Filters, routers and code steps are possible. Version control and automated testing remain limited.
Volume and speed
Possible, with limits: Many apps are checked every few minutes. High volume gets expensive fast.Polling triggers with an interval that depends on your plan. Every step counts toward your usage.
Error handling and follow-up
Possible, with limits: You get an email on an error and can run it again. Figuring out why is up to you.Run history and error notifications. Automatic retries depend on the tool and your plan.
Ownership and maintenance
Owner of code and data
Possible, with limits: Your flows live in the tool’s account. Moving means rebuilding.Flows are tied to the platform. n8n, though, can run on your own server.
When a vendor changes its API
Possible, with limits: The tool keeps its connectors up to date. You adjust your own flows yourself.The platform maintains the connectors. Whatever breaks in your flows as a result, you fix yourself.
When should you choose this?
The best choice if…
…you have two systems, a simple flow and low volume. Then Zapier or Make is often enough.
We build and monitor the integration, for your systems and your rules.
Getting started and costs
Quick start
Possible, with limits: First a call, analysis and testing. That takes longer, but it’s right from day one.API check, mapping document and tests in a test environment (sandbox) before go-live.
Costs
Possible, with limits: A fixed, one-time price. Then a monthly maintenance plan, if you want one.No costs per task or per message: more volume doesn’t change the price. Hosting and maintenance through a fixed monthly plan.
What it can handle
Complex rules
Strong: Exactly your rules: 6% and 21% VAT, B2B customers, exceptions. Tested with your real cases.Mapping and validation in code, with a test per rule and a separate test environment.
Volume and speed
Strong: Instantly, even on busy days. Peaks are neatly processed one after the other.Webhooks where the system offers them, a queue for peaks, batching and respect for rate limits.
Error handling and follow-up
Strong: The integration retries on its own. If that fails, we get an alert, not you.Retries with exponential backoff, a dead-letter queue, alerts and logs you can read.
Ownership and maintenance
Owner of code and data
Strong: Code, mapping and documentation are yours. No lock-in.Source code and documentation are handed over. Hosting on European servers.
When a vendor changes its API
Strong: With a maintenance plan, we keep track and update the integration in time.API versions pinned, deprecations tracked, updates in a maintenance window.
When should you choose this?
The best choice if…
…you have several systems, your own rules, lots of orders, or you want it to keep running without you keeping an eye on it.
Leave them where they work well. In a free 30-minute call, we look together at which flows get stuck on rules, volume or errors nobody sees, and we only rebuild those as custom integrations.
Brand names and logos belong to their owners; they show which tools we compare with. How the no-code tools work is based on their own documentation, September 2026.
How it works
From first call to an integration that keeps running. In six steps, with no surprises.
You don’t need to know what an API is. You tell us how you work, we figure out what your systems can do, and you approve everything before we build.
Demo · Koffiebranderij Vennegem
The examples follow one integration: webshop, POS, Mollie, Sendcloud, Teamleader and Exact Online.
Inventory
Koffiebranderij Vennegem
6 systems
Webshopordersaddresses
POSsalesstock
Exact Onlineinvoices, VATprices
Molliepayments
Sendcloudlabels
Teamleadercontactscustomers
source of truth
01 / 06
Free call and inventory.
In 30 minutes, we map out your systems: which programs you use, which data needs to flow and which system is the boss of each piece of data. We call that the source of truth.
For your IT team · Systems, versions and licenses · volumes per day · source of truth per field
API check
0 of 5 checked
Exact Online
OAuth 2.0 · test company
Mollie
API key · test mode
Sendcloud
API keys · test labels
Teamleader
OAuth 2.0 · sandbox
POS
No open API
POS: a CSV via SFTP every nightExact: 60/min · 5,000/day
02 / 06
We check every API.
We read the documentation, request access and test in a test environment. If a system has no API, we tell you honestly and suggest another route, such as an export that’s ready every night.
For your IT team · Authentication (OAuth 2.0 or API key) · rate limits · webhooks or polling · API version
Mapping document v1.3
Webshop → Exact Online
7/14 fields
line.skuItem code
line.vat_rate: 6VAT code 6%
shipping_lines[0]Separate line
customer.vat_numberAccount by VAT no.
LShipping separate? Yes, please.
Approved
Lotte · Oct 2
03 / 06
You approve the mapping document.
Field by field, we record what goes where: item numbers, VAT codes, customers, shipping costs. You sign off before we build, and the document stays yours.
For your IT team · Field mapping, transformations and validation rules · per direction · with examples
Test run
test environment
0/4 passed
Online order
T-10482
B2B · Brasserie
T-B2B-0319
Return → credit note
T-RET-0007
VAT number missing
T-ERR-VAT
0.00 s
04 / 06
Building and testing with your cases.
We build in a test environment and test with your real situations: a regular order, a B2B invoice, a return. We also test what’s supposed to go wrong: then the integration stops cleanly and you get an alert.
For your IT team · Test keys and test company · automated tests per mapping · error scenarios
Go-live
Tue, Oct 6
TestLive
07:02History imported
07:05Webhooks turned on
09:42First real order#10482
First week: extra oversight
TuWeThFrSaSuMo
05 / 06
Live, at a quiet moment.
We take the integration live when it suits you, bring over your history if you want, and keep an extra close eye on it the first week.
For your IT team · Import in batches within the limits · webhooks only after the import · extra alerts the first week
Integrations
Koffiebranderij Vennegem
All good
Webshop → Exact09:41
Mollie → Exact09:42
Webshop → Sendcloud09:43
POS ↔ Webshop09:44
New API version
Sendcloud · API v2 → v3
Update scheduled
Your dedicated contact at Brisk
06 / 06
We keep it running.
Vendors change their APIs. With a maintenance plan, we monitor your integrations, roll out updates on time and you have one dedicated contact person.
For your IT team · Monitoring and alerts · deprecations and version updates · logs and replay
How long does it take? That depends on your systems. After the API check, you get a schedule and a fixed price.
What does an integration cost? A fixed price, up front.
You add an integration to your webshop, software or app, at the prices below. Want to connect systems you already have? Then you get a fixed quote after a free call.
Data from your ERP, CRM or POS system directly in the app.
Via your system’s API, or an API we build for it
Code and documentation are yours
Between your existing systems
Custom quote
Already have a webshop, POS, accounting software or CRM and want them to talk to each other? We first look at your systems and their APIs. Then you get a fixed price in writing.
Fixed price · 40% deposit at the start · Code and data are yours5.0 on Google, from 49 reviews
Questions about integrations
What it costs, how long it takes, what happens if something goes wrong and who owns what. Answered honestly, in plain words. With a line for your IT team underneath.
Don’t see your question?
Email your question, or your list of systems. You’ll get an answer within 24 hours on business days.
Usually, an integration is part of your webshop, software or app, with a fixed price you see right away in the configurator. An integration between systems you already have, like Teamleader with Exact, is priced by quote, after a free 30-minute call. All prices are excl. VAT.
Integration prices, excl. VAT
In your webshopAccounting integration
€420
In your webshopInventory or ERP integration
€860
In your webshopSell on bol.com
€500
In your softwareIntegrations with existing software
€1,050per integration
In your appIntegration with your systems
€1,895
Between your existing systemsFor example, Teamleader with Exact
// For your IT teamPrices excl. VAT40% deposit at the startmonthly maintenance
That depends on the number of systems, on how good their APIs are and on the rules in your data, like VAT, B2B customers or returns. That’s why we check the APIs first and then set a schedule, with a date for each step: mapping document, testing and go-live. If the integration is part of a new webshop or software, it’s simply included in that schedule.
// For your IT teamAPI checksandboxtesting with your real casesgo-live with historical data
You do: the code, the mapping document and the documentation, with no license per integration or per task. The accounts with your vendors stay in your name; the integration only gets the access it needs, and you can revoke it whenever you want. If you later want to continue with your own IT team or another provider, you take everything with you.
// For your IT teamGit repositorymapping documenttechnical documentationno lock-in
02Your systems
Often, yes. Many packages can export a file, like CSV, Excel or XML: we pick it up at a set time, for example every night. If your software runs on your own server, we can sometimes read straight from the database, with the vendor’s permission. And if orders only come in by email, we read those emails automatically. To be honest: an integration like that is slower than an API and more sensitive to changes in the software. We tell you that up front, along with the alternative.
// For your IT teamCSV/XML over SFTPread-only database useremail parsing (IMAP)EDI
Yes. Your system then gets a secure entrance through which your webshop, your app or your customers and suppliers can fetch and send data. With documentation in the OpenAPI standard format, so any developer can get started with it, and a separate key per party that you can revoke yourself. We include a custom API in a quote.
// For your IT teamREST/JSONOpenAPI 3.1OAuth 2.0 or API keyswebhooksversioning (/v1)
Yes. First we list your flows: what triggers them, which steps they take and where they sometimes go wrong. Then we rebuild them as a custom integration, with error handling and monitoring, test with your real cases and switch over at an agreed moment, so nothing happens twice. To be honest: if a simple flow runs well and the volume stays low, we’ll just tell you to keep it. Plugin, Zapier or custom?
Zapier
Make
n8n
PAPower Automate
// For your IT teamTrigger and action inventoryidempotency during the switchover
Both are possible, and we often combine them. Instantly works with a webhook: one system reports on its own that something happened, like a payment, and the integration passes it on. For large volumes, or for systems that don’t report anything, we work on a fixed schedule, for example every five minutes or every night. We choose per type of data: stock and payments instantly, an overview for your accountant once a day.
// For your IT teamWebhooks (signed)polling on ‘modified since’scheduled batchrate limits
03Accounting and Peppol
Yes, if you invoice other Belgian VAT-registered businesses. Since January 1, 2026, you must be able to send and receive e-invoices via Peppol; a PDF by email is no longer enough. If you can’t, you risk a fine, starting at €1,500. The government’s free Hermes platform stopped at the end of 2025, so you need your own access to Peppol. It’s often already included in your accounting software: then we connect your webshop or software to it. If not, we go directly through a Peppol access point. How Peppol works
// For your IT teamPeppol BIS Billing 3.0UBL 2.1EN 16931Peppol ID 0208:enterprise number
Gladly. Your accountant knows best how invoices, VAT codes and accounts should be set up in your accounting software. Together we define the mapping, and your accountant sees the first postings before we go live. After that, everything comes in on its own, with no folders of invoices at the end of the quarter. We integrate with Exact Online, Yuki, Octopus, WinBooks and Billit, among others. See all systems
Exact
Yuki
Octopus
WWinBooks
Billit
// For your IT teamVAT codesgeneral ledger accountsjournalsaccounts matched on VAT number
04Security, and after go-live
Your integrations run on European servers, with encrypted connections. An integration only gets the permissions it needs: for example, writing invoices but not reading bank details. We store keys and tokens encrypted, never in the code or in an email. In the logs, we mask personal data such as email addresses, and we only process what’s necessary, as the GDPR requires. How we secure it
// For your IT teamTLSOAuth 2.0 scopes (least privilege)secrets encrypted at restmasked logs
It happens, and it’s usually announced well in advance. With a maintenance plan, from €25 per month, we keep track of it: we read what’s changing, update the integration in a test environment and put it live before the old version disappears. From the Growth plan (€69 per month) up, we also monitor your integrations and you get hours for changes every month. If a change is big, like a completely new API, you get a price first and you decide.
// For your IT teamPinned API version per integrationDeprecation and Sunset headersupdate in the sandbox
Then nothing gets lost. Every message is stored safely first and only then processed. If a system is briefly down, the integration tries again later, with a bit more time in between each attempt. If it really doesn’t work, for example because of a wrong piece of data, you get an explanation in plain words. Once it’s fixed, we send the message through again, and nobody has to retype anything. With a Growth or Partner plan, we get that alert first. How it keeps running
// For your IT teamQueueretries with exponential backoffdead-letter queueidempotent reprocessing
Brand names and logos belong to their owners; they show which systems we integrate with.
Ready to connect?
Let your systems talk to each other.
Tell us which programs you use and what should happen on its own. We figure out what’s possible, tell you honestly what it costs and build an integration that keeps running.