Board sort
const url = 'https://api.aerandil.com/v1/functions/hospitality.function.board_sort/invoke';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"params":{"board":"housekeeping_sheet","boards":["housekeeping_sheet"]},"target":{"id":"2489E9AD-2EE2-8E00-8EC9-32D5F69181C0","object_type":"hospitality.property"}}'};
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/functions/hospitality.function.board_sort/invoke \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "params": { "board": "housekeeping_sheet", "boards": [ "housekeeping_sheet" ] }, "target": { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "object_type": "hospitality.property" } }'The order the caller reads one of the property’s boards in — hubOS’s server-defined sort pattern with its per-user override: the caller’s own preference for the board when their session is a staff member who set one (set_staff_sort_preference), else the house’s active pattern (set_board_sort_pattern), else the kernel’s default (the sheet: status, priority, task type, room; the rack: floor, room; work orders: severity, due date, room; pacing: credits still to clean, name). source says which (staff, property, kernel) and pattern_id names the house’s pattern. keys is ordered, first key first, each with its direction; every ranked key (priority — a work order’s severity — task_type, status) carries values, its whole vocabulary least first: the stated order, then the rest in the kernel’s rank. A row with no value for a key sorts after the rows with one, in either direction. The kernel names the order; the client applies it to its rows. Name one board and the answer carries its board, source, pattern_id and keys beside property_id; name several as boards and boards in the answer is a map from each board to that answer, so a handset reads every board its role shows in one call. Exactly one of the two. Read-only.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”object
object
object
Responses
Section titled “Responses”Function invoked. The body carries the typed return_value shaped by the function’s declared return_type.
Envelope returned by the Aerandil function engine. correlation_id is the per-invocation id for trace stitching; return_value is the typed value the function computed (shape declared by the function’s return_type).
object
Per-invocation correlation id; appears on log/trace records this function emitted.
object
object
object
object
object
object
object
object
object
object
object
Example
{ "return_value": { "board": "housekeeping_sheet", "boards": { "housekeeping_rack": { "board": "housekeeping_sheet", "keys": [ { "direction": "asc", "key": "priority" } ], "source": "staff" }, "housekeeping_sheet": { "board": "housekeeping_sheet", "keys": [ { "direction": "asc", "key": "priority" } ], "source": "staff" }, "pacing": { "board": "housekeeping_sheet", "keys": [ { "direction": "asc", "key": "priority" } ], "source": "staff" }, "work_orders": { "board": "housekeeping_sheet", "keys": [ { "direction": "asc", "key": "priority" } ], "source": "staff" } }, "keys": [ { "direction": "asc", "key": "priority" } ], "source": "staff" }}Headers
Section titled “Headers”Always no-store — function results are time-sensitive and never cacheable.
Function or target object not found.
Parameter validation or domain-rule violation.