Sign in

API v1 liveDeveloper docs

Build on InOrbit.
Start in five minutes.

Monitors, Decisions, connections and the agent in your network, behind one API at api.inorbit.hr/v1: REST, event streams, a WebSocket, MQTT and MCP on the same routes.

Start in 5 minutes

$ brew install inorbithr/tap/iohr
$ iohr --version
iohr 0.1.0-alpha.13
$
iohr 0.1.0-alpha.13, signed and with provenance. Every way in, and how to verify it, is on the command line page.Install iohr
0%

Your first call

From nothing to an answer, then the setup for a server. The quickstart has the detail.

  1. 01

    Create a token

    One click here, or in the console for other scopes and a longer life.

    Have a token? Manage tokens in the console
  2. 02

    Call the API

    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.

    Request
    curl https://api.inorbit.hr/v1/me \
      -H "Authorization: Bearer $TOKEN"
    200 OK
    {
      "subject": "ak_7f3k…",
      "kind": "client",
      "scopes": ["identity:read", "account:read"],
      "org": "…"
    }
    Run it from here
    Create or paste a token above, then send the call from this browser.

    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.

  3. 03

    For a server, use a key

    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"

Respond to incidents

From the first page to the postmortem. The guide is being written with the product.

Decisions and Atlas

PRDs, ADRs and RFCs linked to the code, and the map they will feed.

API reference

Every route a token may call, by product area, from the live OpenAPI document. Each opens its reference page with a playground.

126 operations10 areasEvery public route, by product area.

Incidents

preview

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 down