Skip to main content
GET
cURL
Returns what the dashboard’s Debugging view shows for one call, in a single response. Use it when you want to find out why a call was slow, dropped or went off script without stitching together Get execution, the per-turn latency and Get raw logs yourself. The Bolna MCP server uses it for its get_execution_debug tool.

Sections

Pass include to fetch only some sections, for example ?include=execution,logs. Leave it out to get all three. Any other value returns 400.

Reading LLM requests

Every LLM request resends the full prompt and the conversation so far, so in logs each llm request after the first carries only the text it adds. Its data_shared_prefix_chars says how many leading characters it shares with the previous request. To rebuild the full text of each request:
The first request is always whole: it is the exact prompt that ran, with variables filled in. The bundle is trimmed for size. For the full data, use Get execution and Get raw logs.

When a section is missing

One section never fails the whole response. A section that doesn’t exist for this call, or that fails to load, comes back null, and unavailable names it with the reason:

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

execution_id
string<uuid>
required

The unique execution_id

Query Parameters

include
string

Comma-separated sections to return, from execution, progression and logs. Omit to return all three. Any other value returns 400.

Example:

"execution,logs"

Response

Debug bundle for the execution

execution_id
string<uuid>

The execution this bundle is for

unavailable
object

Sections that came back null, each with the reason. not_available means there is no data for that section on this call; error means it failed to load.

Example:
execution
object | null

The execution, keeping only fields that help debug a call (status, error_message, provider and numbers, timestamps, conversation_duration, total_cost, cost_breakdown, usage_breakdown, telephony_data, latency_data, context_details, extractions, summary, tool_call_logs, transfer_call_data, retries). Empty fields are dropped and the prose transcript is left out. Present only when requested.

progression
object | null

Per-turn latency and the structured transcript. Present only when requested.

logs
object[] | null

The call's pipeline logs in order, followed by one webhook entry with its webhook deliveries (calls from the last 14 days only). Present only when requested.