The layout a page shows: the caller's own, else the account's default, else none (origin: default, the page's own order). page is the page's id: overview, agent, local.overview.
Needs scope account:read.
bearerAuthorizationBearer <token>An access token from the identity provider: a person's, or a customer's from the client credentials grant with an API key (developers.inorbit.hr). The gateway verifies it; the audience is iohr-api.
org_id*stringThe account's id: org in GET /v1/me.
page*stringThe page's id: overview, agent or local.overview.
iohr.accounts.v1.GetLayoutResponse
application/json- response
iohr.accounts.v1.GetLayoutResponse
account_default?iohr.accounts.v1.Layout
can_set_default*booleanlayout?iohr.accounts.v1.Layout
origin*stringimport { ApiError, Public } from "@inorbithr/sdk";// Reads INORBIT_TOKEN, or INORBIT_KEY_ID and INORBIT_KEY_SECRET.const api = Public.fromEnv();try { const { value } = await api.accounts.getLayout("<org_id>", "<page>"); console.log(value);} catch (e) { if (!(e instanceof ApiError)) throw e; console.error(`${e.code}: ${e.problem} (request id ${e.raw.requestId})`);}npm install @inorbithr/sdk. Calls the package's public surface; an operation newer than your package needs the next release or a client generated for your account. The SDKs.
{ "account_default": { "page": "string", "scope": "string", "updated_at": "string", "updated_by": "string", "version": "string", "widgets": [ { "hidden": true, "span": 0, "widget": "string" } ] }, "can_set_default": true, "layout": { "page": "string", "scope": "string", "updated_at": "string", "updated_by": "string", "version": "string", "widgets": [ { "hidden": true, "span": 0, "widget": "string" } ] }, "origin": "string"}List dashboard layouts GET
The account's default layouts, page by page: which boxes a console page shows, in what order and how wide (columns of 12). A key with `account:read` reads the account's defaults; a person also gets their own. One page holds them all. Needs scope `account:read`.
Get the monitors board GET
How the account's monitors page is organised: its own categories on top of the six built in, their order, which category a monitor was moved to (over the one the monitor or an agent's checks.toml declares, which stays as it is) and the order inside each; for a person, also their own view (pins, folded categories, sort, list or cards). Needs scope `account:read`.