Release Notes bol Offer API Version 11

Version 11.1 (BETA)

Version Release Date Release Type

11.1

24-11-2025

Minor

Summary of changes:

Missing product content attributes are added to the /not-for-sale-reasons endpoint in case an offer is offline due to missing product attributes.
In this way, a user can directly see which product attributes are missing that caused the offer to be offline.
This applies when the reason.code in the API response is equal to 4004-2.

With the implementation of this new feature, we also streamline the underlying unstructured data model over the rest of the Offer API. This shift is essential for consumer stability as it establishes a predictable, uniform convention for all attributes, significantly reducing integration risks and making the Offer API inherently less error-prone. This allows us to guarantee a foundation that can consistently and safely support future roadmap expansion.

This version includes breaking changes. It is marked as a minor version upgrade because it is still in the BETA phase, where communication was done upfront that breaking changes are expected if needed, within the same major version. See the table below for more details.
Change # Breaking change? Endpoint Change description

1

Yes

POST /retailer/offers
GET /retailer/offers
GET /retailer/offers/{offer-id}

Within the condition object, the field name will change from type to category. This field can be used as a discriminator to distinguish the different fields per type.
See condition object in use cases guide

2

Yes

POST /retailer/offers
GET /retailer/offers
GET /retailer/offers/{offer-id}

attributes will be removed. Each field within attributes is now defined in the condition object. The category field can be used as a discriminator to distinguish the different fields per type.
See condition object in use cases guide

3

No

GET /retailer/offers/{offer-id}/not-for-sale-reasons

Within the reasons array, a category field is introduced, which can be used as a discriminator to distinguish the different fields per type.
See reasons array in use cases guide

4

No

GET /retailer/offers/{offer-id}/not-for-sale-reasons

In case the category within the reasons array equals CONTENT, an additional array called missingAttributes is added where each element contains an object including a name of each product attribute that is missing.
See reasons array in use cases guide

Version 11.0 (BETA)

Version Release Date Release Type

11.0

21-10-2025

Major

New features and improvements