Webhooks, virtuele tickets en terugkerende evenementen

Overview

Webhooks let CompleteEvent send real-time HTTP notifications to your own systems whenever something happens — a registration is confirmed, an attendee checks in, or an auction payment lands. Use webhooks to sync data with your CRM, trigger Zapier automations, update a spreadsheet, or post to Slack.

Webhook endpoints are configured at the organization level in Organization Settings → Webhooks.

Supported Event Types

• registration.confirmed — fires when a registration is confirmed (free or after Stripe payment).
• registration.cancelled — fires when an organizer cancels a registration.
• checkin.completed — fires when an attendee is checked in via QR scan or manual check-in.
• auction.item.paid — fires when a silent auction winner completes payment.

Adding an Endpoint

1. Go to Organization Settings → Webhooks.
2. Enter your endpoint URL (must be HTTPS). Select which event types it should receive.
3. Click Add endpoint. CompleteEvent displays a signing secret — copy this now, it is only shown once.
4. Use the Send test button to send a ping event and confirm your server is reachable.

Request Format

Every webhook request is an HTTP POST with these headers:

• Content-Type: application/json
• X-CompleteEvent-Event — the event type (e.g. registration.confirmed)
• X-CompleteEvent-Signature — HMAC-SHA256 of the request body, signed with your endpoint secret

The body looks like this:

{
  "event": "registration.confirmed",
  "timestamp": "2026-04-15T14:32:00Z",
  "data": {
    "registrationId": "...",
    "eventId": "...",
    "email": "attendee@example.com",
    "firstName": "Alex",
    "lastName": "Smith"
  }
}

Verifying Signatures

Validate every incoming request by computing HMAC-SHA256(secret, requestBody) and comparing it to the X-CompleteEvent-Signature header. Reject requests where the signatures do not match.

Delivery and Retries

Webhooks are delivered once. If your endpoint returns a non-2xx status, the delivery is logged as failed. Check the delivery log on the Webhooks settings page to see recent attempts and response codes.

Virtual Ticket Tiers

Ticket tiers can be marked as virtual by adding a join URL when creating or editing the tier. Attendees who register on a virtual tier receive their join link in their confirmation email and can access it at any time from their event guide page.

Use virtual tiers to offer a lower-cost remote attendance option alongside your in-person tiers, or to run a fully virtual event without separate infrastructure.

Recurring Events

The Duplicate event button in the event dashboard creates a copy of your event with all ticket tiers and settings pre-filled. Set a new start date and optionally check Create as recurring instance to link the copy back to the original — useful for monthly or quarterly event series.

Duplicated events start in draft status so you can review and adjust before publishing.