Manage webhooks
A webhook subscription triggers an HTTP request to a URL of your choice every time a given Eveos event type occurs (new participant, check-in, paid order…).
Get there
Section titled “Get there”- From a session, return to the organizer level: select “Events” in the breadcrumb at the top of the page, or “Switch Event” at the bottom of the sidebar.
- In the organizer sidebar, open “Settings” → “Developer” → “Webhooks”.
Create a subscription
Section titled “Create a subscription”- Select “Create subscription”.
- Enter a “Name” (e.g. “Slack notifications”) and the “Destination URL”. The URL must be an absolute HTTPS address; private IP addresses are rejected.
- Select at least one “Event type”:
participant.created,participant.updated,participant.deleted,checkin.created,order.paid. - In “Projects”, leave empty to deliver events from every project, or choose specific projects.
- Choose the “Payload type” (see below) then confirm.
Payload types
Section titled “Payload types”Full envelope with the public v1 DTO — suited to general integrations.
A flattened snake_case envelope — suited to Zapier and no-code tools.
The request body is entirely defined by a template you write — useful for Slack, Teams, or an ERP.
In the payload designer, select an event type to load the catalog of
available variables (and a preview project to see custom fields), then
insert variables using the {{variable.key}} syntax in the editor. In
JSON, simply wrap the variable in quotes: value escaping is automatic.
The “Content-Type” and additional HTTP headers are configurable.
Use “Preview (local)” for an instant render with sample values, or “Preview (server)” for a server-side render — in both cases, no real HTTP delivery is made.
Security and signing
Section titled “Security and signing”Every subscription has a signing secret, visible in the edit form of an existing subscription.
Status and automatic disabling
Section titled “Status and automatic disabling”- Active: deliveries work normally.
- Unstable: recent failures were recorded, without deactivation.
- Automatically disabled: after 10 consecutive failures, a subscription is disabled (hover the badge to see why). Use “Reactivate” from the action menu to put it back in service; the consecutive-failure counter is then reset to zero.
Monitor deliveries
Section titled “Monitor deliveries”The “View deliveries” menu opens a panel listing a subscription’s deliveries, filterable by status (Pending, Retrying, Succeeded, Failed). For each delivery, review the number of attempts, the returned HTTP status, and, on failure, the error message. Open a delivery to see the payload sent.
Subscriptions created by an external integrator
Section titled “Subscriptions created by an external integrator”An “External” badge identifies subscriptions created by an integrator through the public API (for example from Zapier). You can still view, edit, or delete them from this page, but deleting an external subscription breaks the third-party integration — a warning is shown before you confirm.