Webhooks
Shipbubble sends a payload to notify your application each time there is a status change on any of your labels (orders).
The payload for each webhook event will include information about the related API response. Your provided endpoint should be set up to receive a HTTP POST request, and must always return a 200 HTTP response within 15 seconds of the request if not it would be marked as failed.
We’ll send a webhook every 5 minutes for the first 5 tries in the case of a failed webhook.
VERIFYING WEBHOOKS WITH SHIPBUBBLE SIGNATURE
To prevent your application from a replay attack, we recommend that you verify all webhook events by checking for our unique signature, x-ship-signature, in the request headers of our webhooks.
We hash each webhook message that we send to your URL using HMAC (Hash-based Message Authentication Code) with SHA512 algorithm and SECRET_KEY as a key of the hash
Events
Shipbubble provides various webhook events to notify you about changes in your shipment process.
Here are some of the event types we send, the list will be updated as we release more actions in the future.
Last updated