Retrieve Voice AI Agent Execution API
Fetch specific execution details of a Voice AI agent, including conversation times, statuses, and metrics, via Bolna APIs.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The unique id of the agent
The unique execution_id by the agent
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
Extracted data in JSON format which was mentioned in the agent extraction_prompt
{
"user_interested": true,
"callback_user": false,
"address": "42 world lane",
"salary_expected": "42 bitcoins"
}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"}).

