Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update on the ongoing modernisation of our Post & Parcel API infrastructure #38

Open
ixopo opened this issue Dec 6, 2023 · 0 comments

Comments

@ixopo
Copy link

ixopo commented Dec 6, 2023

Hi Christoph,

recently i got an Email from DHL (see below).

I just tested the Sandbox and didnt get any errors.
You think following gonna be a problem with you lib ?:

  • API communication must be in ISO code UTF-8.
  • Namespaces must be used correctly.
  • Metadata of the response headers can change (e.g. "Access-Control-Allow-Headers").

Also in my application i use the MultiClient. I red here that they also plan to turn off the Tracking API?
Does that affect the library/MultiClient? Will my application still work?

I appreciate the time you spent finding that information for me

####################################################

Dear customers and developers,

Today we would like to give you another update on the ongoing modernisation of our Post & Parcel API infrastructure.
As already announced on 23 October 2023, we have started the gradual conversion of the users of our business customer shipping API and the shipment tracking API.

WHERE ARE WE NOW?

All sandbox API requests are already processed via the new API gateway. With the exception of the Business Customer Shipping API and the Post Order Management API, all of your production API requests are already being processed via the new API gateway.

We will continue to finalise the conversion of these two remaining APIs in January, after the current peak saison.

WHAT CAN YOU DO?

To ensure that your connection to the DHL Business Customer Shipping API continues to work after the changeover, we recommend that you test your current connection against the DHL Business Customer Shipping API sandbox until the beginning 15th January 2024.

Please note that our new API gateway pays closer attention to the specifications we have set:

API communication must be in ISO code UTF-8.
Namespaces must be used correctly.
Metadata of the response headers can change (e.g. "Access-Control-Allow-Headers").

If you encounter errors or other anomalies, please provide us with a detailed error description via your technical contact person or create a support ticket in the Group API Developer Portal (https://developer.dhl.com/).
Tip: You can recognise whether you are already being redirected to the new API gateway if your response header "Access-Control-Allow-Origin" corresponds to the value "https://developer.dhl.com/".

You can find the latest information on the current changeover here: https://developer.dhl.com/post-dhl-entwicklerportal-sunset-information

WHAT HAPPENS TO THE SOAP VERSION OF THE DHL BUSINESS CUSTOMER SHIPPING API?

The DHL Business Customer Shipping API "SOAP" no longer corresponds to the current state of the art and will therefore be successively switched off. Users of the GKV API 1.0 have already been informed about the shutdown date on 31 May 2024.
Please actively plan the changeover to the new DHL Business Customer Shipping API "RESTful" (https://developer.dhl.com/api-reference/parcel-de-shipping-post-parcel-germany-v2?language_content_entity=en#get-started-section/).

You can find a list of all modernised APIs in our new Group API Developer Portal (GDP) at https://developer.dhl.com/post-and-dhl-germany

Sincerely,

Your team Post & DHL Developer Portal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant