Skip to main content
POST
Resume a campaign

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, billing:write, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access within the workspace's available capabilities.

Path Parameters

id
string<uuid>
required

Campaign ID.

Body

application/json

Optional. An empty body is fine unless the sequence of the paused campaign was changed.

compliance_attestation
boolean

Set to true to confirm that the campaign complies with all laws and consent requirements that apply to the contacts being called, including do-not-call lists and opt-in rules. Stored with the campaign (who, when, from which surface). Required to resume a campaign whose sequence was changed while it was paused.

locale
enum<string>

Language of the confirmation wording that is stored. Defaults to the Accept-Language header, then en.

Available options:
en,
de,
fr,
es

Response

Campaign resumed.

data
object
required