Read Round template
const url = 'https://api.aerandil.com/v1/object-types/hospitality.round_template/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.aerandil.com/v1/object-types/hospitality.round_template/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \ --header 'Authorization: Bearer <token>'Read an existing instance.
A house’s planned walk — hubOS’s revision structure: a name, a family (corrective, preventive, technical_legal, inspection_legal), the maintenance plan’s cadence (fixed to the calendar or floating from the last completion, every interval_days) and its next due date, and the checkpoints in order — each a room or a piece of equipment of this house (ref_id), or a general place named by its label, with the items checked there (check, reading with its unit and optional min / max, text, photo, and section headings). One active template per house and name: defining the name again revises it in place. The automation lane is its clock: a sweep over active templates whose due instant has come (next_due_at, the house’s midnight starting next_due_on) and that have no round open starts one (start_inspection_round); completing the round moves next_due_on on. open_round_id names the round in progress; revision counts the walks it has defined (a re-definition that moves the checkpoints is the next), and a start may name the one it saw.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Object id (UUID v7, server-generated at create time).
Query Parameters
Section titled “Query Parameters”Read through an open branch’s copy-on-first-write overlay view instead of the canonical (main) plane. Does not compose with as_of (422). The branch must exist under the caller’s tenant.
Responses
Section titled “Responses”Object found.
object
object
The checkpoints, in walking order, each with its items
object
object
Per-property source attribution and pins. An entry under properties means the property’s current value came from that source (on the source’s own clock, source_updated_at); an entry under pins is a human override protecting the property from sourced writes.
object
object
object
object
object
object
object
object
object
object
object
Example
{ "object_type": "hospitality.round_template", "properties": { "cadence": "fixed", "checkpoints": [ { "items": [ { "kind": "check" } ], "kind": "room" } ], "family": "corrective", "status": "active" }, "scope": { "level": "tenant" }}Headers
Section titled “Headers”Quoted strong validator (RFC 7232 §2.3) carrying the object’s monotonic version. Informational on the read path — object mutation goes through typed actions on /v1/actions/{action}/apply, not raw CRUD.
No object with that id (or soft-deleted).