Outbound webhooks overview
Outbound webhooks send signed, real-time JSON to your own server when registrations, check-ins, refunds, and waitlist activity happen on your events, and when your events are published, updated, rescheduled, cancelled, finished, or sell out. They let you push event data into your CRM, analytics, or any system that accepts an HTTPS request, without a dedicated integration.
Webhooks are available on the Growth plan and above. Growth includes 1 endpoint, and Pro includes 10. Configure endpoints under Settings → Integrations → Webhooks.
How webhooks work
You register one or more HTTPS endpoints and choose which event types each endpoint receives. When one of those events happens, Eventually sends a signed JSON HTTP POST to your endpoint. Each delivery includes an HMAC signature you verify using the endpoint's signing secret and a stable delivery ID you use to avoid processing the same event twice.
If an endpoint fails to respond, Eventually retries the delivery and automatically disables the endpoint after repeated failures. You can send a test event to confirm an endpoint works before relying on it.
Every endpoint keeps a 30-day delivery log under Recent deliveries, so you can see each delivery's state, the HTTP status your server returned, and an excerpt of its response. You can redeliver any logged event from there.
The six event lifecycle types (event.published, event.updated, event.rescheduled, event.cancelled, event.completed, and event.sold_out) are opt-in per endpoint like every other type. New endpoints select all 19 types by default. An endpoint you created before the lifecycle types existed is not subscribed to them automatically, so add them to its event list to start receiving them.
In this collection
Set up outbound webhooks: Add, edit, test, enable, disable, rotate, and remove webhook endpoints.
Webhook events and payloads: The 19 event types, including event lifecycle notifications, the JSON envelope, and how registrations, waitlist entries, and events appear in the data.
Verify Eventually webhook signatures: Confirm a delivery came from Eventually using the HMAC signature, and reject one whose timestamp is too old.
Troubleshoot outbound webhooks: Fix rejected URLs, failed and skipped deliveries, and automatically disabled endpoints.
Start with Set up outbound webhooks to register your first endpoint.