Read Work order entry
const url = 'https://api.aerandil.com/v1/object-types/hospitality.work_order_entry/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.work_order_entry/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \ --header 'Authorization: Bearer <token>'Read an existing instance.
One line on a work order’s thread — hubOS’s fault logbook thread as typed data: a note, work (minutes spent), material (parts used), a delegation to another role, the postponement (written by postpone_work_order, with the date and reason) or the resolution (written by complete_work_order). Linked to its order (work_order_entry_for_work_order) and to the staff member who wrote it when one did (work_order_entry_recorded_by); recorded_by names the principal either way. Append-only: a correction is another line. Photos hang off an entry as attachments. The order’s time and parts are the sum of its entries — a query, not a stored total.
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
Parts used: description, quantity, optionally a unit, and the catalogued material and store a consumed part came from
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.work_order_entry", "properties": { "delegated_to_role": "front_office_agent", "kind": "note" }, "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).