Skip to main content
POST
Create Campaign (v2)
Create a campaign without specifying an agent ID. This allows you to use different agents for different calls within the same campaign.

Quick Example

Workflow

1

Create the campaign (no agent ID required)

Response:
2

Add calls with any agent

Use different agents for each call:
3

Monitor in dashboard

Track campaign performance at /dashboard/batch-calls/{batch_id}

When to Use v2

Use Campaign v2 when:
  • ✅ You want to use different agents in the same campaign
  • ✅ You don’t have the agent ID ready when creating the campaign
  • ✅ You need maximum flexibility

v1 vs v2 Comparison

💡 Recommended: Use v2 for new integrations unless you specifically need all calls to share the same agent.

Response

Success (200 OK)

Save the batch_id - you’ll need it to add calls to this campaign!

Tips

Maximum flexibility: v2 gives you the freedom to assign any agent to any call within the campaign, making it ideal for complex workflows.
No upfront planning: Create campaigns first, assign agents later based on your business logic or customer needs.

Authorizations

X-API-KEY
string
header
required

Body

application/json
name
string
required

Campaign name for identification and organization

Required string length: 1 - 200
Example:

"Inspection Campaign"

Response

Campaign created successfully

batch_id
string

Unique identifier for the created campaign

Example:

"68433b7b0dee98e59245ebab"

message
string
Example:

"Campaign created successfully"

status
string
Example:

"success"