Skip to Content
SendlySendly
API ReferenceCampaigns

Retry a campaign's failed sends

POST
/api/v1/campaigns/{id}/retry-failed

Re-drive only the recipients whose send failed, through the same pipeline the campaign used. Nobody who was already mailed is mailed again: each ledger row is claimed before it is touched, and a row whose email was created before the failure was recorded is re-queued rather than re-sent.

The retry runs in the background, so this returns as soon as it is queued, with the number of rows it was queued for. Takes no request body.

Only a SENT campaign can be retried: a SENDING or PAUSED one still has its own send in progress against the same ledger, and a CANCELLED one was stopped deliberately.

Requires the campaigns:write scope — Create, edit, and organize your campaigns.

headerAuthorizationBearer <API Key>

API key authentication. Use a sk_* (FULL) or pk_* (SENDING_ONLY) key as the bearer token. Public keys (pk_*) are restricted to the email-send endpoints and the self-serve list subscribe/unsubscribe pair; every other endpoint — event tracking included — answers 403 for them. In scope terms (used by /api/v1/* operations): FULL keys hold every scope; SENDING_ONLY keys hold only emails:send.

id*string

Resource id.

Formatuuid

Response Body

The retry was queued

application/json
  1. response

Acknowledgement that a retry of a campaign's failed sends began.

id*string
Formatuuid
queued*integer

How many FAILED rows the retry walk was started for, counted when it was queued.

Example Request
curl -X POST 'https://api.sendly.now/api/v1/campaigns/497f6eca-6276-4993-bfeb-53cbbbba6f08/retry-failed'
Example Response
{  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",  "queued": 0}