Create a coordinated schedule of actions for a device. A schedule is a group of slots that materialise into push actions at fire time, with optional recurrence rules that top up a rolling materialisation horizon. Slot variants are mutually exclusive: at (absolute timestamp) or time (wall-clock plus a schedule-level IANA timezone). The route is published ahead of the implementation; every call returns 501 until the scheduler lands.
Documentation Index
Fetch the complete documentation index at: https://docs.amps.ai/llms.txt
Use this file to discover all available pages before exploring further.
A schedule body: deviceId, optional timezone (required for time-variant slots), optional recurrence, and a non-empty slots array. Slots carry the action template the platform materialises on each fire.
The body is of type string.
Schedule created.