Event attendance caps

Enabling a cap

• Use the Maximum Attendees field when creating or editing an event.
• Leave it blank for unlimited attendance.

How capacity works

• Only Yes RSVPs count toward the limit; Maybe/No do not.
• When full, standard users cannot submit a Yes RSVP.
• Admins can still force-accept guests above the cap.
• Need a hard cutoff instead of a cap? Use the “Close RSVPs” toggle or schedule an auto-close time.

EventFull response

HTTP 400
{
  "error": "EventFull",
  "message": "This event has reached its maximum number of attendees."
}

Force Accept & API usage

Bypass the cap with an event owner token (admin token) when you deliberately want to add someone above the limit.

• The event owner UI includes a Force Accept button next to each RSVP when a cap is set.
• API: add ?force_accept=true and send Authorization: Bearer <event-owner-token> (a.k.a. <admin_token>).
• Each override writes an owner-visible force_accept message for auditability.

POST /api/v1/events/{event_id}/rsvps?force_accept=true
Authorization: Bearer <event-owner-token>
{
  "name": "Guest Name",
  "attendance_status": "yes",
  "guest_count": 0,
  "is_private_rsvp": false
}