Read Board sort pattern
const url = 'https://api.aerandil.com/v1/object-types/hospitality.board_sort_pattern/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.board_sort_pattern/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \ --header 'Authorization: Bearer <token>'Read an existing instance.
The order a property sets for one of its boards (hubOS’s server-defined sort pattern): the attendant’s housekeeping sheet, the supervisor’s rack, the engineer’s work-order board, or the pacing report. keys is an ordered list — the first key decides, the next breaks its ties — each with a direction and, for a ranked key (priority, task type, status), the house’s order of its values (departures before stayovers, say). One per board per house, authored by set_board_sort_pattern (a repeated board replaces it in place) and retired by retire_board_sort_pattern, which gives the board back to the kernel’s default. A staff member’s own preference (staff_member.sort_preferences) wins over it; hospitality.function.board_sort reads the order a caller sees.
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 keys the board is ordered by, first key first — each a key valid for the board, a direction, and for a ranked key optionally the order of its values
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.board_sort_pattern", "properties": { "board": "housekeeping_sheet", "keys": [ { "direction": "asc", "key": "priority" } ], "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).