Shipment events
Freightview sends this request whenever a shipment event occurs, to the production or sandbox webhook URL configured on your account depending on which environment the shipment belongs to. The event property identifies which event was triggered, and data.shipment contains a full snapshot of the affected shipment in the same format as the shipment details endpoint.
Respond with any 2xx status code to acknowledge receipt. Any response with a status code of 400 or greater (or a network/timeout error) is treated as a failed delivery and retried.
Headers
A unique identifier for this delivery. The same value is sent on every retry of the delivery, so it can be used for idempotency.
Authenticates the request and protects against replays, formatted as t=<unix-seconds>,v1=<digest>. v1 is the hex-encoded HMAC-SHA256 of <t>.<raw request body> keyed with your signing secret. Verify the digest and reject timestamps outside your tolerance window before trusting the payload.
Payload
Example payload
{
"timestamp": "2026-07-15T12:34:56.789Z",
"deliveryId": "0f9c2c8e-9c1e-4c1a-8b3a-2b1d9f0e7a55",
"data": {
"message": "Webhook configuration verified"
}
}Response
Acknowledged. Return any 2xx status code to confirm receipt of the event.
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.