Skip to main content

Create or replace an audience

Takes the csvAssetId returned by Upload recipients, reads the file, and stores the list.

Request body

Response

Rows whose recipient cannot be read are dropped and counted in rejectedCount, with the reasons in error. The request fails only when nothing survives.
Check variables against the campaign you intend to send. These are the column names Connectly stored, and they must match the campaign’s placeholders exactly.

Replacing

Pass audienceId to overwrite that audience’s recipients with a newly uploaded CSV. The id and any sends already created from it are unchanged.
An audienceId that names nothing returns 404 β€” it is not created for you.

Get an audience

downloadUrl is a time-limited link to the stored CSV, valid for one hour. Request the audience again for a fresh link. The recipients are never returned inline β€” a million-recipient list is well over 100MB. The stored CSV is not byte-for-byte your upload. The recipient column is renamed external_id, each recipient is in canonical form (E.164, or bsuid: followed by the BSUID), and the columns are sorted by name.

Delete an audience

Sends already created from the audience are unaffected; each keeps its own copy of the recipients.

Errors

Next step

Send to an audience

Send a published campaign to the audience, now or on a schedule.