Webhooks
Webhooks push events to your systems (ERP, TMS, BI, ...) as soon as something changes in IMPARGO, so you don't have to poll the API.
IMPARGO sends a signed JSON POST request to your HTTPS endpoint for every event you subscribed to.
The wire format follows the Standard Webhooks specification v1.0.
You can verify requests with the official standardwebhooks libraries, which exist for most languages (see Verifying signatures).
Webhooks are available in the Business plan. Each company can register up to 10 webhooks.
Setting up a webhook
- In CargoApps, go to Settings → Account Settings → Webhooks (company admins only).
- Click New webhook, enter your endpoint URL (must start with
https://), select the events and enter up to 5 notification emails. These addresses are notified when the webhook starts failing and when it is disabled (see Delivery and retries). Optionally give the webhook a name (up to 40 characters, e.g.ERP order sync) so you can tell your webhooks apart in the delivery log. - Copy the signing secret (
whsec_…). It is only shown once. You need it to verify requests. - Create or update an order to receive your first event.
From the webhooks table you can also pause a webhook (active toggle), edit it, roll its secret or delete it. The deliveries of the last 14 days are listed in the Deliveries tab.
Events
companyorder.created: An order was created.companyorder.updated: An order was updated (including archiving).companyorder.status_changed: The status of an order changed.companyorder.deleted: An order was deleted.companyorder.document_uploaded: Documents were uploaded to an order by a driver (DriverApp), a shipper (ShipperPortal) or a partner (shared order link). Documents uploaded by your own dispatchers via the CargoApps triggercompanyorder.updatedinstead.customer.created: A customer was created.customer.updated: A customer was updated.customer.deleted: A customer was deleted.partner.created: A partner was created.partner.updated: A partner was updated.partner.deleted: A partner was deleted.
The payload of every event is described in Event types.
A machine-readable OpenAPI 3.1 description of all events is available at /webhooks/openapi.json.
Lean payloads
Webhook payloads are deliberately small: they only contain the ID and a few key fields. To get the full object, fetch it via the GraphQL API (see Fetching data after a webhook). This way you always work with the current state of the object, even if an event arrives late or out of order.
Example body of a companyorder.updated event:
{
"type": "companyorder.updated",
"timestamp": "2026-10-12T08:15:30.000Z",
"data": {
"companyId": "64b7f0c2a1b2c3d4e5f60700",
"object": {
"id": "64b7f0c2a1b2c3d4e5f60718",
"reference": "ORD-2026-0042",
"status": "PLANNED",
"archived": false,
"deleted": false,
"updatedAt": "2026-10-12T08:15:30.000Z"
}
}
}
type: the event type.timestamp: when the event happened (not when it was delivered).data.companyId: your company ID.data.object: the lean object.
The event ID is not part of the body. It is sent in the webhook-id header and stays the same across retries.
Responding to webhooks
Respond with any 2xx status code within 15 seconds. Process the event asynchronously if it takes longer.
Any other response (including redirects) or a timeout counts as a failed delivery and is retried, see Delivery and retries.