REST

Plain HTTP over everything the platform knows

Standard REST verbs and filters over your entries, devices, settings and stats — plus TestFlight, billing, the audit ledger and BusyBro's own state. curl works on day one; an SDK is never required.

Read the docs

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, scoped by the database itself.

No SDK, ever

It's PostgREST underneath: predictable URLs, standard filters, JSON in and out. If your language can make an HTTP request, it's already integrated.

Wider than you think

It's not just captured traffic. TestFlight admin, billing, the audit ledger, even BusyBro's sessions and memories are all reachable over the same REST surface.

One token, enforced by the database

The same OAuth token you use for MCP and WebSockets works here, and Postgres row-level security scopes every response to your role. There's no 'the API forgot to check' — the database is the check.

Try it in the docs

The in-dashboard REST explorer builds and fires real requests with your own permissions and renders the live response inline. What you see is exactly what your code will get.

Build on the API

The docs cover authentication, the full table surface, and the Edge Function endpoints — or fire real requests from the in-dashboard REST explorer.

Read the docs Open the REST explorer