Move or re-time one Occurrence of a repeating schedule
Re-time one Occurrence: start / end (HH:MM in the signup's timezone) are required even when unchanged, date (YYYY-MM-DD) moves it to another day, location gives it a place when it moves to another day, and note is a private note for organizers, never shown to participants; message is added to the email and text participants receive. The Occurrence keeps its seriesDate and shiftIndex — they are its key — and becomes detached, so later Series edits leave it alone. Its registrations and Day Attendance move with it. Participants are notified; notified says how many. The slot must belong to a Series: a one-off slot is 400 bad_request (edit it with PATCH /signups/{id}/slots/{slotId}). The account behind the credential must have a verified email, or the call is 403 forbidden. Sending date at all (even the day it is already on) is behind a pre-GA rollout for the person an OAuth token acts as (403 forbidden when they are outside it); an API key is not checked.
Request
- Base URL: https://thesignup.app/api/v1
- URL: https://thesignup.app/api/v1/signups/{id}/slots/{slotId}/move
- Auth: HTTP bearer
Path parameters
Request body
Response
The moved Occurrence and who was told
Changes
No recorded changes to this operation across all 1 revision of this API.