Subscribe to the events your integration uses. The event catalog includes currently emitted events and reserved names. A name being accepted in configuration is not evidence that production emits it.
Events emitted by the service
| Event | When it is emitted | Integration consideration |
|---|---|---|
waiver.signed |
A waiver is signed through the web, kiosk, API, event or prefill flow | Its PDF may still be pending |
waiver.flagged |
A signed record has flags | Payloads include flag labels, not the participant's answers |
waiver.voided |
A waiver is voided | Update downstream status without treating the event as deletion |
waiver.expired |
The expiry sweep detects an eligible expired record | The sweep runs approximately every 15 minutes; it is not an exact expiry-time alarm |
checkin.created |
A new arrival is recorded | Repeat arrivals are separate events |
The expiry event is emitted once for a qualifying record. Voided waivers do not produce this expiry event. Build local time-sensitive decisions around the actual record state, not an assumption that the webhook arrives at the exact expiry instant.
Reserved names and test pings
invitee.bounced and import.completed are reserved and are not currently emitted. Do not build a workflow that depends on either event being delivered.
ping is produced by the endpoint test operation. It is not a normal subscribable business event. Use it to check receiver plumbing and verification, not to infer that a guest action occurred.
Read the envelope
The envelope contains id, event, createdAt, organizationId and data. Business payloads use identifiers, timestamps and non-personal summaries. They do not carry the full participant answers.
Fetch details only when the worker needs them and use the correct organization's key. The state retrieved later can be newer than the historical event, especially after a delayed delivery or manual replay.
Avoid ordering assumptions
Two events about a related workflow may arrive out of order. Make updates based on stable identifiers and the state your application needs. Use delivery deduplication for retries and consult the live event catalog endpoint when inspecting available event definitions.