Getting Started
1
Subscribe to webhooks
Create a webhook to subscribe to an event and define a subscription URL.
2
Receive Webhook Events
When the event occurs, ShipBob sends a
POST request to your subscription URL with relevant data.3
Acknowledge Receipt
Your system should return a
2XX response to confirm successful receipt.4
Handle Retries
If no
2XX response is received, ShipBob retries delivery using an exponential backoff strategy.Key Concepts
- Subscription: A request to receive webhook notifications at a specified URL.
- Subscription URL: The endpoint where webhook data is sent.
- Event: A trigger that generates webhook data (e.g., an order being shipped).
- Topic: The category of event data being sent.
- Payload: The actual event data sent in the webhook.
- Response: A
2XXHTTP response is required to confirm webhook receipt.
Common Use Cases
- ✅ Real-time Order Tracking - Receive
order_shippedandshipment_deliveredevents to provide live tracking updates to customers. - ✅ Inventory Management - Monitor
shipment_exceptionevents to detect and respond to stock shortages. - ✅ Automated Customer Notifications - Trigger automated emails or SMS notifications when shipments are delayed (
shipment_onhold) or delivered (shipment_delivered). - ✅ Order Cancellation Handling - Use
shipment_cancelledevents to update your system when a shipment is canceled. - ✅ Multi-Channel Support - Filter webhook data by sales channel to manage orders from different platforms separately.
Webhook Topics & Events
| Topic | Description | Scopes Required |
|---|---|---|
order_shipped | Fires when a shipping label is purchased, printed, and scanned. If the order is split into multiple shipments, this fires per shipment. | orders_read |
shipment_delivered | Fires when a shipment is delivered to the customer. | orders_read or fulfillments_read |
shipment_exception | Fires when a shipment is moved to exception status (e.g., out-of-stock items). | orders_read or fulfillments_read |
shipment_onhold | Fires when a shipment moves to On-Hold status due to missing information (e.g., address issues). | orders_read or fulfillments_read |
shipment_cancelled | Fires when a shipment is canceled. Does not fire for manually canceled or imported orders. | orders_read or fulfillments_read |
Webhook Headers
ShipBob sends webhook notifications with the following headers:Webhook Payloads (Example Responses)
Unless specified in the table above, the webhook notification sends the full data model of the underlying resource, that is available in the GET endpoint.Body sample for order_shipped topic:
Body sample for order_shipped topic:
Body sample for shipment_delivered topic:
Body sample for shipment_delivered topic:
Body sample for shipment_onhold topic:
Body sample for shipment_onhold topic:
Body sample for shipment_exception topic:
Body sample for shipment_exception topic:
Body sample for shipment_cancelled topic:
Body sample for shipment_cancelled topic:
Retry Schedule
Each message is attempted based on the following schedule, where each period is started following the failure of the preceding attempt:- Immediately
- 5 seconds
- 5 minutes
- 30 minutes
- 2 hours
- 5 hours
- 10 hours
- 10 hours (in addition to the previous)

Static Source IP Addresses
In case your webhook receiving endpoint is behind a firewall or NAT, you may need to allow traffic from static IP addresses. This is the full list of IP addresses that webhooks may originate from.Best Practices
✅ Use HTTPS - Subscription URLs must support SSL. Use RequestBin for testing if needed. ✅ Implement Redundancy - Webhooks may be delayed or lost. UseGET endpoints to periodically reconcile data.
✅ Retry Handling - Events may arrive out of order due to retries—handle them as independent updates.
✅ Use Idempotency - Store webhook event ids and discard duplicates to prevent redundant processing.
✅ Logging & Monitoring - Log webhook requests and responses to diagnose issues.
Troubleshooting Guide
Webhook Not Triggering?
Webhook Not Triggering?
- Ensure your subscription URL is correct and publicly accessible.
- Confirm your app
returns a 2XX responseto ShipBob’sPOSTrequest. - Verify that your app
has the correct webhooks_read or webhooks_write permissions.
Webhook Retries Are Overloading My Server
Webhook Retries Are Overloading My Server
- Ensure your system processes events efficiently and responds within 5 seconds.
- Return a
2XXresponse before doing heavy processing.
Webhook Data is Out of Order
Webhook Data is Out of Order
- Use timestamps from the payload to sort events properly.
- Handle events individually, rather than relying on strict order.
Receiving Duplicate Events?
Receiving Duplicate Events?
- Webhooks are not guaranteed to be sent only once.
- Implement idempotency checks: Store received event IDs and ignore duplicates.
