The three documents
Every capture endpoint takes atool query parameter selecting which government
document the session fills:
Ways to capture a conversation
Whichever way the audio arrives, the same pipeline runs afterwards, and the same
session resources and results
come out.
Session lifecycle
A session moves through phases, visible in the snapshot and on the SSE stream:error and cancelled are terminal. A failed session can be resumed from its saved
audio with POST /sessions/:id/resume — the conversation is never re-run, only the
processing.
SSE events
POST /sessions/:id/stream replays the session’s buffered events, then follows live: