Retrieve voice AI execution API
Fetch details of a specific phone call execution by its ID using Bolna APIs. This includes information such as conversation time, status, and telephony data.
Status lifecycle
A call moves through these statuses. Always wait forcompleted (or a hard-failure terminal) before reading conversation_duration, total_cost, recording_url, or extracted_data — these fields are null or 0 until then.
Completed execution example
summary field and the General > Call Summary entry in extracted_data are populated only when the agent’s call_summary_enabled toggle is on (off by default). The Call Summary entry carries only a subjective value — the confidence, reasoning, and objective fields of regular extractions do not apply to it.
For graph agents, node_extracted_data holds the values the agent’s edges collected during the call, the latest value per key, for example {"availability": "Yes", "callback_hour": 18}. It is null for other agents. See Inline data extraction.
Production pattern: webhook instead of polling
For production workloads, setwebhook_url on your agent and Bolna will POST the execution payload to you automatically — no polling needed. Whitelist source IPs 13.203.39.153, 13.126.9.249 and 13.202.133.53. See Webhooks.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The unique execution_id
Response
Retrieve specific execution by an agent
Unique identifier for the execution
"4c06b4d1-4096-4561-919a-4f94539c8d4a"
Unique id of the agent
Unique id of the batch
^[a-f0-9]{32}$"baab7cdc833145bf8dd260ff1f0a3f21"
Total time duration for the conversation (in seconds)
Total cost incurred by this execution in cents
Current status of the call. Typical progression: queued → initiated → ringing → in-progress → call-disconnected → completed. Important: call-disconnected fires the instant the line drops, before duration, cost, recording URL, and extracted_data are finalized. The true terminal state is completed (or no-answer, busy, failed, canceled, stopped, error, balance-low). Always wait for completed before reading those fields.
scheduled, queued, rescheduled, initiated, ringing, in-progress, call-disconnected, completed, balance-low, busy, no-answer, canceled, failed, stopped, error Associated error message (if any)
If the call was answered by voice mail
Transcription of the execution
Timestamp of agent execution
"2024-01-23T01:14:37Z"
Last updated timestamp for the execution
"2024-01-29T18:31:22Z"
Breakdown of the costs in cents
Telephony call data
Telephony call data
Batch information
AI-generated summary of the call. Populated only when the agent's call_summary_enabled toggle is on; null otherwise. The same text also appears in extracted_data under General > Call Summary with only a subjective value.
Extracted data in JSON format which was mentioned in the agent extraction_prompt
Graph agents only: the values the agent's edge parameters collected during the call, the latest value per key. null for other agents.
Custom variable data injected in the call. For batch executions, the sub-object context_details.recipient_data contains every non-contact_number column from the uploaded CSV row (e.g. {"customer_name": "Asha", "appointment_day": "Friday"}).

