Event structure
Events follow anobject.action naming convention. The data field contains a summary of the resource at the time of the event.
Destinations
Events are delivered to destinations you configure. Deck supports webhooks and native cloud infrastructure out of the box.
Create a destination in the Console or via the API and subscribe to the events you care about:
"events": ["*"] to subscribe to everything.
Deliveries and retries
Each event is delivered independently to every subscribed destination. For webhooks, return a2xx within 5 seconds to acknowledge. For cloud destinations, delivery is handled natively.
Failed deliveries retry up to 10 times with exponential backoff (base 2, starting at 30 seconds). Track delivery status via GET /v2/event-destinations/{id}/event-deliveries.
Retention
Events are stored for 30 days.Events reference
Full list of event types by resource.
Destinations & deliveries
Configure destinations, verify webhook signatures, and track delivery status.
Webhook best practices
Build reliable, idempotent event consumers.
API reference
Events, destinations, and deliveries endpoints.