Resume a campaign

Return a paused campaign to running and immediately re-enqueue its pending contacts.

POST /api/v1/account/{account_id}/campaigns/{campaign_id}/resume

Resume a campaign

cURL

curl --request POST \
  --url https://api.vobiz.ai/api/v1/account/{account_id}/campaigns/{campaign_id}/resume \
  --header 'X-Auth-ID: <x-auth-id>' \
  --header 'X-Auth-Token: <api-key>'

POST https://api.vobiz.ai/api/v1/account/{account_id}/campaigns/{campaign_id}/resume

Returns the campaign to running and re-enqueues pending contacts straight away. Allowed only from paused.

Authentication required

• X-Auth-ID — your Vobiz account ID
• X-Auth-Token — your Vobiz auth token

account_id · string · required

Your Vobiz account ID. Use the same value in X-Auth-ID.

X-Auth-ID · string · required

Your Vobiz account ID, for example MA_XXXXXXXX.

campaign_id · string · required

The campaign to resume. It must be paused.

Example

cURL

curl -X POST \
  "https://api.vobiz.ai/api/v1/account/{account_id}/campaigns/{campaign_id}/resume" \
  -H "X-Auth-ID: {account_id}" \
  -H "X-Auth-Token: {auth_token}"

Sends the campaign.resumed webhook when notify_url is configured.

Some pause reasons clear on their own. A window_closed pause resumes at the next open window, and caller_pool_daily_limit_reached resumes at midnight in the campaign timezone. Reasons such as manual_pause, caller_pool_exhausted, and balance_insufficient need this endpoint after you fix the underlying cause.

Lifecycle

draft ──upload──▶ ready ──start/schedule──▶ running ──▶ completed
                     │                       │  ▲
                     │                       ▼  │
                     │                     paused
                     │                       │
                     └───────────────────────┴──▶ cancelled

non-running campaign ──archive──▶ archived

Invalid transitions return 409 Conflict. Control endpoints take no request body.