# Batches

A batch represents a group of call sessions initiated together as a single operation. 

Batches are useful for scenarios like outbound campaigns, notifications, or any use case requiring multiple calls to be placed concurrently with controlled pacing.



## Stop processing a batch of call sessions

 - [DELETE /v2/projects/{projectId}/batches/{batchId}](https://developers.sinch.com/docs/voice-2.0/api-reference/voice/batches/stopbatchprocessing.md): Stop processing a batch of call sessions.  This will prevent any queued calls in the batch from being initiated.  Calls that are already in progress will not be affected and will continue until completion.

## Get a batch summary

 - [GET /v2/projects/{projectId}/batches/{batchId}](https://developers.sinch.com/docs/voice-2.0/api-reference/voice/batches/getbatchcallsummary.md): Retrieve a summary of a batch call operation, including statistics on completed, failed, in-progress, and queued calls.  This provides an overview of the batch execution state and individual call session states.

## Get batch details

 - [GET /v2/projects/{projectId}/batches/{batchId}/details](https://developers.sinch.com/docs/voice-2.0/api-reference/voice/batches/getbatchdetails.md): Retrieve per-session details for a batch call operation, including the current state of each call session in the batch.
Use this endpoint when individual session-level visibility is needed (for example, to inspect which sessions are QUEUED, IN_PROGRESS or COMPLETED). EXPIRED sessions are never returned because they were never initiated.