Create work order
const url = 'https://api.aerandil.com/v1/actions/hospitality.action.create_work_order/apply';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"branch":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","params":{"allow_duplicate":true,"asset_id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","category":"hvac","description":"example","element":"light","fault_type_id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","from_triage_id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","out_of_order_end":"2026-04-15","out_of_order_start":"2026-04-15","return_status":"dirty","severity":"cosmetic","staff_member_id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","stay_id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","title":"example"},"return_modified":false,"target":{"id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","object_type":"hospitality.room"}}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.aerandil.com/v1/actions/hospitality.action.create_work_order/apply \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "branch": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "params": { "allow_duplicate": true, "asset_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "category": "hvac", "description": "example", "element": "light", "fault_type_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "from_triage_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "out_of_order_end": "2026-04-15", "out_of_order_start": "2026-04-15", "return_status": "dirty", "severity": "cosmetic", "staff_member_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "stay_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "title": "example" }, "return_modified": false, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.room" } }'Open a maintenance work order against a room, optionally assigning an engineer on the spot. When the room is physically unusable, declare the out-of-order window here (out_of_order_start / out_of_order_end / return_status): the order then holds a real room_status_block minted through the same path as take_room_out_of_order — ledger weight, in-house-guest refusal, conflicting-assignment work list and all — and complete_work_order releases it. Never a severity-driven side effect: downtime is always an explicit declaration. Faults by element (2026-10-15): element names the thing in the room that failed (the attendant’s word); fault_type_id names an entry of the house’s or its brand’s catalogue and fills title, category, severity and element wherever the call states none; with no category from either, the element’s trade is the category; with no title, the element’s name is the title. An order already open on the room under the same title (case and spacing aside) or the same fault type is that order — the double fault hubOS lists before a new one is raised: nothing is minted, the response carries a work-order-open-twin warning naming it, and work_order.reported_again records the second report. Two orders naming different assets are not twins; allow_duplicate raises another anyway. What the call declares beyond the report lands on the twin (2026-10-17): a declared out-of-order window blocks the room through it when it holds no block (one it holds that already covers the window is said, any other is refused naming it — an order holds one block), and a staff_member_id takes it when nobody holds it (a holder it has keeps it — assign_work_order re-points); the warning says which, and work_order.reported_again carries block_id and assignee_id. A fault in a public area is create_public_area_work_order.
Effects: create hospitality.work_order; link hospitality.link.work_order_from_triage; link hospitality.link.work_order_for_room; link hospitality.link.work_order_assigned_to; create hospitality.room_status_block; link hospitality.link.room_status_block_for_room; link hospitality.link.work_order_holds_block; modify hospitality.availability_day; link hospitality.link.work_order_for_asset; link hospitality.link.work_order_reported_by_stay; link hospitality.link.work_order_of_fault_type; link hospitality.link.work_order_for_area; modify hospitality.work_order.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”object
Apply against an open branch’s overlay view instead of the canonical (main) plane. The action’s writes land in the branch’s copy-on-first-write overlay, its events in the branch’s own stream, and the invocation is journaled for merge-by-replay. Branch writes are action-only, so this is the write-side entry point to a branch (POST /v1/branches forks one).
object
When true, the response carries modified_objects and modified_links projections — the engine reads the event log inside the same transaction so the projection observes the handler’s own writes.
object
Responses
Section titled “Responses”Action applied. modified_objects and modified_links populated when return_modified: true was supplied.
Envelope returned by the Aerandil action engine. correlation_id ties every event emitted by this invocation; modified_objects and modified_links project the events the handler emitted (per the action’s declared effects); warnings carries any non-blocking soft-validator observations.
object
Per-invocation correlation id; matches events.correlation_id for every event this action appended.
Links established or removed by this invocation. Empty when the caller did not request return_modified.
object
Objects created, modified, or soft-deleted by this invocation. Empty when the caller did not request return_modified.
object
Non-blocking soft-validator observations emitted during this invocation (e.g. comp-authority over-limit, recipe pour-cost over sell-price). Absent when no warnings were emitted.
object
Human-readable summary, suitable for logging or operator-UI surfacing.
Object type the warning was raised against.
Property the warning anchors to, when a single field is the locus. Absent for multi-field rules.
Stable kebab-case rule identifier (e.g. comp-authority-over-limit).
Example
{ "modified_links": [ { "kind": "linked", "link_type": "hospitality.link.work_order_from_triage" } ], "modified_objects": [ { "kind": "created", "object_type": "hospitality.work_order" } ]}Conflict — concurrent modification or unique constraint violation.
Validation error — parameter validation or business-rule violation.