Get Individual Call Status
Get the status of an individual call within a batch operation
GET
Headers
x-api-keystringrequiredAPI key used for authenticating requests to the API.
x-workspace-idstringrequiredWorkspace identifier for the API.
Path Parameters
batchIdstringrequiredThe unique identifier of the batch call operation
jobIdstringrequiredThe unique identifier of the individual call job
Response
jobIdstringThe unique identifier of the call job
statusstringCurrent status of the individual call
waiting- Call is queued and waiting to be processedactive- Call is currently in progresscompleted- Call completed successfullyfailed- Call failed due to an error
phone_numberstringThe phone number that was called
startTimenumberTimestamp when the call started (if applicable)
endTimenumberTimestamp when the call ended (if completed or failed)
durationnumberDuration of the call in seconds (if completed)
errorstringError message if the call failed
resultobjectCall result data including conversation details (if completed)
Example Usage
curl -X GET "https://api.trillet.ai/v1/api/batch-calls/batch_7891011121314/calls/call_123" \
-H "x-api-key: YOUR_API_KEY" \
-H "x-workspace-id: YOUR_WORKSPACE_ID"
Example Response (Completed Call)
{
"jobId": "call_123",
"status": "completed",
"phone_number": "+1234567890",
"startTime": 1703097600000,
"endTime": 1703097642000,
"duration": 42,
"result": {
"callId": "call_abc123",
"transcript": "Hello John, this is an automated call...",
"outcome": "successful",
"metadata": {
"first_name": "John",
"last_name": "Doe",
"email": "john.doe@example.com"
}
}
}
Example Response (Failed Call)
{
"jobId": "call_124",
"status": "failed",
"phone_number": "+1987654321",
"startTime": 1703097600000,
"endTime": 1703097615000,
"error": "Number busy - unable to connect after 3 attempts"
}
Example Response (Active Call)
{
"jobId": "call_125",
"status": "active",
"phone_number": "+1555666777",
"startTime": 1703097700000
}
Error Responses
statusstringWill be "not_found" if the call doesn't exist
errorstringError message describing what went wrong
Common Error Codes:
404- Call not found with the specified job ID500- Server error retrieving call status
Use Cases
- Monitor individual call progress within a batch
- Retrieve detailed results for completed calls
- Debug failed calls to understand failure reasons
- Track call timing and duration metrics
