Retrieve an asset schedule
The plan in force for an asset over Berlin delivery dates, the same for partner and Nomos tokens: for every planned quarter hour one slot, with its author. While Nomos optimises the household, Nomos’s newest slot is in force, and the partner’s where Nomos planned nothing. Otherwise the partner’s newest slot is in force.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
"ha_b7q2m1k8v4n0x3c9l5p2r7td"
Query Parameters
First delivery date, inclusive, in Europe/Berlin (YYYY-MM-DD).
^\d{4}-\d{2}-\d{2}$"2026-09-08"
Last delivery date, inclusive, in Europe/Berlin (YYYY-MM-DD). May equal start.
^\d{4}-\d{2}-\d{2}$"2026-09-08"
Response
The plan in force
asset_schedule "ha_b7q2m1k8v4n0x3c9l5p2r7td"
15min Sorted by time. On a POST, the stored slots. On a GET, the plan in force: one slot per planned quarter hour. A quarter hour without one runs the device's own logic.