What this request does
The single email verification endpoint is designed for real-time server-side workflows such as registration checks, lead qualification, CRM enrichment and support tooling. Send one address as JSON and ListCleaner returns a normalized status without sending any message to the submitted mailbox.
The verification workflow first uses ListCleaner's internal syntax, domain, disposable-domain, blacklist and MX checks. When those checks do not produce a conclusive result, the configured external verification step is used. A completed verification consumes one credit; infrastructure or provider failures are returned as retryable errors and are documented as refunded.
How to use /verify_email
Send exactly one email value in an application/json request.
Use a unique key when your application may retry after a timeout or interrupted connection.
Read the final status from the synchronous response and apply your product's acceptance policy.
Headers, parameters and fields
| Name | Location | Required | Description |
|---|---|---|---|
X-User-Email | Header | Yes | Email address belonging to the ListCleaner API account. |
X-Api-Key | Header | Yes | Secret API key for the authenticated ListCleaner account. |
Idempotency-Key | Header | Recommended | Unique 8–128 character retry key for safely replaying the same email request. |
email | JSON body | Yes | Email address to verify, with a maximum length of 254 characters. |
Response behavior
- HTTP 200 returns success, request_id, email and status.
- HTTP 402 means the account needs at least one available credit.
- HTTP 409 can indicate an idempotency conflict or an identical request still in progress.
- HTTP 429 indicates that the verification rate limit was reached.
- HTTP 503 reports a retryable internal or provider failure.
Execute this request
Edit the request values, then send a live authenticated request to ListCleaner. The HTTP status and duration appear in the response bar, with the actual API response body directly below. File endpoints provide a download link instead of printing binary data.
The live API response will appear here.
Code examples in 10 languages
After credentials are entered above, every example includes the actual account email and API key so the copied request can run immediately. Clear the credentials to return to placeholders.
Use cases and best practices
Common use cases
- Validate an address before creating a customer account.
- Check a lead before adding it to a CRM workflow.
- Verify an address from an internal support or sales tool.
- Prevent repeated checks during request retries with idempotency.
Recommended implementation practices
- Call the endpoint from a trusted backend.
- Treat status as a validation result, not as permission to send unsolicited email.
- Generate a fresh idempotency key for each logical verification.
- Log request_id for support and operational tracing without logging the API key.
Verify a single email address questions
Answers to common implementation, security and response-handling questions for this specific request.
Does single email verification send an email?
No. The API returns the verification status directly and does not send a message to the submitted address.
How quickly is the result returned?
The endpoint is synchronous. Internal matches can return quickly, while an external verification step can take longer.
How do retries avoid a second charge?
Reuse the same email and Idempotency-Key for a retry of the same logical request. ListCleaner can replay the stored result.
What should I do with a 503 response?
Treat it as retryable, retain the same idempotency key and retry with backoff according to your application's reliability policy.