Feature

Reliable webhook delivery

Every status change fires an event. Automatic retries on failure. Full delivery log with per-attempt history. Connect Crated to any downstream system — warehouse, storefront, ERP, internal tooling.

Webhook delivery log listing all outbound events across all webhooks

Delivery log — full history of every outbound webhook event across all endpoints in the space

Event types

shipment.status_changed

shipment.status_changed fires on every status transition. The payload includes the shipment ID, new status, and any additional data attached to the shipment — so downstream systems have everything they need without a follow-up API call.

Reliable delivery

Failed deliveries are retried automatically. Each attempt records the HTTP status code, response time, and timestamp. If all retries exhaust, the event stays in the log — you can inspect it, understand why it failed, and replay if needed.

Configuration

Each webhook endpoint gets a URL, HTTP method (GET, POST, PUT, PATCH, or DELETE), optional API key sent as a request header, optional HMAC signature for request signing, and an active toggle to pause delivery without deleting the config.

Event detail — inspect payload, view delivery attempts with HTTP status, response time, and timestamp

Event detail

Every event in the delivery log links to a detail view showing: event type, target URL, HTTP method, timestamps, the triggering shipment (linked), the full JSON payload, and a list of every delivery attempt with HTTP status code, response time, and exact timestamp.

Delivery log

Space-scoped log of all outbound events across all webhooks. Shows event type, target URL, delivery status (Delivered / Failed / Pending), and time. Full visibility into what was sent, to where, and when.

Compliance & audit

Editing a webhook creates an archive entry. Every configuration change is traceable — what changed, when, and from what previous state. Webhook history is never deleted.