Skip to main content
You need a client_id and client_secret for your merchant account. They are issued from the DropHub console — a credential cannot mint its successor, so there is no API for creating one.
1

Get a token

The token is a short-lived JWT. Cache it and reuse it until shortly before expires_in elapses — see Authentication.
2

Create a shipment

An order reference, where to collect, where to deliver, and who receives it. Nothing else is required.
201 means created. 200 means DropHub already had this order and you are seeing the original shipment — your reference is the idempotency key.
trackingUrl is the customer-facing link. It is minted automatically — send it to your buyer.
3

Register a webhook

Do this once, not per shipment. The signing secret is returned exactly once.
Omitting events subscribes you to all seven. Store signingSecret immediately — see Webhooks for how to verify a delivery.
4

Follow the shipment

Webhooks are the primary mechanism. Poll only when you need a snapshot on demand:
See Tracking for locationStatus and the polling interval the server asks you to honour.
Build against the sandbox at https://api-test.drop-hub.com and certify there before pointing at production. Credentials are not interchangeable between the two — see Environments.

Next

Shipments

Parcel details, COD, saved pickups, and pickup windows.

Cancellation

When a shipment can still be called back.