CallBatchSubmissionResponse

The 202 submission response: the batch summary, one pre-created call per created item, and the rejected entries.

calls keeps submission order, with one cutover exception: A batch that was partly processed when Resia moved to per-item IDs (2026-08-25) can order its items differently — match items by to_phone_number or client_reference. rejected_calls lists every submitted entry Resia did not create, each with its 0-based submission position. calls and rejected_calls together account for every submitted entry. A repeated Idempotency-Key returns the same batch again — the same batch ID, the same call_id values, and the same entries reported as rejected.

  • The Call Agent every call in the batch follows.

  • How the batch's calls are distributed across states right now.

    Properties: 8
  • When Resia accepted the batch.

  • Identifier of the batch.

  • The batch's derived lifecycle state.

    values
    in_progresscompletedcanceled
  • How many calls the batch created. Equal to the submitted count minus the rejected entries; zero when every entry was rejected.

  • One item per created call, in submission order (one cutover exception — see CallBatchItemPage), each with its final call_id. Empty when every submitted entry was rejected.

    Properties: 5
  • When the batch reached a terminal state, or null while it is still in progress.

  • The caller number used, or null when the default was used.

  • Every submitted entry Resia did not create, each with its 0-based submission position and the reason. Empty when every entry was created.

    Properties: 4
  • Open key/value labels on this record. Set any keys and any values. Filter a list by one key and value pair. Resia never interprets a tag. Do not put names, phone numbers, or any personal, health, credential, or secret information in a tag: a tag travels in URLs when used as a filter, and URLs appear in ordinary infrastructure request logs.

    Properties: 1