Validate every address on a list
Start a background run over every contact on the list and answer immediately with the run. Poll GET /api/v1/validation-runs/{id} for progress and read the verdicts from its /results page.
This VALIDATES and changes nothing: no membership is unsubscribed, no contact is deleted. What to do about an undeliverable address is your decision, and a run that acted on its own findings would be acting on a DNS lookup that can also answer unknown.
A second run while one is already in flight for the same list is refused with 409 rather than queued: two runs would bill the same addresses twice.
Requires the validation:write scope — Check whether email addresses can receive mail — this is billed per address.
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.
uuidThe run, accepted and queued
application/json- response
One bulk validation run over a list.
id*stringlist_id*string|nullstatus*string"pending""running""completed""failed"processed_count*integerAddresses checked so far. There is deliberately no total: a list changes size while a run walks it, so a denominator captured up front would be wrong by the time you read it.
deliverable_count*integerundeliverable_count*integerrisky_count*integerstarted_at*|date-timecompleted_at*|date-timefailure_reason*|Set only on failed. Prose for an operator; never parse it.
created_at*stringdate-timecurl -X POST 'https://api.sendly.now/api/v1/lists/497f6eca-6276-4993-bfeb-53cbbbba6f08/validation-runs'{ "id": "string", "list_id": "string", "status": "pending", "processed_count": 0, "deliverable_count": 0, "undeliverable_count": 0, "risky_count": 0, "started_at": "2019-08-24T14:15:22Z", "completed_at": "2019-08-24T14:15:22Z", "failure_reason": "string", "created_at": "2019-08-24T14:15:22Z"}