What this request does
Download the non-deliverable result set and its validation outcomes from a completed ListCleaner job. The download endpoint returns a generated result file rather than a JSON document, so client code should save the response bytes or stream them to storage.
A download belongs to the authenticated account and is addressed by the UID returned during upload. Request the file only after the status endpoint reports that cleaning is complete; a result that is not ready can return a not-found or not-ready response.
How to use /download_list
Retrieve the list status and verify that processing has finished.
Call the download endpoint with the UID and export_type=bad.
Write the response bytes to a file and preserve the filename or content-disposition metadata used by your application.
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. |
uid | Query | Yes | Unique identifier returned when the list was uploaded. |
export_type | Query | Yes | Use bad for this result set. |
Response behavior
- HTTP 200 returns the generated result file.
- The response is binary/file content, not a JSON status object.
- HTTP 404 can mean that the UID is unknown, unauthorized or the export is not ready.
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
- Import cleaned records into a CRM or email platform.
- Archive validation results alongside the original source file.
- Feed a filtered result into an automated campaign workflow.
Recommended implementation practices
- Save the response as bytes rather than parsing it as JSON.
- Check the job status before requesting a download.
- Keep the UID scoped to the authenticated customer.
- Handle 404 responses as a job/readiness condition as well as a missing-resource condition.
Download non-deliverable email results questions
Answers to common implementation, security and response-handling questions for this specific request.
What does export_type=bad contain?
Download the non-deliverable result set and its validation outcomes from a completed ListCleaner job.
Why does the download example save a file?
The endpoint returns file content. The language examples therefore write the response to cleaned-list.csv instead of printing JSON.
Can I download results before cleaning finishes?
No. Check the list status first and request the export only after the job is complete.
Why can the endpoint return 404?
The UID may not exist for the authenticated account, or the requested result file may not be ready yet.