From a8a2f5805b5200d3e36aa952712a84cdfc45e998 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 6 Apr 2026 15:41:47 +0000 Subject: [PATCH] docs: clarify webhook attendee behavior for seated event types Generated-By: mintlify-agent --- webhooks.mdx | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/webhooks.mdx b/webhooks.mdx index 2bc7175..41713f8 100644 --- a/webhooks.mdx +++ b/webhooks.mdx @@ -342,4 +342,14 @@ where `{{type}}` represents the event type slug and `{{title}}` represents the t | name | String | Name of the attendee | | email | Email | Email of the attendee | | timeZone | String | Timezone of the attendee ("America/New\_York", "Asia/Kolkata", etc.) | -| language?.locale | String | Locale of the attendee ("en", "fr", etc.) | \ No newline at end of file +| language?.locale | String | Locale of the attendee ("en", "fr", etc.) | + +### Webhooks for seated event types + +When you use [seated event types](/event-types/offer-seats), multiple attendees can book the same time slot. In this case, webhook payloads include only the attendee whose booking triggered the event — not all attendees for that slot. This makes it easier to process individual bookings in your automation without needing to filter through other attendees. + +For cancellation events (`BOOKING_CANCELLED`), the payload includes all attendees for the time slot, since the cancellation may affect the entire booking. + + +This applies to all webhook triggers except `BOOKING_CANCELLED`. If your event type does not use seats, the `attendees` array behaves the same as before — it contains the booker and any guests. + \ No newline at end of file