Skip to main content
POST
Create campaign

Authorizations

Authorization
string
header
required

Workspace-scoped token sent in the Authorization header as Bearer . Access depends on the credential's allowed operations, read or write scope, and workspace subscription. Use an API key issued in the tracker for Public API v1. MCP uses separate OAuth credentials.

Body

application/json

Omitted cost uses none. Omitted tracking uses redirect and domainId null. Use a rotator set to Global or the campaign country.

name
string
required
Required string length: 1 - 160
trafficSourceId
string
required
destination
object
required

An active rotator in this workspace with an enabled default path. Redirect paths need an enabled offer with positive weight. Hosted landings on enabled redirect paths must be published.

country
string
default:ZZ

Supported ISO 3166-1 alpha-2 country code, case-insensitive and trimmed. ZZ, Global, and an empty string normalize to ZZ (Global). This controls asset compatibility, not visitor filtering.

cost
object
tracking
object

Response

Campaign created

ok
enum<boolean>
required
Available options:
true
data
object
required