Skip to content
API docs

Overview

Lobbe is meeting memory. You record or upload a meeting, Lobbe transcribes it and writes a Lobbe: the summary, the decisions and the action items, kept in your archive.

A personal API token lets your own tools and agents do the same: submit a meeting, wait for it, read its Lobbe and ask about it. A meeting sent with a token spends the same minutes from your balance as one recorded in the app.

The agent loop

Section titled “The agent loop”
submit   POST /api/v1/recordings                    → 202 { recording: { id, status: QUEUED, minutes, statusUrl } }
wait     GET  /api/v1/recordings/:id/status  (60 s) → QUEUED → TRANSCRIBING → [NAMING] → GENERATING → READY
                                                       └─ NAMING: { naming: { url, deadline } }
                                                            hand naming.url to the person, or
                                                            POST /api/v1/recordings/:id/naming { action: "skip" }
read     GET  /api/v1/recordings/:id/bundle[?format=markdown]
act      GET  /api/v1/recordings/search?q=…   ·   POST /api/v1/recordings/:id/ask   ·   POST /api/v1/series/:id/ask
many     GET  /api/v1/events?after=<cursor>   (instead of one status poll per meeting)

Where next

Section titled “Where next”