REST API reference

Two lean, read-only REST endpoints for your recordings — for everything else (content, action items, search) the MCP server is the primary interface.

Updated 4 July 2026

Authentication

Bearer token

Every request needs your API key in the header: Authorization: Bearer kuno_live_…. Create keys in the Kuno app under Settings → Developer.

List recordings

GET /v1/recordings

Lists your recordings, newest first. Requires recordings.read.

Parameter	Type	Description
limit	integer	1–100, default 50.
cursor	string	Pagination cursor from the previous response's `nextCursor`.
bucket	string	`all` (default), `today` or `week`.

curl "https://api.heykuno.com/v1/recordings?limit=2" \
  -H "Authorization: Bearer kuno_live_your_key"

{
  "items": [
    {
      "id": "9c1f…",
      "title": "Site walkthrough Müllerstraße",
      "status": "completed",
      "createdAt": "2026-07-03T09:12:00Z"
    }
  ],
  "nextCursor": "eyJvZmZzZXQiOjJ9"
}

Fetch one recording

GET /v1/recordings/:id

Metadata of a single recording (id, title, status, createdAt). Requires recordings.read.

Note content & action items

Summaries, transcripts and action items are read through the MCP server (POST /v1/mcp) — its get_recording and list_action_items tools return the full content, scope-checked per tool.

Why no REST endpoint for content? The MCP server is the primary integration surface for Kuno data in AI tools and covers all read use cases today. For server-side notifications without polling, see Webhooks; more REST endpoints will follow once they are stable.

Error codes

Status	Meaning
401	Key invalid, expired or revoked (`api_key_auth_failed`).
403	Missing scope or route not permitted for API keys (`api_key_route_not_permitted`).
429	Rate limit reached — retry with backoff.

Was this helpful?