ups-banner-bg
ph_img_faq_page_image

DHL API Details – Multi Carrier Shipping Label App for Shopify FAQs

    FAQs on DHL API credentials, authentication, requests, and integration with Shopify

Questions in this section:

With DHL discontinuing the SOAP API v2 by 31/05/2025, will it still be possible to send parcels via PH Multicarrier after that date?

Yes, it will still be possible to use PH Multicarrier with DHL after the SOAP API discontinuation. The platform will switch to the DHL REST API when it becomes mandatory. Carriers typically provide ample time for such transitions, and PH Multicarrier is committed to updating the integration accordingly. If users face any difficulties after the switch, they are encouraged to reach out for prompt assistance.

Where can I find the MyDHL API in the DHL Developer Portal when creating an app?

The MyDHL API option appears under the “MyDHL” section when creating an app on developer.dhl.com. If you do not see any API or the MyDHL API option is missing, it indicates you either don’t have the necessary access or it is not enabled for your developer account. In this case, contact DHL Support or your DHL Account Representative to request access to the MyDHL API and obtain the right credentials. PluginHive is unable to provide the API credentials or grant access; this must come from DHL.

What should I do while waiting for PluginHive to support the new DHL Express API?

For now, you should continue using your existing XML credentials to configure DHL Express shipping within PluginHive. If you do not have XML credentials or cannot obtain them, consider alternative shipping integrations supported by PluginHive. Additionally, stay in touch with PluginHive support for any interim solutions or updates on DHL API integration progress.

What is the proper handling of shipping addresses without a house number in the DHL Paket API?

DHL Paket API requires the house number to be a mandatory field in the request. If an address legitimately does not have a house number, the correct approach is: – Use “0” (zero) as a placeholder in the streetNumber field to satisfy the mandatory requirement. – Do not leave the streetNumber field blank or reuse the street name as the number, as this causes API validation failures. For example: “`xml <cis:streetName>Main Street</cis:streetName> <cis:streetNumber>0</cis:streetNumber> “` This ensures the address passes validation and the shipment is processed correctly.

What is the process for releasing DHL Express API support in PluginHive, and when can I expect it?

The release of DHL Express API support within PluginHive involves multiple stages including development, testing, and certification by DHL. Because these steps require coordination and external validation, PluginHive cannot provide an exact ETA. The development to support DHL Rest API is scheduled to begin early next year, and certification is pending. PluginHive will inform users as soon as there is a confirmed release timeframe.

What is the API secret for DHL, and how do I find it?

The API secret (also called the Site Password) is part of the DHL API credential set needed to connect your DHL account to the app. To obtain it, contact your DHL Account Representative or DHL support team directly. They will provide you with the full set of API credentials, including the API secret.

Since DHL mandates switching to the REST API by 31/05/2025, and the PH Multicarrier app has not yet switched, what will happen after 01/06/2025?

PH Multicarrier is aware of DHL’s requirement to stop using SOAP API v2 after 31/05/ 2025. The team is actively reviewing and working on this transition. Users should anticipate that the app will switch to the REST API as required to maintain functionality. While the integration is not yet complete, updates will be provided as soon as the migration is finalized, ensuring uninterrupted DHL shipping.

Is there an alternative DHL API version available in PluginHive after the XML integration is discontinued, and how can I switch to it?

Currently, PluginHive is actively working on integrating the DHL REST API as the successor to the older XML versions. Although the REST API integration is not fully live yet, you can already connect your valid DHL REST API credentials (Client Secret & Key) with the app to continue shipping without disruption. Once the REST API support is fully implemented, minimal changes will be required on your end to switch workflows. For guidance on setting up these REST API credentials within the app, you can schedule a call with PluginHive support who can walk you through the process step-by-step. Until then, continue monitoring your DHL account status and ensure your API credentials are compatible with the supported API version.

Is there a roadmap or timeline available for when DHL shipping via PH Multicarrier will be fully operational using the REST API?

The PH Multicarrier team is currently testing the DHL REST API integration but has not finalized a release date yet. Meanwhile, users can continue shipping with DHL using the SHL SOAP API V3, which remains functional. Once a release timeline is established and the REST API integration is ready, users will receive updates with detailed information.

How long does the DHL API certification process usually take for PluginHive’s integration?

The DHL API certification process timeline can vary and depends on coordination between PluginHive and DHL. There is no fixed duration, and currently, PluginHive does not have a specific estimate for when certification will be completed. PluginHive will notify users once the certification is finalized and the integration is ready for deployment.

How can I get help from PluginHive to set up or switch to the DHL REST API integration?

You can contact PluginHive support to schedule a dedicated assistance call for setting up your DHL REST API credentials or transitioning from XML. During the call, the support team will: – Guide you through entering your REST API credentials into the PluginHive app. – Help verify your account setup and connectivity. – Answer any technical questions related to the API changeover. To book a slot for this call, reach out to PluginHive support via their support channels or email. They aim to ensure minimal disruption in your shipping workflow during this transition.

Can PluginHive support troubleshoot DHL API authentication issues without sharing my API credentials?

PluginHive support typically requires your DHL API credentials (Account Number, Site ID, Site Password) to attempt adding your DHL account from their end. However, if you are uncomfortable sharing this sensitive information: 1. Contact your DHL Account Representative for assistance in authenticating and validating your API credentials. 2. Ensure you have the correct and active API credentials before attempting to connect through the PluginHive app. 3. Once you have confirmed credentials are valid, PluginHive can assist further through remote sessions such as Zoom calls without directly handling your credentials.

Are PluginHive Multi-Carrier shipments to DHL processed using the xml-pi API, and is there a region field set to “US” in the requests?

Yes, PluginHive Multi-Carrier communicates with DHL via the xml-pi API. However, there is no explicit region field included in the XML request. The shipment processing region is determined automatically based on the account’s country of origin rather than a region parameter in the request. To verify specifics or troubleshoot, you should share the request and response XML files with DHL support for their review and validation.

Looking for more details or ready to get started?
Visit the app page to explore features and pricing.

Shopify Multi Carrier Shipping Label App