Declare a schedule's history
/irrigation/schedules/{scheduleId}/backfill Expands the schedule’s PAST occurrences and marks them done and verified. An EXPLICIT move: creating a schedule never goes back in time on its own. Capped at 3 years, and never before startsOn.
Path parameters
-
scheduleIdinteger required
Headers
-
Idempotency-KeystringReplays the same 2xx response (24 h)
Request body
-
fromstring dateDefault: the schedule’s
startsOn. Raised tostartsOnif earlier. -
tostring dateDefault: today.
Response
Summary of the declaration
-
scheduleIdinteger -
modulesintegerProbes affected (a parcel schedule targets several).
-
occurrencesintegerOccurrences expanded over the period.
-
insertedintegerOccurrences actually written. Lower than
occurrenceswhen some already existed: the move can be replayed without producing duplicates, and never rewrites what the customer has already declared. -
horizonDaystring date -
fromDaystring dateLower bound actually used — never before the schedule’s
startsOn. -
toDaystring date -
truncatedbooleantrue = the requested period was brought back to the 3-year cap.
Errors
- 400
Invalid body
- 401
Not authenticated
- 403
Insufficient scope/role, or outside your company
- 404
Schedule not found
SCHEDULE_NOT_FOUND