List completed/cancelled schedules
Most recent first, capped at the last 50.
A session token for an existing account, obtained from POST /auth/login (see the Authentication endpoints) - not an API key. Endpoints marked with this scheme reject API key callers outright, regardless of what that key is granted. Outside the Authentication endpoints themselves, everything requiring this scheme manages dashboard resources (rules, grants, keys, device configuration, command catalogs) and mirrors what a human does in the Nexalware web app - it is not meant to be automated by a third-party integration the way the Device Control and Schedules endpoints are.
In: header
Path Parameters
Response Body
application/json
application/json
curl -X GET "https://example.com/api/v1/devices/dev_a1b2c3/schedules/history"[ { "scheduleId": "sched_a1b2c3", "deviceId": "dev_a1b2c3", "slot": 0, "onTs": 1732003600, "offTs": 1732032400, "label": "Morning", "enabled": true, "status": "COMPLETED", "onCommand": { "command": "ON" }, "offCommand": { "command": "OFF" } }]List a device's active schedules GET
Schedules that are PENDING (created, not due yet) or ACTIVE (currently running). For schedules that already finished or were cancelled, see GET .../schedules/history instead.
Update a schedule slot PUT
Only the fields provided are changed, everything else on the existing schedule stays as-is.