Skip to main content
POST
Send Campaigns

Endpoint

Campaigns must be published in the Connectly Flow Builder before you call this endpoint. Sending to an unpublished campaign returns a 409 error.

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

The smallest valid entry. Use this for campaigns that have no variable placeholders.
Variables are defined in the campaign flow in the Connectly UI. Pass the same key names here.
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.
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 HTTP 200 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.
Success response

Error responses

Entry-level errors appear inside the data array with status: "error" — they don’t cause the whole request to fail. HTTP-level errors indicate request-wide failures.
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 HTTP 429 Too Many Requests. Use exponential backoff in your client if you expect high-volume sendouts.