Developer docs

Webhooks

Use Eventzilla webhooks to send real-time registration, order, and attendee updates to your own systems without repeatedly polling the API.

What are webhooks?

A webhook is an HTTP callback. When a selected event happens in Eventzilla, Eventzilla sends an HTTP POST request to the endpoint URL you configure. Your application can then update a website, CRM, marketing platform, reporting system, or internal workflow automatically.

Common use cases

Add a buyer or attendee to your CRM when a registration is confirmed.
Trigger onboarding or reminder email campaigns after a registration update.
Update a website or internal dashboard when orders are created or cancelled.
Track attendee check-ins in real time during the event.

Delivery format

Eventzilla sends webhook notifications as HTTP POST requests.
The request body is JSON.
The payload includes the webhook event type and a data object with event, order, attendee, payment, and ticket details where applicable.

Supported triggers

Trigger	When it fires
`registration.confirmed`	When a registration is confirmed.
`registration.updated`	When a registration is updated.
`registration.pending`	When a registration is pending payment or approval.
`registration.abandoned`	When a registration process is abandoned before completion.
`registration.waitlisted`	When a registration is added to a waitlist.
`registration.invoice.paid`	When an invoice is marked as paid.
`registration.cancelled`	When a registration is cancelled.
`attendee.checkin`	When an attendee is checked in.

Payload structure

The exact fields vary by trigger. Most registration-related webhook payloads include an event identifier, order reference, buyer details, ticket/attendee details, payment status, amounts, and timestamps.

Field	Description
`id`	Unique webhook notification identifier.
`object`	Object family associated with the webhook. For event-related webhooks this is usually `Event`.
`type`	The trigger name, such as `registration.confirmed` or `attendee.checkin`.
`data`	Trigger-specific payload containing order, buyer, event, attendee, ticket, add-on, and session details.

Implementation note: Store the webhook id and relevant order or attendee identifiers so your receiver can safely handle retries or duplicate notifications.

Example payload

This example shows a typical registration.confirmed webhook for a paid order.

{
  "id": "wh_20260417103045",
  "object": "Event",
  "type": "registration.confirmed",
  "data": {
    "orderref": "20260417-10458",
    "order_date": "2026-04-17 10:30:45",
    "buyer_id": "214582001",
    "buyer_first_name": "Amelia",
    "buyer_last_name": "Hart",
    "buyer_email": "amelia.hart@example.com",
    "tickets_in_order": "2",
    "addons_in_order": "0",
    "sessions_in_order": "1",
    "order_amount": "298.00",
    "order_fees": "14.90",
    "discount_code": "",
    "discount_amount": "0.00",
    "tax_label": "GST",
    "tax_amount": "27.09",
    "payment_type": "Credit Card",
    "order_status": "Confirmed",
    "event_id": "2139000456",
    "event_title": "Brisbane SaaS Growth Summit 2026",
    "event_date": "2026-05-22 09:00:00",
    "tickets": [
      {
        "ticket_id": "214582100",
        "attendee_first_name": "Amelia",
        "attendee_last_name": "Hart",
        "attendee_email": "amelia.hart@example.com",
        "bar_code": "493560164138979471",
        "ticket_type": "Early bird admission",
        "ticket_amount": "149.00",
        "questions": []
      },
      {
        "ticket_id": "214582101",
        "attendee_first_name": "Noah",
        "attendee_last_name": "Reed",
        "attendee_email": "noah.reed@example.com",
        "bar_code": "493560164138979472",
        "ticket_type": "Early bird admission",
        "ticket_amount": "149.00",
        "questions": []
      }
    ],
    "addons": [],
    "sessions": [
      {
        "session_id": "2139044264",
        "session_name": "Founder growth workshop",
        "session_amount": "0.00"
      }
    ]
  }
}

Create a webhook subscription

Sign in to your Eventzilla account.
Go to Account Settings.
Open For Developers > Webhook Subscription.
Select Add Webhook.
Enter the HTTPS URL that should receive webhook requests.
Choose whether the webhook should apply to All Events or to one specific event.
Select one or more triggers and save the subscription.

Event scope

Scope	Behaviour
All Events	The webhook fires for every event under the organizer account.
Specific Event	The webhook fires only for the selected event.

Manage webhook subscriptions

Existing webhook subscriptions appear in the webhook list under your organizer account. Use the gear icon next to a webhook to manage it or remove it when it is no longer needed.

Tip: Your receiving endpoint should respond quickly with a successful HTTP status after it accepts the payload. Process longer-running work asynchronously in your own system.

Source content adapted from the Eventzilla support guide to webhooks. Last reviewed for this developer documentation build in 2026.