📦 Parcel carriers

This list is not complete as of today. For further carrier reach out to support@parcellab.com

DHL Germany

To unlock the private interface for DHL, you need the following two pieces of information:

  • ZT-ID: User ID for sender like ZT123456

  • Passwort: Associated password, usually not very creative

This access is also the login to the web portal for the business customers Track & Trace. Therefore, the activation of the interface at the DHL contact must be explicitly requested. This interface is called:

Business Customers Track & Trace (DASS)

Once the interface has been activated, parcelLab will increase the API limits for the interface on behalf of the sender. This is usually done in a few hours.

For large volumes it might be suitable to additionally activate Proactive Reports. For this we are using the EREIGNIS-REPORT (REPSRD). This can be set up by your account manager as well.

DHL Poland

DHL Poland currently still features a different setup than the other countries. Hence, we use the interface described as:

DHL Poland TntWebService (DHL Express Poland Webservice T&T)

DHL provides two credentials for this, all of which are needed to retrieve the interface through parcelLab:

  • clientId: unique ID of the DHL customer

  • password: a password connected with the clientId that allows to find shipments

Both can be requested at your contact at DHL Poland.

DHL Express

For DHL Express, parcelLab accesses the following interface:

DHL Express Global Web Services

The following two areas are needed:

  • Trackingrequest (Track & Trace)

  • Documentretrieve EPOD (proof of delivery)

For this interface, access data must be requested from the DHL Express contact person by indicating the customer number. These are usually provided at short notice and consist of:

  • Username

  • Password

DPD Germany

The activation for the private DPD interface takes place via the contact person in the depot. The activation for the following interface in live operation must be requested:

DPD Cloud Webservice for Tracking (provision of information / DPD Tracking Service), parcelLab partner interface

Please be sure to state that this is the parcelLab partner interface.

DPD provides two credentials for this, all of which are needed to retrieve the interface through parcelLab:

  • UserCredentials CloudUserID: six- to eight-digit number

  • UserCredentials Token: 15-digit alpha-numeric code

The live URLs (endpoints) to the DPD Cloud web service will continue to be communicated. Of these, only those from category "REST (GET)" are needed.

For large clients, we recommend opting for the data transfer via files. Please ask your contact person at the DPD depot for "Scandaten STATUSDATA" on a tracking number level via SFTP on an hourly basis.

DPD UK

Access to the DPD UK API is made using access data that can be used to log in to the MyDPD Local Portal (see screenshot).

To enable the private interface for DPD UK Local, the following two pieces of information are required:

  • Username: User ID for the sender (if applicable, Name of the shop)

  • Password: Associated password

If the username does not work directly, try writing the full username big or small.

Attention: DPD UK is different from DPD UK Local

DPD Austria

DPD Austria currently still features a different setup than the other countries. Hence, we use the interface described as:

Flow type: STATUSDATA (status data central database) File type: CSV with field definition

You key account manager at DPD Austria can have that interface activated. You will receive credentials for a FTP server in return, that need to be provided to parcelLab.

Royal Mail

Due to a current and ongoing restructuring of the interface by Royal Mail, for the time being we recommend using the TDF integration!

For large volume customers we recommend this integration:

TDF (Tracking Data File) Version 2.6

Royal Mail provide the retailer with a set of SFTP credentials. From this SFTP, the data can be retrieved and then needs to be forwarded to parcelLab. For further details, please contact our team at support@parcellab.com

The Tracking API is currently not recommended (see above):

To integrate with Royal Mail, we need the Client ID and Secret of the following interface:

Tracking API V2 (REST)

In order to get the necessary details you have to:

  1. Sign up for an account or login to the Royal Mail API (Developer) Portal: https://developer.royalmail.net/user/login.

  2. Register the application which will be calling the API. When the application is registered, it will be assigned a unique system-generated Client ID and Secret which has to be forwarded to parcelLab.

UK Mail

If you already have an ipostparcels PRO username and password then you can use the same username and password with the API.

To register new usernames and passwords please visit https://www.ukmail.com/register (Live).

Note, if you don't have an account number, your UK Mail account number must be requested through your UK Mail sales executive.

Once you have received an account confirmation, you have to forward the following credentials to parcelLab:

  • Username: Typically the email address you have entered during the registration process,

  • Password: Corresponding password.

GLS Germany

At GLS we use the so-called package tracking via URL / web service, specifically the Track & Trace service. Username and password are required for this interface.

The access data for the interface usually are exactly the access data that can also be used for the portal under gls-group.eu in the section YourGLS / GLS-ONE (see screenshot):

  • Username: Usually a 10-digit number, if necessary followed by a word

  • Password: Associated password

Hermes Germany

For Hermes, we use the interface called SISy-R-API for tracking. Please ask your contact person at Hermes for the activation of this interface. Please also ask for the release of the function GetExpectedDeliveryByID.

As credentials you only get a very long token: usually a 288-digit hexadecimal code.

For large volume clients we recommend opting for status data transfer via flatfiles. Please ask your contact person at Hermes for the STAT files via SFTP with hourly transfer and also "Zustellprognose Flatfiles".

Hermes Austria

For Hermes in Austria (no cross-border shipments, only for domestic shipments), we rely on this interface:

Hermes AT Tracking Data Interface V 2.0

In order to gain access, the key account manager at Hermes needs to be contacted and be supplied with the following two information:

  • IP of server to access Hermes systems

  • Public Key file used for authenticating access

Both will be provided by support@parcellab.com on request.

Hermes UK

In order to retrieve Hermes UK parcel information parcelLab has to authenticate with the following web service:

Parcel tracking Web Service

Please request the following credentials of the interface at your contact at Hermes UK:

  • Group ID

  • Licence Key

UPS

Access to the UPS API is gained via credentials that can be used to log in to the UPS Portal. If no account exists yet, one must first be created.

For private access to the UPS API, an access key must additionally be created. This is done at https://www.ups.com/upsdeveloperkit/manageaccesskeys?loc=en_US using the link "Manage Access Key".

In this template an access key can be generated if none exists yet:

At this point, the UPS system indicates that at first UPS customer numbers must be linked to the existing account.This is done by a self-service verification that requires a current invoice. Afterward, an access key (also called token) is displayed: A 16-character hexadecimal string.

ParcelLab requires the following three credentials:

  • Username: The username for the UPS portal that generated the access key (token).

  • Password: Associated password

  • Access Key: The created token.

FedEx

At first, there must be active access to the FedEx Portal.

This access must then be linked to the sender account. Afterward, you get the first important information, the Account Number.

Secondly, production credentials must be requested for the web service. This happens by clicking on the button Get Production Key. Upon successful request, both the production key and the meter number will be displayed.

Finally, after a successful request of the production key, the production password will be sent to the deposited email address.

TNT

For TNT, we would need you to ask your contact at TNT for the credentials (username and password) for the TNT Express Connect Webservice.

Colis Privé

For Colis Privé, we are using the interface described as:

Electronic Data Exchange between Colis Prive and Customers Version 1.7 or newer Tracking files in \vers_ CUSTOMER

Exchange of data files is handled via SFTP. Hence, you will receive a pair of credentials with username and password and also the address of the server from your key account manager.

Swiss Post

To activate the private interface at Swiss Post, an existing business customer login for the portal is necessary. The Swiss Post Web Service Support can be requested by an email to webservice@swisspost.ch to activate the following interface:

"Track consignments" web service

Subsequently, a new "Technical User" is created in the portal with whose access data the integration of the interface can be carried out.

Austrian Post

Electronic data exchange with Austrian Post is file-based. The following interface can be requested from the contact person at Austrian Post:

Customer interface for the provision of tracking data

The following information must be specified:

Debitor customer number

This is your customer number at Austrian Post

Company name

Name of the own firm

Contact person

Including name, phone number and email

Desired data format

XML

Desired data protocol

SFTP by call of post servers

Time slot for data transmission

Hourly

Post NL

We are working with the Post NL API:

Your account manager at PostNL can request API keys for production with access to the ShippingStatus, Deliverydate, and Timeframe APIs - the number ranges are then assigned directly.

For creation of the credentials, you can also reach out to PostNL's service desk at citservicedesk@postnl.nl

bpost

In order to retrieve bpost parcel information parcelLab has to authenticate with the following web service:

bpack parcel trackingInfo web service.

For authentication, you have to provide parcelLab with the following details:

  • Account ID: E-tailer’s Account ID

  • Password: The password for this interface can be requested by sending an e-mail to shippingmanager@bpost.be.

Chronopost

The following two credentials are required to access the private interface of Chronopost:

  • Chronopost contract number (numéro de contrat)

  • Chronotrace password

If the password is not available, it can be obtained from the responsible Chronopost's sales representative.

PPL Czech Republic

Access to the PPL CZ API is gained via the MyAPI credentials. These must be inquired at ithelp@ppl.cz.

The following data is required:

  • ID: seven-digit number

  • UserName: nine-digit combination of letters and numbers (the first 2-3 letters, if applicable is a combination of the shop name and the remaining numbers are identical to the ID)

The password is identical to the UserName.

It is important, that it's the the MyAPI credentials and not the klient.ppl.cz credentials. Questions regarding the API can be directed to edi.customers@ppl.cz.

Poczta Polska

With the Polish Post, we integrate with their web-service at tt.poczta-polska.pl. The necessary credentials can be requested via email at sledzenie@poczta-polska.pl with providing the following information:

  • Your company name (or name of the company engaged in the contract with Poczta Polska)

  • Number of of shipments per request: 20-50

  • Technical contact details: support@parcellab.com

Pošta Slovenije

With the Slovenian Post we are working the web interface called:

"Shipment Tracking" online service

The required credentials are three entries:

  • Customer number

  • Contract number

  • Branch number

These credentials are provided by your point of contact at Slovenian Post.

Liefery

For Liefery we use Webhooks as data transmission. Thus, you have to provide your contact at Liefery with the format and authentication method by which the data should be sent to parcelLab.

The following authentication method and format should be used:

Liefery authentication
curl -X POST \
https://api.parcellab.com/hook-liefery \
-H 'Content-Type: application/json' \
-H 'token: parcelLab-token' \ // this token will be provided by parelLab
-d '{ "shipment": {} }'

The corresponding token will be provided by parcelLab.