Set up outbound webhooks

Outbound webhooks send signed JSON to your own HTTPS endpoint when registrations, check-ins, refunds, and waitlist activity happen. You configure endpoints under Settings → Integrations → Webhooks, and they are available on the Growth plan and above.

Before you start

You need an Owner or Admin role on the team, because only owners and admins can create, edit, disable, enable, rotate, or remove webhook endpoints. You also need a public HTTPS URL that your server can receive requests at — plain HTTP URLs and private, loopback, or link-local hosts are rejected at save time.

Webhooks are included on the Growth plan (1 endpoint) and Pro plan (10 endpoints). On the Free and Essentials plans, the Webhooks form stays locked until you upgrade.

Add an endpoint

1. Go to Settings → Integrations.

2. Open the Webhooks card and click Add endpoint.

3. Enter your endpoint URL in the Endpoint URL field. It must be a public HTTPS URL.

4. Optionally enter a Label (up to 100 characters) to identify the endpoint, such as your CRM's name.

5. Under Events to deliver, select at least one event. New endpoints select all 11 event types by default; clear any you don't want.

6. Click Save changes.

After you save, Eventually shows your signing secret once, with a Copy button. Copy it immediately — it is not shown again in the normal endpoint view. The only way to see a new secret is to rotate it.

Send a test event

Use Send test event to confirm an endpoint accepts deliveries before you rely on it. It sends a signed ping event through the same delivery path as live events and shows the receiver's HTTP response.

Test events are limited to 5 per minute per client IP. If you hit the limit, wait a minute and try again.

Edit an endpoint

To change an endpoint's URL, label, or event selection, click Edit on the endpoint, make your changes, and click Save changes. Editing an endpoint does not change its signing secret.

Rotate the signing secret

Rotate the secret when you suspect it was exposed or you lost the original. Click Rotate secret on the endpoint. The new secret is shown once — copy it immediately. After rotation, deliveries are signed with the new secret, so update your receiver to match.

Disable and enable an endpoint

Click Disable to stop deliveries to an endpoint without deleting its configuration. Disabled endpoints stop receiving events until you click Enable to turn them back on.

Recent deliveries

Each endpoint keeps a 30-day delivery log, visible under Recent deliveries on the endpoint in Settings → Integrations. The panel shows the last 25 rows, newest first.

Each row shows the event type, the outcome (delivered or the last HTTP status), the attempt count, the timestamp, and the first 255 characters of the failing response body. Retries update the row in place rather than adding new rows.

Redeliver an event

Use Redeliver on a logged event to re-send it through the normal delivery pipeline. Only Owners and Admins can redeliver, and the endpoint must be enabled. Redelivery reuses the same X-Eventually-Delivery-Id and follows the same retry and automatic-disable rules as a live delivery.

Remove an endpoint

Click Remove to delete an endpoint and stop all deliveries to it. There is no confirmation that restores a removed endpoint, so only remove one you no longer need.

Plan caps and over-limit endpoints

Your plan caps how many endpoints you can configure: 1 on Growth and 10 on Pro. The Webhooks card shows how many endpoints you've used out of your cap.

If you downgrade to a plan with a lower cap, your existing endpoints stay configured but deliveries to the endpoints over the new cap are paused until you upgrade or remove endpoints. You can re-enable delivery by removing other endpoints or upgrading your plan.

When an endpoint fails to respond, Eventually retries and then automatically disables it after repeated failures. See Troubleshoot outbound webhooks for what to do.