Skip to main content
POST
Resume a paused run
Puts a paused run’s held calls back on the dispatch queue.

What comes back

Exactly what pause held, plus anything attached while the run was paused. Nothing is dropped, and nobody is called twice — a contact already reached during the running window has a call behind them and is not re-queued.
affectedCalls is how many calls were restored.

Only from PAUSED

Resuming a run that is not paused is a 422. In particular there is no resume from CANCELLED, which is terminal.

Error Scenarios

  • 404 Not Found: the run does not exist, or belongs to another company
  • 422 Unprocessable Entity: the run is not paused
  • 403 Forbidden: the API key does not hold write:runs

Pause Run

What resume undoes

Get Run

Watch it dial again

Authorizations

Authorization
string
header
required

API key for authentication using Bearer scheme

Path Parameters

id
string<uuid>
required

Query Parameters

companyId
string

Required for ATS API keys to specify which company to access. Ignored for standard company API keys.

Response

Transition applied

status
enum<string>
required

The run's status after the transition

Available options:
DRAFT,
SCHEDULED,
RUNNING,
PAUSED,
COMPLETED,
CANCELLED
Example:

"RUNNING"

affectedCalls
number
required

How many of the run's calls this request moved: queued by a launch, withdrawn by a pause, restored by a resume, closed out by a cancel. Not calls placed - a 2xx means queued, not dialled.

Example:

42