Get Conversation Snapshot
Did this conversation go well? One verdict over the whole thread.
issues names every problem found across every session in the thread —
errors, failed tools, slow responses, a bad connection — and ok is true
when there were none. Cost and duration sum across sessions; latency and
tooling come from the merged timeline.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Successful Response
The band at the top of the call and conversation views.
The worst reading on each side of the call, kept apart on purpose.
A collapsed "the connection was poor" reads as a platform fault even when
the poor leg was the caller's own network, which is the difference between
a support ticket and a shrug. overall stays for readers that only want one
word; agent and caller are unknown on calls whose trace predates the
side field.
How the call sounded, as opposed to how fast the stack was.
Derived from started_speaking_at / stopped_speaking_at, which LiveKit
puts on every message and nothing has ever read. None of it is a platform
defect — a long reply is the prompt's doing and a long silence is often the
caller thinking — which is why it lands here as numbers rather than in
issues.