Skip to main content
POST
Start Campaign
To let Ringg choose caller numbers from a number pool instead, use Start campaign (number pool). list_id is the one returned by Upload campaign contact list; agent_id is the agent the list was uploaded for; from_numbers are workspace numbers from List workspace numbers: send each number’s id (recommended), or the number written exactly as it is listed there. Each retry dials the next number in the list.
A success returns {"status": "campaign registered successfully!"} and the campaign’s campaign_status becomes scheduled or ongoing in Get all campaigns. The workspace balance must cover the campaign (Billing); otherwise the request returns 402.

Errors

  • 400: an ID is wrong, a caller number is not in the workspace (From numbers not found: …), or the campaign has already started.
  • 402: the balance does not cover the campaign.
  • 401: X-API-KEY is missing or invalid.

Authorizations

X-API-KEY
string
header
required

Headers

X-API-KEY
string
required

(Required) Your Ringg AI API key.

Example:

"rg_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Body

application/json
agent_id
string
required

(Required) ID of the agent that will handle the calls.

Example:

"00000000-0000-4000-8000-0000000000a1"

list_id
string
required

(Required) ID of the uploaded campaign contact list.

Example:

"123e4567-e89b-12d3-a456-426614174000"

from_numbers
string[]
required

(Required) Caller numbers, as workspace number IDs from List workspace numbers (recommended) or as numbers written exactly as listed there. Each retry dials the next number in the list. A number not in the workspace returns 400.

Example:

Response

Campaign started successfully.

status
string

Success message indicating campaign registration

Example:

"campaign registered successfully!"

has_ongoing_calls
boolean

Whether the workspace has other ongoing calls

Example:

false