PostNL API
POST /parcels/v1/shipment/activatereturn endpoint removal
Stopped workingSubscribe to PostNL APIShare
On August 1, 2026, PostNL API removed POST /parcels/v1/shipment/activatereturn. Requests sent to this endpoint are no longer accepted and fail with an error response.
Calls it hits
POST /parcels/v1/shipment/activatereturn
What to use instead of these calls
Stop creating Shipment and Return labels using Characteristic 152 or Option 026 and remove the handover blockade. Because the service is withdrawn without a direct replacement, redesign returns to manifest each return as a new return shipment with a new barcode using Returns API v4 or a return label.
The Shipment and Return label service is withdrawn with no direct replacement; returns must be redesigned as separate return shipments.
In PostNL API's words
Effective 1 August 2026, calls to this endpoint will no longer be accepted. Requests will result in an error response.
Facts
- API
- PostNL API
api.postnl.nl - Kind
- Endpoint removal
- Announced
- April 3, 2026
- Takes effect
- August 1, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against PostNL API's own pages
Questions
When does this change take effect?
Calls to POST /parcels/v1/shipment/activatereturn on PostNL API stopped working on August 1, 2026.
What happens to calls after August 1, 2026?
They have failed since August 1, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.