DHL ECOMMERCE UK TECHNICAL SPECIFICATION UPDATE

As part of ongoing enhancements to the DHL eCommerce UK Cloud API, the service endpoints will be updated in the near future.

New API Endpoints (Coming Soon)

• Live / Production: https://api.evripremium.com
• Test / UAT: https://uat-api.evripremium.com

These new URLs are not yet active; please check this page regularly for updates.

The confirmed go live date will be published here in advance to allow enough time for customers and third party vendors to prepare for the transition.

Required Action

If you are using a legacy API integration, you are required to complete your migration to the Cloud API no later than 30/06/2026.

Failure to complete the migration by this date will result in the inability to generate shipment labels, request collections, or track parcels. If you anticipate any challenges meeting this deadline, it is important that you contact your Account Manager immediately to discuss available options.

How this affects you

Please review the section below that applies to your integration setup:

1. Clients using legacy API integrations

• Your existing legacy API integration must be fully replaced with the DHL eCommerce UK Cloud API.
• Development and testing must be completed by your technical team.
• DHL eCommerce UK will provide documentation, test environments, and technical support.

Next steps:

• Review the Cloud API documentation via our Developer Portal.
• Confirm your technical contact email address and DHL eCommerce UK account numbers, so that Cloud API credentials can be issued.
• As part of ongoing improvements to the DHL eCommerce UK Cloud API, the URL endpoint will be changing in the near future.
• The new endpoint will be:
• Live/Production: https://api.evripremium.com
• Test/UAT: https://uat-api.evripremium.com

Please note that this change is not yet active. Customers must refer to this page for the latest information and the confirmed go live date for this endpoint. Updates will be published ahead of the transition.

2. Clients using third-party vendors that use legacy integrations

• Your vendor must migrate their integration to the Cloud API to maintain service continuity.
• Please contact your vendor immediately to confirm their migration plans and timelines.

Next steps:

• Speak to your third-party vendor about this change.
• As part of ongoing improvements to the DHL eCommerce UK Cloud API, the URL endpoint used by your third-party vendor will be changing in the near future.
• Live/Production: https://api.evripremium.com
• Test/UAT: https://uat-api.evripremium.com

Please note that this change is not yet active. Your vendor must refer to this page for the latest information and the confirmed go live date for this endpoint. Updates will be published ahead of the transition.

3. Clients already using the Cloud API

• No migration is required; however, as part of ongoing improvements to the DHL eCommerce UK Cloud API, the URL endpoint will be changing in the near future. Please see section above.

For technical migration development related questions, clients or their developers may submit queries directly to itroadmapsupport@evri.com

All commercial, timeline, and migration ownership remains with your Account Manager, who will coordinate support and ensure appropriate follow-up. You’ll also find a list of FAQs at the foot of this page.

If you'd like to receive detailed tracking information about your shipments, we can provide this data in a designated secure area. Download the guide below for full details.

Please use the links below to download the following updates:

• Self-label technical specification v5.6
• Access to the DHL developers portal for the cloud API v1.3.0

These files include the data requirements detailed in the Windsor Framework for shipments moving from Great Britain to Northern Ireland.

Please use the links below to download example orders + clearance schemas for Ship and to view the user guide:

Please note that the data requirements are dependent on and will change based on the trade lane movement which you have selected.

The 4 trade lanes are C2C, C2B, B2C and B2B

If the recipient of a shipment is a consumer but the delivery address is a business address, such as their place of work, this will be a 2C movement.

For customers using our self-label or API solutions, you will be asked to provide the code for each shipment which is used to confirm the trade lane movement and is not used to categorise the delivery address. The data requirements will change dependent on the selected trade lane.

Codes to use: C2C, C2B, B2C or B2B

C2C - shipper and recipient are consumers
C2B – shipper is a consumer and recipient is a business
(If shipment is going to a consumer at a business address, for example their work address, this is still a C2C movement)
B2C – shipper is a business and recipient is a consumer
B2B – shipper and recipient are businesses
(If shipment is going to a consumer at a business address, for example their work address, this is still a B2C movement)

Not at risk ‘green lane’ and at risk ‘red lane’ B2B trade lanes

A B2B shipment will be classed as not at risk ‘green lane’ based on the provision of either your UKIMS number (as the shipper) or the UKIMS number for the receiving business. For green lane shipments the simplified H8 dataset will be required.

For at risk ‘red lane’ movements the full H1 international dataset will be required.

To move goods on the B2B trade lane that are considered ‘not at risk’ of entering the EU, either the sending or receiving business will need to be authorised under the UK Internal Market Scheme (UKIMS) and meet the criteria for moving goods under this scheme. You can now apply for authorisation under UKIMS.

Where business to business movements take place using UKIMS, we will act as the declarant submitting a simplified dataset referred to as the H8 dataset.

The holder of the UKIMS number will need to be declared as the importer on record.

Deferment account

If your B2B goods do not qualify under UKIMS and are therefore considered ‘at risk’ of leaving Northern Ireland, a full H1 international dataset will be required for the declaration. ‘At risk’ shipments will also be charged at the applicable European Union (EU) rate of duty.

If you will be shipping ‘red lane’ goods and will move to use a deferment account linked to your NI EORI number for Customs charges, please remember to authorise DHL to apply charges to this account. You'll need to subscribe to the CDS service via your HMRC Government Gateway account. Please check the gov.uk website for further guidance. You will need to state your deferment account number within the shipment data.

Alternatively, if you do not provide your deferment account number we will apply the DHL eCommerce UK deferment account.