GET
/
v1
/
api
/
batch-calls
/
{batchId}
/
calls
/
{jobId}
curl --request GET \
  --url https://api.trillet.ai/v1/api/batch-calls/{batchId}/calls/{jobId} \
  --header 'x-api-key: <api-key>' \
  --header 'x-workspace-id: <x-workspace-id>'
{
  "jobId": "<string>",
  "status": "<string>",
  "phone_number": "<string>",
  "startTime": 123,
  "endTime": 123,
  "duration": 123,
  "error": "<string>",
  "result": {}
}

​
Headers

​
x-api-key
string
required

API key used for authenticating requests to the API.

​
x-workspace-id
string
required

Workspace identifier for the API.

​
Path Parameters

​
batchId
string
required

The unique identifier of the batch call operation

​
jobId
string
required

The unique identifier of the individual call job

​
Response

​
jobId
string

The unique identifier of the call job

​
status
string

Current status of the individual call

  • waiting - Call is queued and waiting to be processed
  • active - Call is currently in progress
  • completed - Call completed successfully
  • failed - Call failed due to an error
​
phone_number
string

The phone number that was called

​
startTime
number

Timestamp when the call started (if applicable)

​
endTime
number

Timestamp when the call ended (if completed or failed)

​
duration
number

Duration of the call in seconds (if completed)

​
error
string

Error message if the call failed

​
result
object

Call 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

​
status
string

Will be “not_found” if the call doesn’t exist

​
error
string

Error message describing what went wrong

Common Error Codes:

  • 404 - Call not found with the specified job ID
  • 500 - 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