Skip to content
aerandil.com
GitHub

Traverse from Work order

POST
/v1/object-types/hospitality.work_order/objects/{id}/traverse
curl --request POST \
  --url https://api.aerandil.com/v1/object-types/hospitality.work_order/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/traverse \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "as_of": "2026-04-15T12:00:00Z", "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "cursor": "example", "direction": "out", "limit": 1, "link_type": "hospitality.link.pattern_clusters_work_order", "role": "example" }'

RPC-shaped traversal. Pick the edge by (link_type, direction) or by role — the registry resolves a role name (e.g. managed_by, direct_reports) to the underlying link side. link_type wins when both are present.

A maintenance request, typically against a room or venue. Tracks severity (cosmetic through to safety) through an explicit lifecycle: assign, schedule, start, complete (with a resolution), void (with a reason). Whether the room is out of order while the order is open is never a flag here — it is a real room_status_block held via work_order_holds_block, minted through the same code path as take_room_out_of_order and released on completion. The order is a thread (2026-10-13): its work_order_entry lines log notes, time, parts, hand-offs, the postponement and the resolution; it may name the equipment it is for (work_order_for_asset, its id carried as asset_id) and the guest stay that reported it (work_order_reported_by_stay), and postpone_work_order defers it to a named date (resume_work_order brings it back when the date comes). A hand-off on the thread stamps delegated_to_role until the order closes. Since 2026-10-15 a fault is for a room (work_order_for_room) or a public area (work_order_for_area, create_public_area_work_order), never both; it may name the room element it is in and the fault_type it was raised from; and it carries its holder’s id (assignee_id, or a worker group’s group_id) beside the edge every assigning verb moves.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
id
required
string format: uuid

Object id (UUID v7, server-generated at create time).

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json

Body for POST .../traverse. At least one of link_type or role MUST be supplied — the server returns 422 missing_traversal_target when both are absent. link_type wins when both are set.

object
as_of

RFC3339 temporal window: return neighbours whose edge was in effect at this instant ([effective_from, effective_to)) instead of now.

string format: date-time
branch

Traverse through an open branch’s overlay view instead of the canonical (main) plane. Does not compose with as_of (422).

string format: uuid
cursor
string
direction

Edge direction. Optional when the binding is asymmetric.

Allowed values: out in
limit
integer
>= 1 <= 500
link_type

API name of the link type to traverse. Narrowed to link types that bind the source. Wins over role.

Allowed values: hospitality.link.pattern_clusters_work_order hospitality.link.pattern_remediation_chained_action_target hospitality.link.stock_movement_for_work_order hospitality.link.stored_object_for_work_order hospitality.link.work_order_answers_feedback hospitality.link.work_order_assigned_to hospitality.link.work_order_assigned_to_group hospitality.link.work_order_entry_for_work_order hospitality.link.work_order_for_area hospitality.link.work_order_for_asset hospitality.link.work_order_for_room hospitality.link.work_order_from_checkpoint hospitality.link.work_order_from_maintenance_plan hospitality.link.work_order_from_round hospitality.link.work_order_from_triage hospitality.link.work_order_holds_block hospitality.link.work_order_of_fault_type hospitality.link.work_order_reported_by_stay
role

Link-side role name (e.g. managed_by, direct_reports). Mutually substitutable with link_type — the registry resolves the role to its underlying link and direction.

string

Responses

Section titled “Responses”

200

Section titled “200”

Neighbours along the resolved link.

Media typeapplication/json
object
data
required
Array<object>
object
created_at
required
string format: date-time
id
required
string format: uuid
object_type
required
string
properties
required
object
scope
required
One of: discriminator: level
object
level
required
string
Allowed value: tenant
Allowed values: tenant
tenant_id
required
string format: uuid
updated_at
required
string format: date-time
version
required
integer
>= 1
direction
required
Allowed values: out in
has_more
required
boolean
link_type
required
string
next_cursor
string
Example
{
  "data": [
    {
      "scope": {
        "level": "tenant"
      }
    }
  ],
  "direction": "out"
}

404

Section titled “404”

No object with that id, or link type unknown.

422

Section titled “422”

Validation error — must supply link_type or role.