WAREHOUSE_SCHEDULE

Update Series

Changed on

Edit a recurring series' template ("this and following events").

from_schedule_id scopes the edit: that occurrence and every later one change, everything before it is left as it is. Omitting it scopes the edit from the current instant instead.

Time/config-only edits update the in-scope approved occurrences in place on their own dates. Sending days_of_week and/or end_date reschedules the series: the in-scope approved occurrences are replaced with a set materialized from the new cadence (user-deleted occurrences stay deleted). timezone is immutable. Occurrences whose window conflicts are skipped and reported in skipped.

patch/warehouse/schedules/series/{series_id}

Request

  • Base URL: https://api.myaltimate.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.myaltimate.com/warehouse/schedules/series/{series_id}
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Path parameters

series_idinteger required

Headers

x-tenantstring required

Request body

schedule_type'manual' | 'block' required

One of: manual, block

start_time_localstring required

Local wall-clock "HH:MM"

duration_minutesinteger required
days_of_weekstring[] nullable

New weekday cadence; omit to keep the current days.

end_datestring date nullable

New end date (at most 90 days from today); omit to keep the current end date.

from_schedule_idinteger nullable

The occurrence the edit was launched from. The edit applies to it and every later occurrence; earlier ones keep the schedule they already have. Omit to apply from now.

Response

Successful Response

series_idinteger required
warehouse_namestring required
instance_idstring nullable
schedule_type'manual' | 'block' required
days_of_weekstring[] required
start_time_localstring required
duration_minutesinteger required
timezonestring required
end_datestring date nullable
status'active' | 'cancelled' required

Lifecycle of a recurring warehouse-schedule series.

A series that would materialize zero occurrences is never persisted (creation fails with 400), so there is no rejected state here.

created_byinteger required
created_atstring date-time nullable
updated_atstring date-time nullable

Changes

  • a1870d258a3aRevision changes
    • info

      added the new optional request property //

    • info

      added the optional property / to the response with the status

    • info

      added the optional property /// to the response with the status

  • 6aa0788aa5dcRevision changes
    • info

      added the new optional request property

    • info

      added the new optional request property

    • info

      added the new optional request property

    • info

      added the optional property // to the response with the status