As part of continuous improvements to Zalando’s Fulfilment solution, a new API endpoint has been introduced for retrieving received items. This change will take effect from May 1st, 2025.
What is changingÂ
The current endpoint "GET /received-items/{merchant-id}" will be deprecated and replaced by "GET /reports/received-items/{merchant-id}"
Lengow integrates this new endpoint, and no action is required from you using the Lengow Zalando Fulfilment solution directly. Consult Lengow API documentation here.
However, if you are using the old endpoint in custom integrations, you must update your systems accordingly.
Improvements in the new endpoint
Zalando has introduced several enhancements:
- Extended time interval: Retrieve data for up to 1 year (previously limited to 100 days).
- Cursor-based pagination: Enables easier data retrieval using a next_page_token, without adjusting time intervals manually.
- Removal of unused or redundant fields: "site_id (duplicate of location_id)"; "parent"; "tour_number"; "consumed_timestamp".
- Retention of received_timestamp, indicating when items were physically received.
- Two new optional fields added: "merchant_item_id"; Â "merchant_article_id".
(These fields are included only if you provided them during inbound.)
Check Zalando API documentation here.
What you have to do
Action required by May 1st, 2025
If you’re using the deprecated endpoint "GET​/received-items​/{merchant-id}" in a custom setup, please make sure to:
- Switch to the new endpoint: "GET /reports/received-items/{merchant-id}"
- Adapt your data parsing to account for new fields and pagination
- Discontinue use of removed fields
The previous endpoint will be fully disabled on May 1st, 2025.
Original message
[...]
This new endpoint comes with some improvements:
We are extending the time interval limitation from 100 days to 1 year.
It supports cursor-based pagination, allowing you to seamlessly retrieve the next set of data by simply providing the next page token, without the need to adjust the time interval.
Irrelevant and duplicated properties have been eliminated:
site_id and location_id properties represented the same value, so we have removed site_id.
parent and tour_number have been removed, as these properties were unused.
consumed_timestamp property is removed as it represents data that is relevant for internal usage only. Note that the received_timestamp property remains as it represents the time when an item was physically inbounded.
We’ve also added two new properties:
merchant_item_id and merchant_article_id properties are introduced to provide merchant-specified data if it was supplied during the items’ inbound process.
[...]
Â