ListCleanerDeveloper platform
POST/delete_list?uid=YOUR_LIST_UID

Delete an email cleaning job

Remove a retained list-cleaning job and its associated accessible resources from the authenticated account.

Destructive actionUID queryAuthenticated owner
Temporary tab credentials

Authenticate once for every guide

Your email and API key remain in this tab's session storage, work across all request pages, and disappear when the tab closes.

Credentials have not been entered.

Overview

What this request does

The delete-list request is the lifecycle endpoint for removing a list that is no longer required. It uses POST with the list UID as a query parameter and applies the same account authentication as the rest of the API.

Deletion should be presented as an intentional action in customer-facing software. Confirm that your application no longer needs the job or its exports, capture any required audit metadata and handle missing jobs without assuming they belong to another account.

Implementation workflow

How to use /delete_list

Identify the exact UID

Resolve the target through your own stored job record or the list-status endpoint.

Confirm the intent

Require an explicit product-level confirmation before the destructive API call.

Process the response

Remove the job from local views after success and handle missing UIDs safely.

Request contract

Headers, parameters and fields

NameLocationRequiredDescription
X-User-EmailHeaderYesEmail address belonging to the ListCleaner API account.
X-Api-KeyHeaderYesSecret API key for the authenticated ListCleaner account.
uidQueryYesExact UID of the list to delete.

Response behavior

  • HTTP 200 confirms successful deletion.
  • HTTP 400 reports a missing UID or invalid request.
  • HTTP 404 means the list could not be found for the authenticated account.
Interactive API console

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.

Your saved tab credentials are added to the request headers and never printed in the response panel.
This performs a real API operation and may use credits or change account data.
Ready-to-run examples

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.

POST /delete_list?uid=YOUR_LIST_UIDContent type:
PHP
Integration guidance

Use cases and best practices

Common use cases

  • Remove test uploads from an account.
  • Implement a customer-controlled retention workflow.
  • Clean up completed jobs after downstream results have been archived.

Recommended implementation practices

  • Show the filename/reference and UID before confirmation.
  • Do not retry blindly after an uncertain network failure; check whether the job still exists.
  • Record deletion in your own audit trail when required.
  • Never accept a UID from an untrusted user without an authorization check in your application.
Focused FAQ

Delete an email cleaning job questions

Answers to common implementation, security and response-handling questions for this specific request.

Can a deleted list be downloaded later?

Treat deletion as permanent for the API workflow. Download or archive required results before deleting the job.

Why does deletion use POST?

This API defines deletion as an authenticated POST action with the UID supplied as a query parameter.

What if the request times out?

Check the list status before retrying so your application can distinguish a completed deletion from a transient failure.

Can one account delete another account's list?

The API scopes requests to the authenticated account; applications should also enforce their own user authorization before calling it.