Set up workspace webhooks, verify signed messages and turn off delivery for individual events.
A webhook sends a message from Badgy to another app, for example when a guest checks in. Messages can include guests’ names and email addresses, so only send them to apps you trust.
New webhooks are on by default for every event linked to your workspace.
Add a webhook
Section titled “Add a webhook”Only workspace admins can add webhooks.
- In the workspace dashboard, open Integrations, then Manage webhooks and Add webhook.
- Paste the receiving app’s public
https://address into Endpoint URL. Under Triggers, choose when Badgy should send a message, then select Add webhook. - Choose Copy secret and add the signing secret to the receiving app.
Test a trigger and check that the other app got the message. Badgy doesn’t retry failed deliveries.
Webhook signing
Section titled “Webhook signing”Badgy signs every webhook message. The receiving app uses the signing secret to check that the message came from Badgy and wasn’t changed. Treat the secret like a password.
For developers: Use a Standard Webhooks verifier with the signing secret, the original request body (before parsing), and the webhook-id, webhook-timestamp, and webhook-signature headers. Reject missing or invalid signatures and timestamps more than five minutes from the current time.
Webhook payload
Section titled “Webhook payload”The payload is the data Badgy sends to your app. It arrives as JSON in the body of a POST request. Read trigger to find out what happened and event to see which event it happened at.
Example check-in
Section titled “Example check-in”{ "trigger": "check-in", "id": 42158, "identifier": "it_12345", "ticketType": "General Admission", "firstName": "Alex", "lastName": "Morgan", "email": "alex@example.com", "status": "CHECKED_IN", "checkedInAt": "2026-11-20T09:30:00.000Z", "event": { "orgSlug": "example-events", "slug": "autumn-meetup", "name": "Autumn Meetup", "provider": "TICKET_TAILOR", "providerEventId": "ev_12345" }}Fields
Section titled “Fields”Optional fields may be left out. All values are strings except id (a number) and event (an object).
| Field | What it means |
|---|---|
trigger |
What caused Badgy to send the message. |
id, identifier |
The ticket’s numeric ID and text identifier. Neither is the webhook-id header, which identifies the message. |
firstName, lastName, email |
The guest’s name and email address. |
company, phone, role |
Extra guest details, when available. Optional. |
ticketType |
The ticket type on the guest’s record. Optional. |
status |
The ticket’s status. |
checkedInAt |
When the guest checked in. Check-in messages use an ISO 8601 UTC timestamp. Optional for other messages. |
event.orgSlug, event.slug |
The parts of the Badgy event URL that identify the organiser and the event. |
event.name |
The event name in Badgy. Optional. |
event.provider |
The ticketing provider code, such as TICKET_TAILOR or LUMA. |
event.providerEventId |
The event ID in the ticketing provider, when available. Optional. |
Turn off a webhook for one event
Section titled “Turn off a webhook for one event”Open the event’s Settings, select Webhooks, and switch it off. Other events aren’t affected.
Edit or remove a webhook
Section titled “Edit or remove a webhook”In Manage webhooks, use Edit to change the address or triggers. Delete removes the webhook from all events in the workspace. If you use Rotate secret, update the receiving app right away.