Shipium Webhooks
Receive real-time event notifications from Shipium at an endpoint you specify.
About Shipium webhooks
Shipium supports an event-driven model for certain workflows, allowing your systems to receive automatic notifications when key events occur — without needing to poll Shipium's APIs. When a supported event happens, Shipium sends an HTTP POST request with event details to the endpoint URL you configure.
Webhooks are available for the following Shipium products:
- Webhooks for Carrier Selection & Label Updates. Receive notifications when carrier selections or labels are created, updated, or deleted.
- Webhooks for Tracking. Receive real-time tracking status updates as they occur.
- Webhooks for Billing Management. Receive notifications when invoices are created, finalized, or voided.
- Webhooks for Pack App Order Lifecycle. Receive notifications when Pack App order statuses change.
Each webhook type is registered and managed separately, reflecting the distinct workflows and event types of each product. Refer to the individual pages above for registration steps, event type details, and sample payloads.
Where to register your webhook
Webhook registration is managed within the Shipium Console for the product associated with the webhook type you need:
- Carrier Selection & Label webhooks. Accessible from the main Shipium Console under Carrier Selection > Carrier Selection Webhooks
- Tracking webhooks. Accessible from the main Shipium Console under Tracking > Webhooks
- Billing Management webhooks. Accessible from the Billing Management application under Billing Webhooks
- Pack App webhooks. Contact your Shipium representative to configure
How webhooks work
When a supported event occurs in Shipium, the platform sends an HTTP POST request to your registered endpoint URL containing a JSON payload with event details. Custom headers — such as authentication tokens or secret keys used to verify the request — can be configured per webhook to secure delivery to your endpoint. Your endpoint must respond with an HTTP status code in the 200–299 range to acknowledge receipt.
Shipium employs automated retry logic if delivery fails. Refer to the individual webhook documentation pages for the retry policy applicable to each webhook type.
Custom HTTP headers
If your endpoint requires authentication or custom routing headers, you can configure additional HTTP headers as part of your webhook setup in the Shipium Console. These headers are included in every webhook request Shipium sends to your endpoint.
For instructions on generating and configuring custom headers — including how to set up HTTP Basic Authentication — see Configure Custom HTTP Headers for Webhooks.
Related documentation
- Webhooks for Carrier Selection & Label Updates
- Webhooks for Tracking
- Webhooks for Billing Management
- Webhooks for Pack App Order Lifecycle
- Configure Custom HTTP Headers for Webhooks
Resources
Your Shipium team member is available to help along the way. However, you might find these resources helpful:
Updated 16 minutes ago