API version number

The DACHSER API version number is composed of 3 parts: x.y.z

  • x: is the highest level. When we change it, there is a breaking change. It means that you will have to update your system and call the new API version. The previous one will remain available for a certain time only (see deprecation period below).
  • y: the middle level change, when there are new functionalities, but the previous version remains compatible. If you don’t need the new possibilities you don’t need to change anything
  • z: the lowest level is used when we have minor modifications, like documentation update for instance

Breaking change and deprecation period

Despite we are respecting Postel’s principle, it could happen that we have to change the API in a way that the old version has to be stopped.

In this case, you will of course be informed by e-mail (we will use the one you’ve entered when you have created your login, that’s why technical e-mail addresses are important).

The previous version will be available for a certain time, to give you the chance the plan the update/test and production.

The deprecation period will depend on the importance of the modification but will be at least of 1 month.

No PRODUCTION until confirmed by the DACHSER branch

You can create your account, application and subscribe to our API in the “Trial Environment” and do test as you want.

Your related DACHSER branch will always have to confirm that they agree that you are using the API in production.

Recommendation for creating “application”

You are a customer of DACHSER then we advise that you create

  • One “application for TEST” and subscribe to the “Trial Environment” of the API you’ve chosen.
  • One “application for PRODUCTION” and subscribe to the “Full environment” of the API you’ve chosen

You are a Software Editor then we advise that you create

  • One “application for TEST” and subscribe to the “Trial Environment” of the API you’ve chosen.
  • One “application for PRODUCTION” for each of the DACHSER customers and subscribe to the “Full environment” of the API you’ve chosen
    before going live, we will ask our customer to confirm that they accept we go in production with your system.