Get Conversation
Fetch a conversation’s execution, activity thread, usage, and sub-executions.
Authorizations
API Key for authentication
Response
Successful Response
Combined view of one chat conversation.
conversation_id is the parent gateway execution id, which is also the
activity-thread id. execution, activity, and usage can each be
independently None when the upstream is unavailable — the route returns
404 only when BOTH execution AND activity are missing.
usage at this root level is aggregated across the parent execution
AND every entry in sub_executions (single upstream call to the
llm_usage:aggregate endpoint). Per-sub usage is mirrored on each
SubExecutionResponse.usage so clients don't have to fan-out.
Parent gateway execution row (status, result, sub_executions, deep_planning, …).
Ordered message list (user, agent, tool calls, reasoning, …).
Aggregate cost + token usage over parent + every sub-execution. Best-effort.
Triple-shape entry for every sub-execution spawned by this conversation.
Per-message feedback rows recorded against the parent execution.

