Create Batch Call
Authentication
Enter your API key with the Bearer prefix, e.g. ‘Bearer sk_…’.
Headers
Request
Human-readable batch name.
Caller-ID override. Falls back to the agent’s bound number.
Schedule the batch for a future time (RFC 3339). Omit to start immediately.
Ringing timeout in milliseconds applied to every call in the batch (how long each recipient rings before the dial gives up). Range 1000-80000 (1-80s). Omit to use the 30s default. Express this in milliseconds even if a UI collects seconds.
Response headers
Response
Prefixed wire identifier (batch_<26 char Crockford base32>).
URL paths accept only this
prefixed form; legacy UUID path parameters are rejected with
404.
Prefixed wire identifier (agent_<26 char Crockford base32>)
of the agent that will run the batch.
Human-readable batch name.
Lifecycle status. A batch deferred to a future time is
pending with a non-null scheduled_at; it moves to running
once the scheduled time arrives and the dispatcher starts
dialing.
Total number of recipients (the progress denominator).
Caller-ID override. When set, prefixed wire identifier
(phone_<26 char Crockford base32>) of the phone number to
use; falls back to the agent’s bound number when null.
Per-call ringing timeout in milliseconds applied to every recipient in the batch. Null when the batch uses the 30s default.