Patch Call Batch
Change a batch’s policy while it runs. The next pass picks it up.
Everything here is policy, so nothing revisits a recipient already called,
and calls in flight finish under the policy they were dispatched with. You
do not need this to pick up a republished prompt — every call already runs
the current published version. start_at moves only while the batch is
still scheduled.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Policy edits, allowed while a batch is scheduled, running or paused.
calling_window and start_at accept an explicit null to clear
them — "dial at any hour", "start on the next pass" — which is why the
service reads model_fields_set rather than treating absent and null the
same way. Every other field keeps the usual PATCH rule: absent means
unchanged.
The hours a batch may dial in, on the batch's own clock.
A window that crosses midnight (21:00–06:00) is valid and means
exactly what an evening consumer-calling window means: the day check applies
to the start side, so 21:00–06:00 on days: [5] runs Friday
21:00 through Saturday 06:00.
1 <= x <= 51 <= x <= 101 - 2005 <= x <= 1440Response
Successful Response
The hours a batch may dial in, on the batch's own clock.
A window that crosses midnight (21:00–06:00) is valid and means
exactly what an evening consumer-calling window means: the day check applies
to the start side, so 21:00–06:00 on days: [5] runs Friday
21:00 through Saturday 06:00.
scheduled, running, paused, completed, canceled, failed What a call ran, frozen at the moment it started.
Written only when the call differs from "the published agent, as-is" — so a
null agent_plan means exactly that. members[0] is the agent that
answered.