Days

Add a day to a signup

Add a date to the signup. A date the signup already has answers 200 with that day and created: false, seeding nothing; a new one is 201. On a repeating schedule a new date inside the schedule's range gets the schedule's Shifts (seededShifts), and one outside it is created with none and unseededReason: "out-of-range". Items every other date carries are copied onto a new date (seededItems). Notifies nobody. A date that is not a real calendar date is 422.

post/signups/{id}/days

Request

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

Path parameters

idstring uuid required

Request body

datestring required

The date to add, YYYY-MM-DD, in the signup's timezone.

Response

The date was already there; the existing day, nothing seeded

createdboolean required

False when the date was already there and the existing day came back.

seededShiftsinteger required

Shifts the repeating schedule's plan put on a newly created date. 0 on a reused date.

seededItemsinteger required

Items every other date already carries, copied onto a newly created date. 0 on a reused date.

unseededReason'out-of-range' | 'empty-rule' | 'null' nullable required

Why a new date on a repeating schedule got no Shifts: out-of-range (outside the schedule's range — extending the schedule will not fill it; add Shifts with POST /signups/{id}/slot_series/{seriesId}/occurrences after extending) or empty-rule. Null otherwise.

Changes

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