Supported Carriers

DHL Express

For DHL Express, parcelLab retrieves status information using the DHL Express Global Web Services interface.

The following areas are needed:

• Trackingrequest (Track & Trace)

• Documentretrieve EPOD (proof of delivery)

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

• Account number

• Username

• Password

FedEx

For FedEx, parcelLab retrieves status information using the FedEx web service.

Access to the FedEx web service is gained via obtaining active access to the FedEx portal. This access must then be linked to the sender account, which provides the account number.

Production credentials must then be requested for the web service. This happens by clicking the Get Production Key button. 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 email address provided.

TNT

For TNT, parcelLab retrieves status information using the TNT Express Connect web service.

For this interface, access data must be requested from your key account manager at TNT.

You will receive a username and password for access that need to be shared with parcelLab.

UPS

For UPS, parcelLab retrieves status information using the UPS API.

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

To obtain the credentials:

1. Navigate to the UPS Developer Portal.

2. Click Create an Application on the home page or select Apps from your profile menu.

3. In the first dropdown list, select I want to integrate UPS technology into my business.

4. In the second dropdown list, select the associated shipping account.

5. Click Next. Contact information fields will display.

6. Enter the contact information of your company’s point of contact.

7. Select the Tracking API to be added to your application.

8. After saving your application, UPS generates a Client ID and Client Secret.

The client ID and client secret must be shared with parcelLab to access the UPS API.

OnTrac

For OnTrac, parcelLab retrieves status information using the Web Service Integration.

For this interface, access data must be requested from your contact at OnTrac.

You will receive a username and password for access that needs to be shared with parcelLab.

When asking for those credentials, please mention that the parcelLab integration follows the OnTrac Application Restrictions:

• parcelLab only tracks shipments that are already tendered to OnTrac

• After successful delivery, shipments are not tracked anymore

• Shipments are tracked at a maximum of five times per day

• No historical data is retrieved through the integration

DHL Germany

For DHL Germany, parcelLab retrieves status information using the DHL private interface. This interface is called DHL Parcel DE Tracking (Post & Parcel Germany).

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

• ZT-ID - the User ID for the sender (for example: ZT123456)

• Passwort - the associated password

This access is also the login to the web portal for the business customers' Track & Trace. To use this interface, you need business customer access. The activation of the interface must be explicitly requested from your DHL sales contact.

When 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.

DPD Germany

For DPD Germany, parcelLab retrieves status information using the DPD private interface.

Activation of this interface in live operation must be requested from your contact at the DPD depot for the following:

• DPD Cloud Web Service for Tracking (provision of information/DPD Tracking Service)

Note: You need to state that this is the parcelLab partner interface.

DPD provides the following credentials, which are needed to retrieve the interface through parcelLab:

• UserCredentials CloudUserID - a six- to eight-digit number.

• UserCredentials Token - a 15-digit alpha-numeric code.

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

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

GLS Germany

For GLS Germany, parcelLab retrieves status information using the URL/web service, specifically the Track & Trace service.

The username and password are required for this interface. The access data for the interface is usually the username and password that can also be used for the portal under gls-group.eu in the YourGLS/GLS-ONE section as follows:

• Username - the username (usually a 10-digit number, if necessary followed by a word)

• Password - the associated password

Hermes Germany

For Hermes Germany, parcelLab retrieves status information using the SISy-R-API interface.

Activation of this interface must be requested from your contact at Hermes.

Note: You also need to ask for the release of the GetExpectedDeliveryByID function.

As credentials you get a token, which is usually a 288-digit hexadecimal code.

For large volume clients, we recommend opting for status data transfer via flat files. You will need to ask your contact at Hermes for the STAT files via SFTP with hourly transfer and also "Zustellprognose Flatfiles".

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 - the name of your company

• Contact person - the contact person, including name, phone number, and email address

• Desired data format - .xml

• Desired data protocol - SFTP by call of post servers

• Time slot for data transmission - hourly

DPD Austria

DPD Austria currently features a different setup than the other countries. Therefore, parcelLab retrieves status information using the interface described as follows:

• Flow type: STATUSDATA (status data central database)

• File type: CSV with field definition

Activation of this interface must be requested from your key account manager at DPD Austria. You will receive credentials for a FTP server in return, that need to be provided to parcelLab.

Hermes Austria

For Hermes Austria (no cross-border shipments, only for domestic shipments), parcelLab retrieves status information using the following interface:

• Hermes AT Tracking Data Interface v2.0

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

• IP of server to access Hermes systems

• Public Key file used for authenticating access

Please fill in our contact form and both will be provided on request.

Swiss Post

For Swiss Post, parcelLab retrieves status information using the Swiss Post private interface.

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 [email protected] 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.

DPD UK

For DPD UK, parcelLab retrieves status information using the DPD UK API.

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

To enable the private interface for DPD UK Local, the following information is required:

• Username - the User ID for the sender (if applicable, name of the shop)

• Password - the associated password

If the username does not work directly, try writing the full username in upper case or lower case.

Important: DPD UK is different from DPD UK Local.

Evri UK (previously Hermes)

For Evri UK, parcelLab retrieves status information using the Parcel Tracking Web Service interface.

You will have to provide Evri with a list of IPs to be whitelisted:18.197.59.25 and 3.123.172.160.

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

• Group ID

• Licence key

For large volumes, we recommend opting for another interface called:

• HDI Parcel Tracking Batch File

Data transfer will be set up via FTP by Evri.

UK Mail

For UK Mail, parcelLab retrieves status information using the UK Mail API.

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, go to https://www.ukmail.com/register (live).

Note: If you do not have an account number, your UK Mail account number must be requested through your UK Mail sales executive.

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

• Username - typically the email address you have entered during the registration process

• Password - the associated password

Chronopost

For Chronopost, parcelLab retrieves status information using the Chronopost private interface.

The following 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 your Chronopost sales representative.

Colis Privé

For Colis Privé, parcelLab retrieves status information using the following interface:

• Electronic Data Exchange between Colis Privé and Customers v1.7 or newer with tracking files in \vers_ CUSTOMER

Data transfer is provided via SFTP. Therefore, you will receive a pair of credentials with username and password and also the address of the server from your key account manager.

Mondial Relay

For Mondial Relay, parcelLab retrieves status information using the following interfaces:

• WEB SERVICE Parcel tracking (WSI2_TracingColisDetaille)

• Point Relais search (WSI3_PointRelais_Recherche)

This access is granted through the following credentials:

• Enseigne (brand) - the merchant ID code, eight fixed characters

• Private key - a secret key required for authentication

With these credentials, the parcelLab system can generate the security key needed for accessing the status information.

SEUR

For SEUR, parcelLab retrieves status information using the Shipments Trace and Tracking SEUR Web Service interface.

For this interface, access data must be requested from your contact at SEUR.

You will receive the following credentials for access that needs to be shared with parcelLab:

• User - the user, an alphanumeric value (min four characters - max 25 characters)

• Password - the associated password, an alphanumeric value (min six characters - max 12 characters)

GLS Italy

For GLS Italy, parcelLab retrieves status information using the GLS Italy Track & Trace interface.

The following data is required to get access to this interface:

• codicecontratto/contract code - this is your GLS Italy contract code

• siglasede - a set of alphanumeric codes for all departure locations

bpost

For bpost, parcelLab retrieves status information using the following interface:

• bpack parcel trackingInfo web service

For authentication, you must provide parcelLab with the following details:

• Account ID - the e-tailer’s account ID

• Password - the password for this interface can be requested by sending an email to [email protected].

DPD BeNeLux

For DPD BeNeLux/DPD Netherlands, parcelLab retrieves status information using the following interface:

• DPD Integration Services/Parcel LifeCycle Service

For authentication, you must provide parcelLab with the following details:

• DelisId - Delis ID provided by DPD

• Password - the password associated with the Delis ID

• customerUid - the customer ID provided by DPD

Post NL

For Post NL, parcelLab retrieves status information using 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 [email protected].

DHL Poland

DHL Poland currently features a different setup than the other countries. Therefore, parcelLab retrieves status information using the following interface:

• DHL Poland TntWebService (DHL Express Poland Web Service T&T)

For this interface, access data must be requested from your contact at DHL Poland.

DHL provides the following credentials, which are needed to retrieve the interface through parcelLab:

• clientId - the unique ID of the DHL customer

• password - the password connected with the clientId that allows to find shipments

Poczta Polska

For Polish Post, parcelLab integrates with their web service at tt.poczta-polska.pl. The necessary credentials can be requested via email at [email protected] by 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: [email protected]

PPL

For PPL, parcelLab retrieves status information using the PPL CZ API.

Access to the PPL CZ API is gained via the MyAPI credentials. These credentials can be requested via email at [email protected].

The following data is required:

• ID - a seven-digit number

• UserName - a nine-digit combination of letters and numbers (the first two-three 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 is the MyAPI credentials and not the klient.ppl.cz credentials.

Note: Questions regarding the API can be directed to [email protected].

Pošta Slovenije

For Slovenian Post, parcelLab retrieves status information using the following interface:

• Shipment Tracking online service

For this interface, access data must be requested from your contact at Slovenian Post.

The following credentials are required:

• Customer number

• Contract number

• Branch number

CargoLine

For shipments from CargoLine (a group of freight carriers), parcelLab retrieves status information using the following interface (German name):

• Datensatz für Statusberichte – Release 100 (Package-Header-Satz: ‘STAT512’)

Data transfer is usually provided via FTP or SFTP.

Dachser

For shipments from Dachser, parcelLab retrieves status information using the following interface:

• Statusdaten CSV v2.0.1 (2014-07-14)

Data transfer is provided via FTP by Dachser.

DB Schenker

For shipments from DB Schenker, you need to request the following access via your contact at DB Schenker:

• EDIFACT IFTSTA D.96A

Subsequently, you will receive access data to Schenker's FTP server, which usually consists of a server (usually edi-cc.dbschenker.com), path (usually/ out / iftsta), a user and password.

Gebrüder Weiss

For shipments from Gebrüder Weiss, parcelLab retrieves status information using the following interface:

• BORD512 via EDI including parcel numbers in RFF+CW with the parcelLab-setup

This interface must be created for each customer individually, which may involve costs. Please request this interface from your contact at Gebrüder Weiss and contact the parcelLab team.

Hellmann

For shipments from Hellmann, you need to request the following access via your contact at Hellmann:

• EDIFACT IFTSTA D.96A

Subsequently, you will receive access data to Hellmann's FTP server, which usually consists of a server (usually a CNAME on hellmann.net), path (usually/out/iftsta), a user and password.

IDS Systemlogistik

For shipments from IDS (freight forwarders), parcelLab retrieves status information using the following standardized IDS interface:

• elix/IDS Flatfile Interface

Data transfer is usually provided via FTP or SFTP.

Inntralog

For shipments from Inntralog, our setup requires the transfer of status data with the event codes IMP, WEC, WED, WEP, VSF, WED, AVV, AVS, ABG, AKL, AVW, and KNA via SFTP.

Kühne+Nagel

For shipments from Kühne+Nagel, status data is provided according to the EDIFACT IFTSTA specification via SFTP, that can be used by parcelLab.

Rhenus

For shipments from Rhenus Logistics, the interface works with the STAT512 format (release 100 or higher). Please ask your account manager to activate all status codes 1xx to 9xx.

Data transfer is provided via SFTP by Rhenus. You will receive a username, password, and server name that need to be forwarded to parcelLab.

BJS Home Delivery

For shipments from BJS Home Delivery, parcelLab retrieves status information using the Events CSV interface. Data transfer is provided via SFTP.

DHL 2-Mann-Handling

For shipments from DHL 2-Mann-Handling, parcelLab retrieves status information using the DHL web interface. For this interface to be accessible, parcelLab need the DHL Freight-internal tracking number in the format 60<12 digits>.

Dynalogic

For shipments from Dynalogic, parcelLab retrieves status information using the following interface:

• GetTransportOrderActivities web service

Data transfer for Dynalogic trackings is provided via API web server that requires credentials to authenticate with.

For this interface, access data must be requested from your contact at Dynalogic.

You will receive the following credentials for access that needs to be shared with parcelLab:

• loginName

• Passwort

Hermes Einrichtungs-Service

For shipments from Hermes Einrichtungs-Service (HES), parcelLab retrieves status information using the StatusDepCSV interface as of 31.07.2014. Data transfer is provided via FTP access. The credentials for this FTP server will be provided to the shipper and need to be forwarded to parcelLab.

We need both the confirmation files with the filename pattern <VersenderID>-YYYY-MM-DD-HH-mm.csv listing the tracking URL and the status files with the filename pattern sdgstat-<VersenderID>-YYYY-MM-DD-HH-mm.csv.

Rhenus Home Delivery

For shipments from Rhenus Home Delivery, please ask for the parcelLab interface as XML via SFTP. Rhenus will upload status files directly to a parcelLab server, and our Support team will provide you with access credentials beforehand.