List a campaign's failed sends
The recipients this campaign did not reach, read from its per-contact send ledger. The campaign counters say how many were sent; only this says WHO was dropped and why, which is what makes retrying a decision rather than a guess.
reason comes from a fixed vocabulary, not from the underlying error text, so it is stable enough to branch on. It is null for rows recorded before reasons were captured.
Cursor-paginated like every other v1 list. Unlike them it also returns total: the retry action operates on that number, and a page that can only say has_more cannot tell you whether 3 or 30,000 sends failed.
Requires the campaigns:read scope — View your campaigns and their performance.
AuthorizationBearer <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*stringResource id.
uuidlimit?integer1 <= value <= 10020after?stringOpaque cursor from a previous response's next_cursor.
1 <= lengthFailed sends
application/json- response
Cursor-paginated list of a campaign's failed sends.
data*array<>has_more*booleannext_cursor*|Pass as after to fetch the next page. null on the last page.
total*integerEvery FAILED row on this campaign, not just this page.
curl -X GET 'https://api.sendly.now/api/v1/campaigns/497f6eca-6276-4993-bfeb-53cbbbba6f08/failures'{ "data": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "contact_id": "f245e2a3-e141-4d41-912c-b1c1f5bd5598", "email": "string", "reason": "string", "failed_at": "2019-08-24T14:15:22Z" } ], "has_more": true, "next_cursor": "string", "total": 0}