Skip to content

Declare a schedule's history

POST /irrigation/schedules/{scheduleId}/backfill
  • Scope irrigation:write
  • API key x-api-key
  • Base URL https://api.hub.akuasense.com/v1

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

  • scheduleId integer required

Headers

  • Idempotency-Key string

    Replays the same 2xx response (24 h)

Request body

  • from string date

    Default: the schedule’s startsOn. Raised to startsOn if earlier.

  • to string date

    Default: today.

Response

200

Summary of the declaration

  • scheduleId integer
  • modules integer

    Probes affected (a parcel schedule targets several).

  • occurrences integer

    Occurrences expanded over the period.

  • inserted integer

    Occurrences actually written. Lower than occurrences when some already existed: the move can be replayed without producing duplicates, and never rewrites what the customer has already declared.

  • horizonDay string date
  • fromDay string date

    Lower bound actually used — never before the schedule’s startsOn.

  • toDay string date
  • truncated boolean

    true = 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