Skip to main content
GET
Get Batch Call Details
Read only Get Batch Call Details selects calls belonging to a batch in your workspace. The current API-key response for a normal paginated request is an empty object because batch detail fields are filtered out. Use List Calls with batch_call_id for paginated call records, or set export=true on this endpoint for a root array of matching call records.

When to use this

  • Operational dashboards: render the batch detail page with live progress.
  • Status polling: use List Calls with the batch ID while a campaign is waiting or running.
  • Audit logs: inspect the calls created for the batch and their current outcomes.
  • Re-run preparation: compare previous call outcomes before creating a new batch with Create Batch Call.
To list every batch, use List Batch Calls. To investigate calls in the dashboard, use Call History and filter by the batch ID.

Path parameters

Common query parameters

The returned callLogs page supports the same operational filters used by call log browsing.

Errors

  • 400 Bad Request is returned when query parameters are invalid or an export exceeds the applicable row limit.
  • 404 Not Found is returned when the batch does not exist.

Authorizations

Authorization
string
header
required

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

Path Parameters

id
string
required

Batch call ID

Example:

"batch_abc123"

Query Parameters

agent_id
string

Filter by agent ID(s) - can be a single ID or comma-separated list (e.g., 1,2,3)

call_id
string

Filter by call ID - can be a single ID or comma-separated list (e.g., call_abc,call_def)

batch_call_id
string

Filter by batch call ID - can be a single ID or comma-separated list (e.g., batch_abc,batch_def)

from
string

Filter by sender phone number

to
string

Filter by recipient phone number

type
enum<string>

Filter by call type(s) - can be a single value or comma-separated list

Available options:
phone,
web
call_direction
enum<string>

Filter by call direction(s) - can be a single value or comma-separated list

Available options:
inbound,
outbound
latency_min
number

Filter by minimum latency (in milliseconds)

latency_max
number

Filter by maximum latency (in milliseconds)

agent_version_id
string

Filter by agent version ID(s) - can be a single ID or comma-separated list (e.g., 1,2,3)

agent_version_name
string

Search by agent version name (partial match, case-insensitive)

sentiment
enum<string>

Filter by sentiment(s) - can be a single value or comma-separated list

Available options:
positive,
neutral,
negative,
unknown
start_date
string

Filter by start date (ISO format)

end_date
string

Filter by end date (ISO format)

duration_greater_than
number

Filter by minimum call duration (in milliseconds)

duration_less_than
number

Filter by maximum call duration (in milliseconds)

duration_min
number

Filter by minimum duration range (in milliseconds)

duration_max
number

Filter by maximum duration range (in milliseconds)

page
number

Page number (starts from 1)

Example:

1

limit
number

Number of records per page (min: 1, default: 20, max: 200)

Example:

20

created_at
enum<string>

Sort by created_at (asc or desc)

Available options:
asc,
desc
duration
enum<string>

Sort by duration (asc or desc)

Available options:
asc,
desc
status
string

Filter by call status(es) - can be a single status or comma-separated list

export
boolean

Set to true to export all data without pagination

end_reason
string

Filter by end/hangup reason - exact match; comma-separate multiple values for OR filtering

columns
string

Export only: comma-separated column keys. Omitting both transcript and summary raises the single-export limit from 5000 to 10000 rows. Omit this parameter to include all columns.

Example:

"duration,status,agent_name"

is_ivr
boolean

Filter by whether the call was handled by an IVR agent. Both promoted or transferred calls and pure menu calls count. Set true for IVR calls only, false for non-IVR calls only, or omit for all.

tags
string

Filter by lead tags snapshotted onto the call when it was placed. Comma-separated for multiple values. Matching is case-insensitive because tags are lowercased on upload.

Example:

"priority,q3-campaign"

tags_match
enum<string>
default:any

How multiple tags values combine. Use any to return calls carrying at least one, or all to return only calls carrying every one.

Available options:
any,
all

Response

Calls in the batch returned successfully.

The response is of type object.