User Manual
Help Center/User Manual/Connector directory: carriers & shipping aggregators

Connector directory: carriers & shipping aggregators

Last updated 2026-10-20

Direct carrier connections (UPS, FedEx, USPS, DHL) and one-key aggregators (Shippo, EasyPost, ShipEngine, ShipStation, Easyship, AfterShip, Sendle): the exact fields each wizard asks for and where to get them.

Two ways to ship from Docklify: connect a carrier directly with your own carrier account (rates are quoted and labels billed against that account), or connect an aggregator with a single API key and ship through the carriers enabled in your aggregator account. Either way, a connection with no credentials runs in simulation mode — rates and labels are clearly marked as simulated, and a test without real keys never reports a fake success.

Carriers (direct)#

UPS

Live rates, labels and tracking through the UPS API, quoted against your own UPS account. The full step-by-step guide is “Connect UPS” in this section; the field summary:

FieldRequired?Where to get it
Client IDRequiredUPS Developer Kit → create an app → OAuth credentials
Client SecretRequiredSame app page in the Developer Kit
Shipper Number (Account Number)RequiredYour 6-character UPS account number — on any UPS invoice

UPS offers separate test and production credentials — keep them in separate connections and pick the right environment when you test.

No credentials yet? You can still rehearse the whole flow in Docklify: create the UPS account first and leave the key fields empty — rates in the Ship dialog, labels and tracking then run in a clearly marked practice mode. Practice rates are estimates for training only (shown with a “Simulated” tag), practice labels carry a large DEMO watermark and cannot be used to ship, and practice tracking shows a sample timeline. As soon as you save real credentials, everything switches to live UPS data automatically.

FedEx

Live rates, labels and tracking through the FedEx API, against your own FedEx account.

FieldRequired?Where to get it
API Key (Client ID)RequiredFedEx Developer Portal → My Projects → your project → API credentials
Secret Key (Client Secret)RequiredSame credentials page; shown once when the project is created
Account NumberRequiredYour FedEx account number — on any FedEx invoice

FedEx works with live data only — there is no practice mode. Fill in the API Key, Secret Key and Account Number above and save; rates, labels and tracking then run against your FedEx account right away. If the credentials are missing or incomplete, Docklify will ask you to add them first, before rating, buying a label or tracking.

USPS

Rates, labels and tracking through the USPS APIs. OAuth credentials get you rates and tracking; buying labels additionally needs your USPS payment account identifiers (CRID / MID / EPS).

FieldRequired?Where to get it
Consumer KeyRequiredUSPS Developer Portal → Apps → your app
Consumer SecretRequiredSame app page
CRIDOptionalYour USPS Customer Registration ID — from your USPS business account / BCG profile; needed to buy labels
MIDOptionalYour USPS Mail ID — from the same business account profile
EPS Account NumberOptionalYour USPS Enterprise Payment System account number — labels are billed against it

DHL Express

Rates, labels and tracking through the MyDHL API (Express). Credentials are issued by DHL — there is no self-service key page.

FieldRequired?Where to get it
UsernameRequiredIssued by your DHL account representative for MyDHL API access (Basic Auth)
PasswordRequiredIssued together with the username
Account NumberRequiredYour DHL Express account number — on any DHL invoice

Shipping aggregators (one key, many carriers)#

With an aggregator you keep one connection and one API key; which carriers you can actually ship with depends on the carriers enabled in your aggregator account. Test keys (sandbox) rate and label with sample data; live keys create real, billed labels — ShipStation in particular has no sandbox, so treat its key as live from the start.

Shippo

Rates, labels and tracking across the carriers in your Shippo account, with one API token.

FieldRequired?Where to get it
API TokenRequiredShippo dashboard → Settings → API → API tokens. Test tokens start with shippo_test_, live tokens with shippo_live_

EasyPost

Rates, labels and tracking across the carriers in your EasyPost account, with one API key.

FieldRequired?Where to get it
API KeyRequiredEasyPost dashboard → Settings → API Keys. Test keys start with EZTKtest, production keys with EZTKprod

ShipEngine

Rates, labels and tracking across the carriers in your ShipEngine account, with one API key. Sandbox keys (starting with TEST_) produce sample labels you can practise the whole flow on.

FieldRequired?Where to get it
API KeyRequiredShipEngine dashboard → Settings → API Management → API keys

ShipStation

Rates and labels through your ShipStation account (V2 API). Important: ShipStation V2 has no sandbox — labels created with this key are real and billed.

FieldRequired?Where to get it
API KeyRequiredShipStation → Settings → Account → API Settings → API keys (V2)

Easyship

Rates, labels and tracking across the carriers in your Easyship account, with one access token. Easyship’s sandbox is a separate environment with its own token.

FieldRequired?Where to get it
Access TokenRequiredEasyship dashboard → Settings → API Integration / developers → access token (production tokens start with prod_)

AfterShip (Postmen)

Rates and labels through your Postmen (AfterShip Shipping) account. Postmen does not offer a tracking API — use it for rating and labels, and track in the carrier or in Docklify’s tracking views.

FieldRequired?Where to get it
API KeyRequiredPostmen dashboard → Settings → API (sent as the as-api-key header)
Shipper Account SlugOptionalThe slug of the carrier account in Postmen to ship with, if you have several

Sendle

Labels and tracking with Sendle (AU / US / CA). Sendle has no rate-shopping API — quotes come back per order when you create it.

FieldRequired?Where to get it
Sendle IDRequiredSendle dashboard → Settings → API (your Sendle ID)
API KeyRequiredSame API settings page (used with the Sendle ID as Basic Auth)