List links of Round template

GET

/v1/object-types/hospitality.round_template/objects/{id}/links/{link_type}

const url = 'https://api.aerandil.com/v1/object-types/hospitality.round_template/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/links/hospitality.link.inspection_round_from_template?direction=out';
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.round_template/objects/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/links/hospitality.link.inspection_round_from_template?direction=out' \
  --header 'Authorization: Bearer <token>'

List the neighbours of an instance along a typed link. Direction is inferred when the source binds the link on exactly one side; symmetric links (same object type on both ends) require an explicit ?direction=out or ?direction=in.

A house’s planned walk — hubOS’s revision structure: a name, a family (corrective, preventive, technical_legal, inspection_legal), the maintenance plan’s cadence (fixed to the calendar or floating from the last completion, every interval_days) and its next due date, and the checkpoints in order — each a room or a piece of equipment of this house (ref_id), or a general place named by its label, with the items checked there (check, reading with its unit and optional min / max, text, photo, and section headings). One active template per house and name: defining the name again revises it in place. The automation lane is its clock: a sweep over active templates whose due instant has come (next_due_at, the house’s midnight starting next_due_on) and that have no round open starts one (start_inspection_round); completing the round moves next_due_on on. open_round_id names the round in progress; revision counts the walks it has defined (a re-definition that moves the checkpoints is the next), and a start may name the one it saw.

Authorizations

aerandil_oauth
objects:read
aerandil_oauth
objects:hospitality.round_template:read

Parameters

Path Parameters

required

string format: uuid

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

link_type

required

Allowed values: hospitality.link.inspection_round_from_template hospitality.link.round_template_at_property

API name of the link type. Narrowed to link types that bind this source object type on at least one side.

Query Parameters

direction

Allowed values: out in

Edge direction to follow. Optional when the link binds the source on exactly one side; required for symmetric links.

limit

integer

>= 1 <= 500

cursor

string

as_of

string format: date-time

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

branch

string format: uuid

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

200

Neighbours along the typed link.

application/json

object

data

required

Array<object>

object

created_at

required

string format: date-time

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

No object with that id, or link type unknown.

422

Validation error — direction conflicts with the link’s binding.