Monitors
live8 operations
Check an endpoint on a schedule: runs, health, uptime and latency.
From nothing to an answer, then the setup for a server. The quickstart has the detail.
One click here, or in the console for other scopes and a longer life.
Send the token on every call. GET /v1/me answers who the API thinks you are. Send it from here with the token from step one, or from a terminal.
curl https://api.inorbit.hr/v1/me \
-H "Authorization: Bearer $TOKEN"{
"subject": "ak_7f3k…",
"kind": "client",
"scopes": ["identity:read", "account:read"],
"org": "…"
}Every page of the reference has the same token bar and a playground that sends it: fill the fields in, press Send, read the answer. The samples beside it carry the token too.
A server that keeps a secret makes an API key in the console and exchanges it for a token that lives fifteen minutes: the OAuth 2.0 client credentials grant.
curl -u "$KEY_ID:$KEY_SECRET" https://auth.inorbit.hr/oauth2/token \
-d grant_type=client_credentials \
-d audience=iohr-api \
-d scope="identity:read account:read"By what you are trying to do. Times are for a first read.
Four guides, in order: a first call, the credential your code will keep, the command line, a client in your language.
Check what matters on a schedule and hear about it where you already listen.
From the first page to the postmortem. The guide is being written with the product.
Reach what our cloud cannot: the agent runs in your network and only connects out.
PRDs, ADRs and RFCs linked to the code, and the map they will feed.
Who may call what, what each call costs, and the bounds every client should expect.
Connect the tools you already use, and let an assistant act as you.
The rules every call follows, whichever way it travels.
Every route a token may call, by product area, from the live OpenAPI document. Each opens its reference page with a playground.
8 operations
Check an endpoint on a schedule: runs, health, uptime and latency.
no public routes yet
Open, acknowledge and resolve incidents, and write the postmortem.
Not in the public API yet. A monitor's health changes arrive as the events monitor.down and monitor.recovered.
Get told when a monitor goes down48 operations · Decisions, Corrections
Spaces of PRDs, ADRs and RFCs: documents, versions, reviews, comments and diagrams.
19 operations
Connect outside systems, grant their use to a token or a product, and call their actions.
6 operations
Enroll the agent in your network, revoke it, and run checks through it.
19 operations · Webhooks, Test inboxes, Events
The event catalogue and live stream, webhook endpoints, deliveries and test inboxes.
15 operations · Identity, Accounts, Usage and units, Domains
Who is calling, the account and its audit log, verified domains, usage and units. Keys are made in the console or with iohr token create.
4 operations
The catalogue iohr ext install reads: listings, versions, scopes and publishers.
4 operations
Consented recordings of how people move through a site, from the browser extension.
3 operations
The weekly digests of what changed in Go, Rust and Solidity.