Webhook Event Types
This page lists every event type that StandShare can send to a configured webhook endpoint. Use this reference when deciding which events to subscribe to and when understanding the data your integration will receive.
For an explanation of how webhooks work, see Understanding Webhooks. To configure a webhook endpoint, see Configure Webhooks.
Supported event types
| Event Type | Trigger | Data Included |
|---|---|---|
event.created | A new event is created | Event name, date, venue, and status |
event.updated | An event's details change | The updated fields |
event.cancelled | An event is soft-cancelled | Event name and cancellation timestamp |
event.settled | An event's settlement is committed | Event name and settlement summary |
attendance.checked_in | A worker checks in at an event | Worker name, event, and check-in timestamp |
attendance.checked_out | A worker checks out of an event | Worker name, event, and check-out timestamp |
roster.updated | An event's worker roster changes | Event name and a summary of the change |
Additional event types will be added in future releases. If you need a specific event type that is not listed here, use the feedback form to let us know.
Example payload
Every webhook delivery uses the same outer structure. The data field contains the details specific to the event type.
The following is an example payload for an event.created notification:
{
"id": "whk_01H...",
"type": "event.created",
"created_at": "2026-05-05T14:30:00Z",
"data": {
"event_id": "evt_01H...",
"name": "Friday Night Football - North Stadium",
"date": "2026-09-12",
"venue": "North Stadium",
"status": "upcoming"
}
}
Other event types follow the same structure — id, type, created_at, and data — with different fields inside data depending on what triggered the notification.
Payload shapes may change as new fields are added in future releases. Build your integration to ignore fields it does not recognize, rather than treating unknown fields as errors. This ensures your integration continues to work as the platform evolves.
Next Steps
- Understanding Webhooks — how delivery works, retry behavior, and security signatures
- Configure Webhooks — set up a webhook endpoint in your organization settings
- API Keys — scoped keys for tools that pull data from StandShare on demand