Skip to Content

RSVPs and statuses

What an RSVP is, the four statuses, where RSVPs come from, and how guests change their own.

An RSVP is one guest's answer to one event: a name, an email, how many extra guests they bring, answers to your questions, and a status. Guests never create an account.

Statuses

statusMeaningTakes seats
goingComing.Yes, 1 + guests
waitlistedThe event was full; they are in line for a spot.No
not_goingAnswered no. Useful for invitations.No
cancelledWas going or waitlisted, then cancelled.No

You can create an RSVP as going (the default) or not_going. waitlisted is decided for you when the event is full. Set cancelled with PATCH to cancel; the seat is freed and the waitlist moves up.

One RSVP per email per event

A second RSVP with the same email for the same event is refused with 409 already_registered. Through the widget, the guest gets their manage link emailed again instead, so they can change the first one. Nobody can edit someone else's RSVP by knowing their email.

If the earlier RSVP was cancelled or not_going, a new RSVP reuses it (same ID) and switches it back on.

Sources

source records where an RSVP came from: embed (the widget), page (a hosted event page), api or dashboard. You never set it on the secret-key API; it is always api there. The public RSVP endpoint takes source: "embed" (the default) or "page", and the widget sends page when its source attribute says so. Guests can only RSVP through embed and page while an event is published and has not ended; your API key and the dashboard can still add guests to draft, private or past events.

Guests change their own RSVP

Every RSVP made through the widget or a hosted page gets a manage link, emailed to the guest and shown after they RSVP. It opens a page where they can change their plus-ones and answers, or cancel. Under the hood that is the public GET and PATCH /v1/public/rsvps/{manage_token}.

Check-in

POST /v1/rsvps/{id}/check-in marks a guest as arrived and sets checked_in_at. Checking in twice keeps the first time. Only a going RSVP can be checked in: a cancelled, not going or waitlisted one answers 409 rsvp_not_going. In the dashboard's door list, a check-in can be undone whatever the guest's status.

Delete or cancel

  • PATCH /v1/rsvps/{id} with { "status": "cancelled" } keeps a record and frees the seat.
  • DELETE /v1/rsvps/{id} removes the RSVP and its guest data for good.

To remove a person from every event at once, see data rights.

On this page