08-01-2020 – 7 improvements in the new version of the Retailer API

Do you want to work more efficiently? Automation via the bol.com Retailer API will help you to manage your sales processes from a single API. From April 1 this will become even better with the release of V5 of the Retailer API. See below for more information about the release.

Version 5 of the Retailer API, which was announced here , will contain new functionality as well as several enhancements. Read below for a summary of all the planned changes. Be aware that if any of the changes do not prove successful in this phase of development, they can be delayed or removed from V5.

Migrate to v5

  • If you wish to upgrade to the new API, you can involve an integration partner in the process.
  • If you are new to the API, you can learn more about it at Automation via integration partner .

New functionality

Search terms

The new version of the API will provide insights into the search terms that customers use as bol.com. Additionally, you can retrieve data about terms that are related to specific search terms. These can be viewed over a defined period. Understanding search terms will help you to:

  • Improve product information and make articles easier to find.
  • Make trend analyzes of specific items, which can help you to make better estimates for your purchasing.
  • Discover which articles are in demand, to enable you to expand your range.


Deliveries for Logistics via bol.com (LVB)

Deliveries for LVB makes it easier to set up pre-notifications for LVB replenishment shipments. You can also get better insights into the status of your shipment, and easily view whether the articles have been received, processed, and placed in stock in the warehouse. V5 also allows you to use the PostNL delivery service via the API.

Orders for Logistics via bol.com (LVB)

As part of improving order management in the API, orders will now remain visible for 48 hours. This makes it much less likely that you will overlook LVB orders due to fast shipping.

Further orders improvements are expected in the API version following V5, which will be released in H2 of 2021.

Allowable retail price

This enhancement for v5 allows you to retrieve what the market would see as a good price for articles that are now offline due to a too-high price. You can also directly change the price.

The enhancement is currently under testing; if it does not produce a positive effect for partners and bol.com, it will be stopped.

For more information, see Allowable retail price .

Pickup points

Currently the API only allows you to send orders directly to the address of a customer. This feature will make it possible for you to ship an order to a pickup point where the customer can collect it at their convenience.

For more information, see Shipping items to pickup points .

Offline orders

Sometimes articles can have an offline status without you noticing. This functionality allows you to get an overview of which articles are offline and why.

For more information, see Unpublished offers report.


This functionality allows you to subscribe to events about the process-status of actions you did through the API – for example, newly created offers or order confirmations. You will receive these events via your own webhook. Other events will be added in H2 2021.

For more information, see Subscription API .

BETA Testing

In the meantime, we are working on more functionality in the API. We are planning to release the following components somewhere in H1 2021 as a BETA. If they are successful, they will be added in V6.


This feature will allow you to see which promotions will apply to your assortment. This allows you to determine more easily if you want to participate in a promotion.

Feedback on product information

In V4 of the API we already provided you with some feedback regarding new product information – namely, whether or not it is valid. We are now also providing you with feedback into whether the product information is online in the webshop.

Image labeling

Partners often indicate that product images are not shown in the requested order. The option to label images will solve this problem. If we can make this improvement backwards-compatible we will provide this functionality in both V4 and V5.

Important note about the Content API

The last-mentioned Image labeling improvement makes up part of the Content API. The predecessor of the Content API – the Content FTPS – will be turned off on January 1, 2022. If you want to keep using our Content functionality, make sure that you upgrade to the Content API in time.

Geplaatst in Content API, Retailer API