Why are we updating our APIs and systems?
Smooth transition to new versions
Faster integration, improved security
The new APIs are easier to integrate and less prone to errors, making your processes more efficient and reliable. Advanced security features, such as Multi-Factor Authentication, will further protect your data.
More flexibility with REST
The new versions will be REST-only. This simplifies maintenance and reduces costs. REST is lighter, more modern, flexible, and easier to use than SOAP. It is also widely supported by developers and tools, making integration simpler.
Consistent APIs, easier maintenance
The new API versions are aligned in structure and terminology, ensuring uniform integration and easier maintenance, saving you significant time.
When will the updates be rolled out?
The new APIs will become available in phases throughout 2025. You will receive timely notifications about when you need to migrate. By mid-2026, the older API versions will be phased out.
Which APIs and developments are planned?
Shipment API v4 en Checkout API v4
A new standard for track & trace will be introduced, featuring clear and consistent status updates available in real time. All business customers and integration partners will migrate within the specified timeframe.
New track & trace information and integrations
The new versions simplify the technical connection and shipping process with clear product names and the option of a portrait or landscape shipping label. All business customers and integration partners will migrate in phases.
Discontinuation of sFTP
In 2026, we will stop using sFTP and switch to faster and more secure API integrations. All business customers and integration partners will adopt these new APIs for quicker data exchange.
New Mijn PostNL Zakelijk
The old platform no longer meets requirements. Therefore, all business customers will migrate to the updated MijnPostNL Zakelijk environment. This platform is faster, more user-friendly, and future-proof. Learn about all the changes.
Other questions
Updating within the current version is risky because changes to the existing API structure can cause disruptions in customer integrations. Based on customer feedback after previous adjustments (which had both expected and unexpected impacts), we have learned that breaking changes within the same version can disrupt customers' operations. To avoid this, we have chosen to release a new API version for significant changes, such as a new architecture, security standards, and improved performance.
This change management process is an industry standard: for breaking changes, a new version is introduced to ensure the stability of existing integrations, allowing you to transition in a controlled manner.