REST

Your capture data over plain REST

api.busymate.net exposes entries, devices, settings, service stats, and infra status as a PostgREST + Edge Functions API — authenticated with the same OAuth token, scoped to your role.

Read the docs

API Console

GETapi.example.com/v1/users/42Send

200 OK165 ms1.2 KBapplication/json

{
  "id": 42,
  "name": "Ada Lovelace",
  "active": true,
  "roles": ["admin", "viewer"]
}

Query your latest entries — curl

bash

curl 'https://api.busymate.net/rest/v1/entries?select=id,host,method,status&order=created_at.desc&limit=20' \
  -H 'Authorization: Bearer <OAUTH_ACCESS_TOKEN>' \
  -H 'apikey: <OAUTH_ACCESS_TOKEN>'

Why REST

No SDK, no surprises

If your tool speaks HTTP, it speaks Busymate. Standard PostgREST query syntax over a Bearer token — the same identity that authorizes the dashboard, MCP, and Realtime.

Plain REST over PostgREST

Query entries, devices, settings, and service stats with standard REST verbs, filters, and pagination — no custom SDK required.

One OAuth token

Authenticate with the same OAuth access token that powers MCP and Realtime — issued via OAuth 2.1, no separate API key to manage.

Capability-scoped by role

Every request is gated by your role's capabilities through row-level security — the API can never return more than your role permits.

Build on the API

The docs cover authentication, the full table surface, and the Edge Function endpoints for stats and infra status.

Read the docs Open the dashboard