Skip to main content
An API Campaign ties an approved WhatsApp Message Template to a reusable, named campaign. Once created (and its status is LIVE), you trigger individual per-contact sends via the Send Campaign endpoint — passing dynamic parameter values at send time for each recipient. This two-step model (create once, send many) lets you configure the template association once and reuse it for all programmatic sends, without repeating template configuration on every API call.

Endpoint

Authentication

Path Parameters

string
required
Your Convo project ID.

Request Body

string
required
The name of an approved WhatsApp Message Template in your project. The template must have status: "APPROVED" — campaigns linked to pending or rejected templates cannot send messages.
string
required
A unique name for this campaign within your project. This is the identifier you use in all subsequent Send Campaign calls. Choose a descriptive, stable name (e.g., ShipmentAlerts_Q4_2024).

Request Example

Response

A successful request returns 200 OK with the full campaign object. The campaign is immediately LIVE and ready to accept send requests.
string
The unique identifier of this campaign.
string
The campaign name you provided.
string
Campaign type. Always "API" for campaigns created via this endpoint. Broadcast campaigns created in the dashboard have type "BROADCAST".
string
Current campaign status. Newly created API campaigns are always "LIVE".
string
The media type of the linked template (e.g., "TEXT", "IMAGE", "VIDEO").
object
Contains the full template object that this campaign is linked to, including the template body, buttons, parameters, and metadata.
string
ISO 8601 timestamp of when the campaign was created.

Error Responses