Campaigns
Send Campaigns
Trigger one or more campaign flows to multiple recipients with variables, versioning, and per-entry status reporting 📩
POST
Send Campaigns
Endpoint
Request body
entries array (required)
Each object in entries represents one recipient. You can mix entries for different campaigns in the same request.
options object (optional)
Examples
Minimal entry — no variables
Minimal entry — no variables
The smallest valid entry. Use this for campaigns that have no variable placeholders.
Entry with variables
Entry with variables
Variables are defined in the campaign flow in the Connectly UI. Pass the same key names here.
Multiple campaigns in one request
Multiple campaigns in one request
Connectly creates a separate sendout for each unique
campaignName + campaignVersion combination. This request produces three sendouts: campaign_A at v1.0, campaign_A at its latest active version, and campaign_B at v1.0.Allow duplicate sends
Allow duplicate sends
By default, the API prevents sending the same campaign to the same customer twice. Override with
allow_multiple for use cases like recurring alerts.Response
The API always returns HTTP200 with a data array. Each element corresponds to a unique campaignName + campaignVersion sendout generated by the request.
If you call the API again for the same campaign and recipient group,
status returns "updated" rather than "created" — no duplicate sendout is created.Error responses
Entry-level errors appear inside thedata array with status: "error" — they don’t cause the whole request to fail. HTTP-level errors indicate request-wide failures.
Campaign not found
Campaign not found
Campaign version not found
Campaign version not found
Missing or invalid variables
Missing or invalid variables
Triggered when required flow variables are absent or the entry payload is otherwise invalid.
Rate limiting
This endpoint is limited to 200 requests per second. Exceeding this returns HTTP429 Too Many Requests. Use exponential backoff in your client if you expect high-volume sendouts.