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.
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.
iohr.accounts.v1.GetMonitorBoardResponse
application/json- response
iohr.accounts.v1.GetMonitorBoardResponse
account?iohr.accounts.v1.MonitorBoard
can_edit_account*booleanperson?iohr.accounts.v1.MonitorBoard
import { 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.getMonitorBoard("<org_id>"); 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": { "categories": [ { "builtin": true, "colour": "string", "id": "string", "name": "string" } ], "category_order": [ "string" ], "collapsed": [ "string" ], "monitor_order": [ { "category_id": "string", "monitor_ids": [ "string" ] } ], "pins": [ "string" ], "placements": [ { "category_id": "string", "monitor_id": "string" } ], "scope": "string", "sort": "string", "updated_at": "string", "updated_by": "string", "version": "string", "view": "string" }, "can_edit_account": true, "person": { "categories": [ { "builtin": true, "colour": "string", "id": "string", "name": "string" } ], "category_order": [ "string" ], "collapsed": [ "string" ], "monitor_order": [ { "category_id": "string", "monitor_ids": [ "string" ] } ], "pins": [ "string" ], "placements": [ { "category_id": "string", "monitor_id": "string" } ], "scope": "string", "sort": "string", "updated_at": "string", "updated_by": "string", "version": "string", "view": "string" }}Get a dashboard layout GET
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`.
List audit log entries GET
The account's audit log: who changed its members, roles, invitations, keys, tokens, name, plan, policy or deletion, and when, with the changed fields before and after. Newest first; with `after`, only newer entries, oldest first, which is how an `audit.event` webhook receiver fetches what it was told about. Needs a token given `account:audit`, and reads its own account. Needs scope `account:audit`.