Loading the description…
What the board page does, it does through this. The browser is one client of it, not a privileged one.
Two tokens, two doors. The board token, in an
Authorization: Bearer … header or a ?token= query, opens everything
under /api. The registration token opens only POST /api/report: a
machine can announce itself with it, and cannot read the board.
No command travels through it. POST /api/do/… names something a
machine published in its own Argus config, and the machine decides whether the board may
ask for it.
The most useful call to start with is the board itself: every machine, as of the last sweep. It needs nothing but curl:
curl -s http://your-board:8070/api/board \ -H "Authorization: Bearer $PANOPTES_TOKEN"
The machine-readable description is
openapi.json: point Swagger UI, Postman or a client
generator at it. A running board serves its own at /api/openapi.json,
behind the token.
Loading the description…