Integrate list cleaning and real-time email verification into your application using the ListCleaner REST API.
Enter your ListCleaner account email and API key once. They are kept only in this tab's temporary session, applied to every documentation request page, and discarded when the tab closes.
POST /verify_emailValidate an individual email address and receive the normalized result in the same HTTP response. This is suited to signups, lead forms, CRM enrichment and server-side validation workflows.
POST /upload_listUpload a structured email list, select its email column and use the returned UID to follow processing. CSV, XLSX, TSV and delimited TXT examples are available for every supported programming language.
GET /show_listsList all jobs, inspect one job, download complete or filtered results, and remove a retained list when it is no longer required.
GET /get_creditsRetrieve the current credit balance for the authenticated ListCleaner account before submitting validation work.
Choose an operation and programming language. After you enter tab credentials, each example includes the actual account email and API key so the copied request is ready to run.
Expand an operation to inspect its request fields, response codes and data models, or use Try it out with the temporary tab credentials entered above.
Use ListCleaner to verify an individual address during a signup or CRM workflow, or upload an entire customer list for asynchronous cleaning. The REST API gives your application a consistent way to submit data, monitor cleaning jobs, inspect results and download processed files.
Call POST /verify_email for a synchronous status response. ListCleaner checks its internal data and validation layers before using the configured external verification step when needed.
Upload CSV, XLSX, TSV or delimited TXT files, identify the email column and track processing with the returned list UID. XLSX workbooks must contain one worksheet.
Inspect list status through the API and download all, deliverable or non-deliverable results for use in your CRM, email platform or internal data pipeline.
Authenticate requests with your account email and API key:
X-User-Email: you@example.comX-Api-Key: YOUR_API_KEYSend credentials only over HTTPS and keep the API key on your server rather than in public browser code.
Quick answers for developers integrating email verification and bulk list cleaning.
POST /verify_email checks one address through ListCleaner's internal validation data and verification workflow, then returns its status in the same API response. It is designed for server-side signup, CRM and lead-validation workflows.
Upload a CSV, XLSX, TSV or delimited TXT file to POST /upload_list, identify the email column and retain the returned UID. Use that UID to monitor the job and download the required results.
The list validation API accepts CSV, XLSX, TSV and delimited TXT files. The current endpoint limit is 100 MB and up to 1,000,000 data rows per upload.
No. An XLSX upload must contain exactly one worksheet. Split a multi-sheet workbook into separate files and submit each worksheet as its own cleaning job.
Send your account email in X-User-Email and your API key in X-Api-Key over HTTPS. The credential form above applies both values to every Try it out request for the current page only.
Send a unique Idempotency-Key with POST /verify_email. Repeating the same email and key replays the stored result instead of creating a second charge.
No. No message is sent to the submitted address. The validation result is returned directly in the API response as quickly as the verification workflow allows.
Call GET /show_lists to retrieve all retained jobs, or add a list UID to retrieve one specific job and its current processing status.
Use export_type=all for every processed row, export_type=ok for deliverable results, or export_type=bad for non-deliverable results.
Call GET /get_credits with the same account email and API key. The response returns the current balance for the authenticated account.
No. Production requests should come from a trusted backend, with the API key stored in a protected secret or environment variable. This documentation keeps entered credentials only in page memory and never inserts them into displayed examples.