bol.com API: connect bol.com to your webshop, stock and accounting

What you can do with the bol.com API

• Fetch new orders and pass them on to your warehouse or webshop
• Report shipments with tracking
• Update stock and offers from your central stock
• Process returns in stock and accounts
• Orders and costs to your accounting

How the integration works

The Retailer API works with a client ID and secret per seller account. Some actions, such as reporting a shipment, bol processes asynchronously: the integration then requests the status and alerts you if something did not succeed. Everything runs in n8n on your own server, with logging and alerting.

Facts about the bol.com API

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

Fact	What the documentation says	Source
Authentication	OAuth 2 client credentials with a client ID and secret from the Seller Dashboard; a bol retailer account is required.	bol.com: Authentication
Token lifetime	299 seconds. No refresh token; you request a new token, but not per request, because the token endpoint has a lower limit.	bol.com: Authentication
Rate limits	Per endpoint, published by bol: for example 25 per minute for fetching the order list and 25 per second for shipment notifications. When exceeded, 429 with Retry-After.	bol.com: Rate limits
Asynchronous	Write actions such as a shipment notification return a process status; the integration polls that status until SUCCESS, FAILURE or TIMEOUT.	bol.com: Conventions
Push notifications	Through the Subscriptions API v11: ORDER, SHIPMENT and PROCESS_STATUS as a webhook (IDs only, RSA-SHA256 signature). Ten attempts; after that the subscription is disabled.	bol.com: Subscriptions API
Test environment	A demo environment with fixed example responses (paths /retailer-demo/), with real authentication.	bol.com: Demo
Version	Version per resource in the URL and the Accept header; Retailer API v10 is current, v8 and v9 have been switched off since 11 December 2024. Deprecated resources are removed after at least twelve months.	bol.com: Versioning
n8n	No built-in node; one community node on npm (June 2025). I connect through the Retailer API with an HTTP step.	n8n documentation

What you need on your side

• A bol retailer account and an administrator who can create API credentials in the Seller Dashboard
• One place that keeps stock leading: your webshop, your WMS or the accounts
• A list of your shipping methods and the carrier per country
• Agreements on who assesses returns before stock and accounts are updated

Where it often goes wrong, and how I prevent it

• Overselling: if stock is not updated in time, you sell what you do not have. That is why stock goes through straight after every sale elsewhere.
• Asynchronous processing: a report has only succeeded once bol confirms it. The integration checks that status.
• Delivery promises: late shipment reports count towards your performance at bol. An alert warns you about delays.
• Returns: a return must update both stock and accounts.

In practice

In my own e-commerce, bol.com pipelines for orders and stock run alongside the webshop, so both channels see the same stock.

What it costs

I build a bol.com integration as one scoped process for a fixed price, from €750. Maintenance and monitoring are a monthly fee: n8n management from €250 per month, server management €145 per server. In the free assessment we work out your process. All prices and what is included →

What I do not do

• I do not manage your bol account or your offers; the integration processes orders, shipments and stock according to your rules.
• I do not request a new token per call; that is against bol's rules and leads to blocks.
• I only consider a write action successful once bol confirms it through the process status.

Frequently asked questions about the bol.com API

Does n8n have a bol.com node?

No. I connect bol.com through the official Retailer API in n8n. That is custom work, but it runs on your own server and is monitored.

Does this also work if I sell via Channable?

Yes. Then we look at which side leads: Channable for feeds, or a direct integration for orders and stock. I avoid double routes.

What if bol changes the API?

bol announces new API versions in advance. With maintenance, I update the integration before an old version disappears.

Why is a shipment notification at bol not final straight away?

bol processes write actions asynchronously. You get a process status back that later becomes SUCCESS, FAILURE or TIMEOUT. The integration polls that status and reports when a shipment has not been processed, so an order is not wrongly counted as shipped.

How long is a bol token valid?

299 seconds. The integration reuses the token until just before it expires and only then requests a new one, because the token endpoint has a lower limit than the rest of the API.