Slots

Cancel one Occurrence of a repeating schedule

Cancel one Occurrence, softly: the row and everyone registered on it stay, and they are told (note is a private note for organizers, never shown to participants; message is added to the email and text participants receive. notified says how many). The Occurrence becomes detached. Cancelling an already-cancelled Occurrence is a no-op that notifies nobody and keeps the first cancelledAt. Undo it with POST /signups/{id}/slots/{slotId}/reconnect. The slot must belong to a Series: a one-off slot is 400 bad_request (delete it with DELETE /signups/{id}/slots/{slotId}). The account behind the credential must have a verified email, or the call is 403 forbidden.

post/signups/{id}/slots/{slotId}/cancel

Request

  • Base URL: https://thesignup.app/api/v1
  • URL: https://thesignup.app/api/v1/signups/{id}/slots/{slotId}/cancel
  • Auth: HTTP bearer

Path parameters

idstring uuid required
slotIdstring uuid required

Request body

notestring nullable

A private note for organizers, kept on the Occurrence and never shown to participants.

messagestring nullable

Added to the email and text participants receive about this change.

Response

The cancelled Occurrence and who was told

Changes

No recorded changes to this operation across all 1 revision of this API.