Carrier credentials

To ship with a carrier, you connect it once under Carriers and type in the carrier credentials the carrier gave you. The form asks for different fields for each carrier. This page lists every field, carrier by carrier. Each carrier also has its own step-by-step page under Connect a carrier or integration. Walkthrough with screenshots: Carriers. The Test mode checkbox is explained in Test mode.

You do not choose a sender address here. Add your addresses from the organization menu → Manage → Addresses (Sender addresses). You pick the address on the shipment or on a shipping rule.

Connect a carrier

Open All carriers

In the sidebar, click Carriers, then the All carriers tab. My carriers shows the carriers you have already connected.

Click Connect

Each carrier card has Connect and Learn more. Learn more opens the carrier’s own website. A card marked Deprecated is an older connection that is being phased out. Use the current one instead.

Fill in the form

The Connect carrier window opens. Fill in Carrier name, then the fields under Carrier settings. Fields marked * are under Required fields. The rest are under Optional fields, further down.

Click Connect in the window

You see Carrier connected, and the carrier appears on My carriers marked Connected. If nothing happens when you click Connect, a field marked * is still empty.

Connect carrier window with Carrier name Bring and the required API key and API secret fields — Connect carrier for Bring - the name, then the required API key and API secret

You can connect the same carrier more than once, for example one connection per carrier account or a second one for testing. Give each connection its own name. Every connection counts toward the number of carriers your plan allows (Billing and usage).

Fields on every carrier

Field	Required	What to enter
Carrier name	Yes	The name you see on My carriers and on shipments. It starts filled in with the carrier’s name, and you can change it, for example to “GLS Denmark (test)”.
Brand	No	Shown only when your organization has brands. The help text reads Only this brand can use this carrier. Leave it on No brand (organization-wide) to let every brand use the carrier.

Fields with “Password” or “Secret” in the name hide what you type. The gray text under each field is the carrier’s own description, quoted in the tables below.

Zippendo saves the credentials without checking them with the carrier. A typo shows up the first time you send a shipment with that carrier, as The carrier rejected your login details. Update the carrier credentials under Carriers. Open the carrier, fix the value and click Save (see Edit a carrier below).

Fields by carrier

GLS Denmark

Field	Required	Description in the form
Login name	Yes	GLS customer number used for API authentication (LoginName)
Password	Yes	GLS account password
Customer ID	Yes	GLS customer ID (typically same as login name)
Contact ID	Yes	GLS contact identifier for your account
Test mode	No	Enable test mode (uses GLS test environment)

Full guide: Connect GLS Denmark.

GLS Croatia, Czech Republic, Hungary, Slovakia and Romania (MyGLS)

Connect carrier window for GLS Croatia with Username (email), Password and Client number — GLS Croatia - Username (email), Password and Client number

The five cards GLS Croatia, GLS Czech Republic, GLS Hungary, GLS Slovakia and GLS Romania have the same fields. The description under Username (email) names the card’s country.

Field	Required	Description in the form
Username (email)	Yes	The email address you sign in to MyGLS with (GLS Croatia).
Password	Yes	The password you sign in to MyGLS with.
Client number	Yes	Your GLS client number (digits only), as issued by GLS with your contract and shown in MyGLS.
Test mode	No	Use the MyGLS test environment. Requires a test account from GLS.

A MyGLS login works only on its own country’s card. When you change your MyGLS password, update Password here right away: after five failed sign-ins MyGLS locks the login for a few minutes. Full guide: Connect GLS Croatia, Czech Republic, Hungary, Slovakia or Romania.

Bring

Field	Required	Description in the form
API key	Yes	Your Mybring API key for authentication
API secret	Yes	Your Mybring login ID (email address used as API UID)
Customer number	No	Bring customer number for your account
Return customer number	No	Bring customer number for return shipments
Test mode	No	Turn on test mode for this carrier

API secret is the email address you sign in to Mybring with, not a password. Full guide: Connect Bring.

PostNord

Field	Required	Description in the form
Customer number	Yes	Your PostNord customer number (kundenummer, 8-9 digits)
Country	Yes	Which PostNord country your agreement is with. Pick Denmark, Sweden, Norway or Finland from the list.
Return customer number	No	PostNord customer number for return shipments (if different)
Test mode	No	Turn on test mode

You do not need a PostNord API key. Zippendo provides it. Full guide: Connect PostNord.

DAO Denmark

Field	Required	Description in the form
Customer ID	Yes	DAO customer ID (kundeid)
API password	Yes	DAO API password (kode)
Test mode	No	Use DAO’s test system. Leave off for real shipments.

Full guide: Connect DAO Denmark.

FedEx

Field	Required	Description in the form
API key	Yes	FedEx API key (Client ID) from your FedEx Developer Portal
API secret	Yes	FedEx API secret (Client secret) from your FedEx Developer Portal
Account number	Yes	Your FedEx account number (used to bill shipments and pickups)
Test mode	No	Use FedEx’s test system with test credentials. Leave off for real shipments.

Full guide: Connect FedEx.

UPS

Connect carrier for UPS with Client ID, Client secret and Account number — UPS - Client ID, Client secret and Account number

Field	Required	Description in the form
Client ID	Yes	UPS Client ID from your app on the UPS Developer Portal
Client secret	Yes	UPS Client secret from your app on the UPS Developer Portal
Account number	Yes	Your 6-character UPS shipper account number (used to bill shipments and pickups)
Test mode	No	Use UPS’s test system. Leave off for real shipments.

Full guide: Connect UPS.

DHL Express

Field	Required	Description in the form
Username	Yes	Your DHL Express API username for authentication
Password	Yes	Your DHL Express API password for authentication
Account number	Yes	Your DHL Express account number (shipper account)
Test mode	No	Use the DHL Express test environment (test credentials required)
Location Finder API key	No	Your DHL Location Finder API key from the DHL developer portal. Needed to search for and deliver to DHL Service Points.

Full guide: Connect DHL Express.

Instabox, Budbee and Porterbuddy

These three carriers are part of Instabee and use the same form: one API key and Test mode.

Connect carrier for Instabox with API key and Test mode — Instabox - API key and Test mode

Field	Required	Description in the form
API key	Yes	Your Instabee Integration API key (sent as ‘Authorization: ApiKey <key>‘)
Test mode	No	Use Instabee’s test environment

Paste the key exactly as Instabee gave it to you. Full guides: Connect Instabox, Connect Budbee, Connect Porterbuddy.

Instabox (Legacy API)

This card is marked Deprecated on All carriers, with the note The standalone Instabox API is deprecated. Migrate to the Instabee-powered Instabox integration. Connect Instabox instead if you can.

Field	Required	Description in the form
Client ID	Yes	Your Instabox OAuth client id
Client secret	Yes	Your Instabox OAuth client secret
Customer number	Yes	Your Instabox customer number — used as the parcel id prefix (e.g. PA02)
Test mode	No	Use Instabox’s test environment

Full guide: Connect Instabox (Legacy API).

Matkahuolto

Field	Required	Description in the form
Account number	Yes	Your Matkahuolto sender account number (SenderId). Required for every booking — shipments cannot be created without it.
Test mode	No	Use Matkahuolto’s test environment

You do not need a Matkahuolto user ID or password. Zippendo provides those. Full guide: Connect Matkahuolto.

DPD Polska

Field	Required	Description in the form
Login	Yes	Your DPDServices web-service login, issued by DPD Polska.
Password	Yes	Your DPDServices web-service password.
Payer number (FID)	Yes	Your DPD payer number (master FID). Digits only. Sent on every request.
Payer sub-number (numkat)	No	Payer sub-number billed for shipments. Leave empty to bill the master FID.
DPD Pickup API key	No	Key for DPD’s Pickup (mypudo) point finder. Needed only to search service points and lockers.
Test mode	No	Use DPD’s demo environment

Full guide: Connect DPD Polska.

Royal Mail

Field	Required	Description in the form
API key	Yes	Your Click & Drop API authorisation key (Settings → Integrations → Click & Drop API). Labels through the API require an Online Business Account (OBA).
Click & Drop carrier	No	Only if your Click & Drop account has more than one carrier (OBA number + posting location): the carrier’s name from Settings → Shipping Carriers.
API Portal client ID	No	Client ID of your app on developer.royalmail.net (My Apps). Enables Royal Mail tracking and the Local Collect location finder. Ask your Royal Mail account manager to enable the Tracking and Local Collect products on your account first.
API Portal client secret	No	Client secret of the same developer-portal app. Required for tracking; Local Collect works with the client ID alone.

Royal Mail has no Test mode, because Click & Drop has no test system. You can send shipments without the two API Portal fields. Tracking and the Local Collect search need them. Full guide: Connect Royal Mail.

PostNL

Field	Required	Description in the form
API key	Yes	Your PostNL API key from Mijn PostNL (sandbox keys only work in Test mode).
Customer code	Yes	Customer code as known at PostNL Pakketten (1–6 characters, e.g. DEVC).
Customer number	Yes	Customer number as known at PostNL Pakketten (up to 8 digits).
Collection location	No	6-digit code of the PostNL collection location on your contract, if you have one.
Test mode	No	Use PostNL’s test system with a test API key. Leave off for real shipments.

Every PostNL shipment uses your own PostNL API key. Full guide: Connect PostNL.

DPD Switzerland

Field	Required	Description in the form
User ID	Yes	Your DPD Switzerland user ID for the Label Print service, issued by DPD. Case-sensitive.
Password	Yes	The password issued with the user ID.
Customer number	Yes	The “Invoice Nr.” in the email DPD sent with your login, also printed as “Sender account” on a DPD label. Digits only; a leading KD is removed.
Test mode	No	Use DPD Switzerland’s test environment. Requires test credentials from DPD.

Full guide: Connect DPD Switzerland.

DHL Parcel Benelux

Field	Required	Description in the form
API user ID	Yes	The user ID of your API key, found in My DHL eCommerce under Settings > API keys.
API key	Yes	The secret of the same API key, from My DHL eCommerce under Settings > API keys.
Account number	Yes	Your DHL eCommerce account number, billed for shipments and pickups (e.g. 08500001).
Test mode	No	Use DHL Parcel’s test environment. Requires test credentials from DHL’s sales team; your regular API key does not work there.

My DHL eCommerce shows the key once, when you create it. Creating a new key replaces the old one, so update it here too. Full guide: Connect DHL Parcel Benelux.

DHL eCommerce Europe

Field	Required	Description in the form
Client ID	Yes	The eConnect client ID DHL eCommerce Europe sent you when it set up your API access.
Client secret	Yes	The secret that came with your eConnect client ID.
Customer ID	Yes	Your DHL eCommerce Europe customer ID (EKP or local customer number), for example 5012345678.
Account number	No	Your DHL account number. Fill it in only if DHL asked you to send it with your shipments.
Pricing reference	No	The customer pricing reference DHL gave you for Connect Light, if any.
Developer Portal API key	No	The API key of your app on DHL’s Developer Portal (developer.dhl.com), with Shipment Tracking - Unified, its Push API and Location Finder - Unified added. You need it for tracking and for DHL Parcel Connect ServicePoint.
Cash on delivery account holder	No	Name on the bank account DHL pays cash on delivery amounts into.
Cash on delivery IBAN	No	IBAN of the bank account DHL pays cash on delivery amounts into (SEPA).
Cash on delivery BIC	No	BIC of that bank account.
Cash on delivery bank name	No	Name of the bank that holds that account.
Cash on delivery bank city	No	City of the bank that holds that account.
Test mode	No	Use DHL eCommerce Europe’s test system. It needs the test credentials DHL sends you for it; your live credentials do not work there.

DHL eCommerce Europe’s sales team gives you the client ID and secret: test credentials first, live ones after DHL has approved your test shipments. The Developer Portal API key comes from your own app on DHL’s Developer Portal. Full guide: Connect DHL eCommerce Europe.

DPD Belgium

Field	Required	Description in the form
Login	Yes	Your DPD login (delisId) for DPD Belgium’s web services, issued by DPD Belgium.
Password	Yes	The password issued with the login.
Test mode	No	Use DPD’s test environment. Requires test credentials from DPD Belgium.

DPD Belgium’s Customer IT team ([email protected]) gives you the login, and a separate test login for Test mode. Senders in Luxembourg use DPD Belgium too. Full guide: Connect DPD Belgium.

DPD Hungary

Field	Required	Description in the form
Login	Yes	The API login DPD Hungary issued you.
Password	Yes	The password DPD Hungary issued with the login: a long code of letters and digits.
Customer ID	Yes	Your DPD Hungary customer ID.
Sender address ID	Yes	ID of your registered pickup address at DPD Hungary. The label prints that address.
Customer account number	No	Your DPD Hungary customer account number, if DPD issued one.
Test mode	No	Use DPD’s test environment. Requires test credentials from DPD Hungary.

The label shows the address DPD Hungary has on file for the Sender address ID, not the sender address on the shipment. DPD Hungary’s integration team ([email protected]) gives you the credentials, and separate ones for Test mode. Full guide: Connect DPD Hungary.

DPD Latvia

Field	Required	Description in the form
API token	Yes	An API token from eServiss, DPD’s customer portal: open Token list and create one. DPD shows it only once.
Test mode	No	Use DPD’s test environment. Requires a token from the sandbox eServiss, DPD’s test portal.

Full guide: Connect DPD Latvia.

DPD Lithuania

Field	Required	Description in the form
API token	Yes	An API token from eSiunta, DPD’s customer portal: open Token list and create one. DPD shows it only once.
Test mode	No	Use DPD’s test environment. Requires a token from the sandbox eSiunta, DPD’s test portal.

DPD Lithuania’s support team ([email protected]) links your contract to your eSiunta user. Full guide: Connect DPD Lithuania.

Helthjem

Field	Required	Description in the form
Client ID	Yes	The API client ID Helthjem’s integrations team issued for your webshop ([email protected]).
Client secret	Yes	The API client secret issued together with the client ID.
Shop ID	Yes	Your Helthjem shop ID, a number such as 16, issued together with the API credentials.
Test mode	No	Use Helthjem’s test environment. Requires test credentials from Helthjem; production credentials do not work there.

If you already ship with Helthjem, ask [email protected] for the credentials. New customers apply at helthjem.no/bli-kunde. Full guide: Connect Helthjem.

Posti

Field	Required	Description in the form
Client ID	Yes	From Posti’s Developer Portal (developer.posti.com): the Client ID of the application account user you add for Zippendo. Select both API roles, shippingapi and 2026-04.
Client secret	Yes	The Client secret the Developer Portal shows once, together with the Client ID.
Logistics contract number	Yes	Your Posti logistics contract number, usually six digits starting with 6. Add it to the same application account user in the Developer Portal, or Posti refuses your shipments.
Tracking API username	No	The Tracking API username Posti customer service gives you for your contract. Needed only to track your shipments.
Tracking API password	No	The password Posti sends with the Tracking API username. Posti locks the account for an hour after five failed sign-in attempts.

Posti has no Test mode, because Posti has no test system. Without the two tracking fields you can still send shipments, but no tracking events arrive. Full guide: Connect Posti.

Danske Fragtmænd

Field	Required	Description in the form
API username	Yes	The API username Danske Fragtmænd issued for your agreement (ask [email protected]). Enter it without the Fragt\ prefix; Zippendo adds it.
API password	Yes	The password issued with the API username.
Agreement number	Yes	Your Danske Fragtmænd agreement number (aftalenummer), 8 or 12 digits.
Hub	Yes	The two-letter hub your agreement belongs to, for example AR or GL.
Label size	No	The label your printer takes: 10 x 15 cm (default) or 10 x 19 cm. Options: 10 x 15 cm, 10 x 19 cm.
Test mode	No	Use Danske Fragtmænd’s test environment. Requires a separate test API user from Danske Fragtmænd.

Full guide: Connect Danske Fragtmænd.

DSV XPress

Field	Required	Description in the form
Subscription key	Yes	Primary key of your Booking - XPress subscription on developer.dsv.com (Profile page). DSV uses the same address for demo and production: enter your demo keys to test.
Booking service key	Yes	The Booking key shown on the API profile page of the XPress portal (demo.xpress.dsv.com for demo, xpress.dsv.com for production).
Personal access token	Yes	Your personal access token, shown on the API profile page of the XPress portal (demo.xpress.dsv.com for demo, xpress.dsv.com for production).
Account number	Yes	Your DSV XPress account number, digits only. Set the label format to 10x15 in your XPress user settings.
Tracking subscription key	No	Primary key of your Tracking - XPress subscription, if DSV issued a separate one.
Tracking service key	No	The Tracking key shown on the API profile page of the XPress portal (demo.xpress.dsv.com for demo, xpress.dsv.com for production). Shipments are not tracked without it.

DSV XPress has no Test mode. To test, connect your demo keys as a separate carrier. Full guide: Connect DSV XPress.

DSV Road

Field	Required	Description in the form
myDSV username	Yes	The myDSV login DSV enabled for API access (usually an email address).
myDSV password	Yes	The password of that myDSV login.
Customer number (MDM)	Yes	Your 10-digit DSV customer number. DSV’s demo sign-up email contains a test number.
Access token subscription key	Yes	Primary key of your subscription on developer.dsv.com (Profile page) to “Fetch DSV Access token”.
Booking subscription key	Yes	Primary key of your subscription on developer.dsv.com (Profile page) to “Booking”.
Labels subscription key	Yes	Primary key of your subscription on developer.dsv.com (Profile page) to “Labels”.
Tracking subscription key	No	Primary key of your subscription on developer.dsv.com (Profile page) to “Tracking”. Shipments are not tracked without it.
Road product code	No	The Road product code in your DSV agreement, if DSV gave you one.
myDSV template	No	A booking template DSV set up for you in myDSV, if any.
Test mode	No	Use DSV’s demo environment. Requires the demo login and keys from DSV’s sign-up email.

Full guide: Connect DSV Road.

DSV Road (DB Schenker)

Field	Required	Description in the form
Booking subscription key	Yes	Primary key of your subscription on developer.dsv.com (Profile page) to “Booking - Connect”.
Connect access key	Yes	The access key from Usage Registration → Maintain User - Customer → Access Key in myDSV (formerly Schenker Connect).
Tracking subscription key	No	Primary key of your subscription on developer.dsv.com (Profile page) to “Tracking - Connect”. Shipments are not tracked without it.
User group ID	No	Your Connect user group ID, if your Connect administrator says shipments need one.
Test mode	No	Use DSV’s Connect test environment. Requires the test access key and subscription keys from DSV.

Full guide: Connect DSV Road (DB Schenker).

Edit a carrier

On My carriers, click Edit carrier on the carrier. The Edit carrier page has two sections:

General - Carrier name and, when your organization has brands, Brand.
Carrier settings - the same carrier fields as when you connected, including Test mode. The saved values are shown, so you can check them for typos.

Change what you need and click Save. You see Carrier updated. If saving fails with You’re over your plan’s limits. Upgrade your plan or remove what you no longer use., your organization has more carriers than its plan allows (for example after a downgrade). Upgrade, or delete a carrier you no longer use. Label format and printers are not set here. They live on the shipment and under Printers.

Delete a carrier

Open the carrier

On My carriers, click Edit carrier, then Delete at the top of the page.

Confirm

The Delete carrier window asks you to type the carrier name in capital letters, for example GLS DENMARK. Type it and click Delete.

You see Carrier deleted. Shipments you already sent keep their labels and tracking numbers.

Deleting a carrier also deletes every shipping rule that uses it. To change credentials or switch from test to live, edit the carrier instead.

If something goes wrong

What you see	What to do
Nothing happens when you click Connect	Fill in Carrier name and every field marked *.
You’ve reached your plan’s limit. Upgrade your plan or remove something you no longer use.	Your plan allows a set number of carriers: Free 1, Standard 3, Growth 8, Pro and Enterprise unlimited. Upgrade or delete a carrier you no longer use. See Billing and usage.
Couldn’t connect the carrier. Try again.	Try again in a moment.
Carrier not found. when you delete a carrier	A carrier with booked pickups cannot be deleted. Contact support if you need it removed.
The carrier rejected your login details. Update the carrier credentials under Carriers. (when you send a shipment)	Open the carrier with Edit carrier, check each value against what the carrier gave you, check that Test mode matches the kind of credentials you have, and click Save. More in Carrier authentication failures.

Your carrier is not on the list

Click Carrier requests in the sidebar and request the carrier.

Connect a carrier or integration - one page per carrier
Test mode - testing with the carrier’s test system
Carrier products and services - you choose products on the shipment or shipping rule, not on this form
Carriers - the walkthrough
Carrier authentication failures

​Connect a carrier

​Fields on every carrier

​Fields by carrier

​GLS Denmark

​GLS Croatia, Czech Republic, Hungary, Slovakia and Romania (MyGLS)

​Bring

​PostNord

​DAO Denmark

​FedEx

​UPS

​DHL Express

​Instabox, Budbee and Porterbuddy

​Instabox (Legacy API)

​Matkahuolto

​DPD Polska

​Royal Mail

​PostNL

​DPD Switzerland

​DHL Parcel Benelux

​DHL eCommerce Europe

​DPD Belgium

​DPD Hungary

​DPD Latvia

​DPD Lithuania

​Helthjem

​Posti

​Danske Fragtmænd

​DSV XPress

​DSV Road

​DSV Road (DB Schenker)

​Edit a carrier

​Delete a carrier

​If something goes wrong

​Your carrier is not on the list

​Related

Connect a carrier

Fields on every carrier

Fields by carrier

GLS Denmark

GLS Croatia, Czech Republic, Hungary, Slovakia and Romania (MyGLS)

Bring

PostNord

DAO Denmark

FedEx

UPS

DHL Express

Instabox, Budbee and Porterbuddy

Instabox (Legacy API)

Matkahuolto

DPD Polska

Royal Mail

PostNL

DPD Switzerland

DHL Parcel Benelux

DHL eCommerce Europe

DPD Belgium

DPD Hungary

DPD Latvia

DPD Lithuania

Helthjem

Posti

Danske Fragtmænd

DSV XPress

DSV Road

DSV Road (DB Schenker)

Edit a carrier

Delete a carrier

If something goes wrong

Your carrier is not on the list

Related