---
title: "Resume a paused parallel-dialer session by auto-fetching next batch"
method: POST
path: "/voice/dialer/sessions/{session_id}/resume"
tags: ["Voice"]
---

# Resume a paused parallel-dialer session by auto-fetching next batch

`POST /voice/dialer/sessions/{session_id}/resume`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/voice/dialer/sessions/{session_id}/resume`
- Auth: HTTP bearer

Resume a PAUSED parallel-dialer session.

The voice service's ``PATCH /sessions/{id}/status`` rejects
``ACTIVE`` - the real resume flow is to call ``start-session`` again
with the existing ``session_id`` and a fresh batch of contacts. This
route does the lookup + filtering + forwarding in one shot so an MCP
caller only has to supply the session id (and optionally a batch
size).

Steps performed server-side:

1. Fetch the session via ``GET /api/parallel-calls/sessions``
   (filtered to the caller's org). Voice has no per-id GET, so we
   page with ``page_size=200`` and find the row.
2. Verify the session belongs to the caller's org and is in the
   ``PAUSED`` state. ACTIVE / COMPLETED sessions return 422.
3. Read ``list_id`` and the ``list_offset`` cursor from
   ``session_metadata``. Sessions created without a ``list_id``
   (ad-hoc / campaign-mode) cannot be resumed via this route and
   return 422.
4. Page contacts out of the source list starting at the cursor,
   skipping rows already in ``session.contact_ids`` and rows that
   have no usable phone field.
5. Forward up to ``max_contacts`` rows to voice's
   ``/api/parallel-calls/start-session`` with the existing
   ``session_id``. Voice de-duplicates active calls within the
   session and auto-promotes status to ACTIVE on success.

The ``list_offset`` we send back to voice is advanced by the total
number of rows we read from the list (called + skipped + dialed) so
a future resume picks up where we left off, not where the previous
pause cursor sat.

## Path parameters

- `session_id` string, required: Session UUID.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- DialerSessionResumeRequest: Body for resuming a paused parallel-dialer session. The resume endpoint mirrors what the dialer UI does when the SDR clicks "Start Dialing" on a paused session: it pages the source list using the cursor stored in ``session_metadata``, filters out already-called contacts, and forwards the next batch to the voice service's ``start-session`` endpoint. Only ``max_contacts`` is exposed - org / user / from_phone / list_id / agent / session_metadata are all read off the persisted session so the caller doesn't have to reconstruct them.
  - `max_contacts` integer: Number of contacts to dial in this batch. Voice caps parallel dialing at 4.

## Response `200`

Successful Response

- ApiResponseDialerSessionResumeResponse
  - `data` DialerSessionResumeResponse, required: Echo of voice's ``ParallelDialResponse`` plus a count of contacts dialed. ``dialed_count`` is the number of calls actually placed in this resume batch. It can be lower than ``max_contacts`` when the list is near exhausted, every remaining row is missing a phone, or every candidate was already called earlier in the session. ``twilio_token`` and ``conference_name`` are deliberately dropped - they are SDR-frontend specific and an MCP / API caller has no use for them. The dialer UI regenerates them on join.
    - `session_id` string, required
    - `status` string, required
    - `message` string, nullable
    - `name` string, nullable
    - `org_id` string, nullable
    - `user_id` string, nullable
    - `user_email` string, nullable
    - `from_phone` string, nullable
    - `session_metadata` object, nullable
    - `total_calls` integer
    - `dialed_count` integer
    - `created_at` unknown
    - `updated_at` unknown
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)