Capacity and waitlist
How seats are counted, what happens when an event is full, and how the waitlist moves.
Seats
capacity is a number of seats, or null for no limit. Each going RSVP takes 1 + guests seats, so Ada plus one friend takes two. max_guests caps the plus-ones per RSVP (0 to 100); asking for more answers 422 too_many_guests.
counts on every event shows where you stand:
{ "going": 30, "waitlisted": 3, "spots_left": 2 }The widget turns that into "30 going, 2 spots left".
When an RSVP does not fit
Seat checks happen inside the database with the event row locked, so two guests can never take the last seat at the same moment.
| The event | The RSVP gets |
|---|---|
Has room for 1 + guests | going |
Is full (or the party does not fit) and waitlist_enabled is true | waitlisted |
| Is full and has no waitlist | 409 capacity_reached |
How the waitlist moves
When seats free up (a cancellation, a deleted RSVP, or you raise or remove capacity), waitlisted guests are promoted in the order they joined. A party too big for the free seats is skipped, and the next one that fits moves up.
Each promoted guest:
- changes to
going, - gets an email saying they are in,
- triggers an
rsvp.promotedwebhook.
Promotion stops once an event is cancelled or has ended.
Over your plan's RSVP limit
Capacity is about seats at your event. Your plan's monthly RSVP count is separate, and it never turns a guest away. See locked RSVPs.