What this request does
The single-job view uses the show-lists endpoint with a UID query parameter. It is the preferred request for a progress screen, webhook replacement or backend poller that already knows which uploaded list it is tracking.
The response exposes the same list metadata used in the dashboard, including record counts and current processing state. Once the job reaches a completed state, use the UID with one of the download endpoints to obtain all, deliverable or non-deliverable results.
How to use /show_lists
Persist the identifier returned when the list was accepted.
Send the UID as the show_lists query parameter.
Continue measured polling while active, or enable downloads after completion.
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 list identifier returned by the upload endpoint. |
Response behavior
- HTTP 200 returns the matching job data.
- HTTP 404 means no matching list is available to the authenticated account.
- Status and last update fields describe progress and freshness.
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
- Drive a live progress view for one upload.
- Resume monitoring after a worker restart.
- Decide when download links should become active.
Recommended implementation practices
- Use a moderate polling interval such as the interval already used by your dashboard.
- Stop polling final states.
- Do not guess or enumerate UIDs.
- Handle 404 without exposing account details.
Show one email cleaning job questions
Answers to common implementation, security and response-handling questions for this specific request.
Where does the UID come from?
It is returned by POST /upload_list when a cleaning job is successfully created.
How often should I poll?
Use a measured interval appropriate for the user experience and stop when a final state is returned.
What does a 404 response mean?
The UID may be invalid, removed or unavailable to the authenticated account.
Can this request download the results?
No. It reports job information. Use /download_list after the job is complete.