Schenker is now part of DSV. If you use Schenker via Carrier Connect or are planning to integrate it, this will result in some changes to the procedure. You may have already been contacted by DSV and received, for example, information about a new interface (SOAP API).
This article summarizes all the important information for you.
- The following information applies to all Schenker services, regardless of the country of origin (DB SCHENKERair, DB SCHENKERland, DB SCHENKERocean, DB SCHENKERroad).
Your existing Schenker connection will continue to operate
If you are already using Schenker via Carrier Connect, you do not need to take any action at this time regarding the interface you are using. The standards agreed upon and approved by Schenker and AEB (e.g., IFTMIN/IFTSTA) remain in effect and continue to function as usual.
You don't need to change anything.
Why we are not implementing the new SOAP API
DSV is currently providing a new SOAP-based interface. From our perspective, this is an interim step toward a final solution.
We made a conscious decision not to implement this interim solution in Carrier Connect. A SOAP connection would require additional effort on your part, which would have to be repeated anyway when you later switch to the final interface.
To keep your migration effort as low as possible, we are instead waiting for the new, generic REST API from DSV.
Outlook: the new DSV REST API
DSV plans to release a new, global REST API with the first product capabilities toward the end of 2026. We base our planning on this interface. Based on current information, we expect to be able to offer an integrated connection via this REST API in Q1 2027.
Once the scope of functions and the timeline have been finalized, we will inform you about the next steps here.
Important: DSV will determine your classification
Whether and how a connection to Schenker or DSV is possible depends on your classification at DSV. DSV assigns customers to an appropriate connection type based on defined criteria. This procedure is already in place at DSV and will also apply to Schenker going forward.
For you, this means the following: Before we can set up or expand a connection in Carrier Connect, DSV will determine your classification and which standard applies to you.
Proceed as follows:
- Is there an existing connection? You do not have to do anything. Your Schenker connection will continue to operate as usual.
- New connection or expansion? First, contact DSV and clarify the intended standard for your project.
- Have you been contacted by DSV regarding the SOAP API? AEB does not plan to provide a connection via SOAP API in Carrier Connect. You can let DSV know that you use Carrier Connect from AEB. DSV is aware of this status quo.
Do you have any questions?
If you have any questions about your specific Schenk or DSV integration, our Support team will be happy to assist you. Simply submit a request.