Skip to content
VerifyEmailAPI

Check now

POST /v1/blacklist/targets/{id}/check

Runs the check immediately rather than waiting for next_check_at, and returns the target as the check left it alongside the check itself — so confirming a delisting is one request, not two.

Terminal window
curl -X POST https://api.tryverifyemail.com/v1/blacklist/targets/{id}/check \
  -H "Authorization: Bearer sk_your_api_key"

Response

Section titled “Response”
{
  "target": {
    "id": "665f1c2a9b4e7d0012ab34cd",
    "status": "clean",
    "listed_on": [],
    "last_checked_at": "2026-08-21T11:30:02.000Z",
    "next_check_at": "2026-08-21T17:30:02.000Z"
  },
  "check": {
    "id": "665f1c2a9b4e7d0012abcdef",
    "target_id": "665f1c2a9b4e7d0012ab34cd",
    "checked_at": "2026-08-21T11:30:02.000Z",
    "listed": false,
    "listed_on": [],
    "failed_on": ["spamhaus_zen"]
  }
}

failed_on lists the providers that supplied no evidence in either direction on this check. They are reported rather than hidden: a list that keeps appearing there is an operational problem, not a clean result.

See also

Section titled “See also”