ListClean
DATA · DATA & ANALYTICS
Email list verification, its results, CSV uploads, and remaining credits on their own key.
Connect ListClean with Fabriq Developer
Your user pastes their ListClean credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting ListClean in practice
ListClean’s verdicts are `clean`, `dirty`, `unknown` and `error` rather than the valid/invalid wording its marketing pages use, and a failure still arrives as HTTP 200 with `success: 0` and an `error_code` in the body — so error handling that reads only the status code files failures as results. Batch verification takes at most 3,000 addresses per call, and results come back per list ID and per type, so a full result set is three downloads.
Scopes that draw scrutiny
X-Auth-TokenThe single API key, sent as a header. There are no scopes: the same token verifies addresses, reads uploaded lists and downloads results.X-Auth-Token as a query parameterThe CSV download endpoints also accept the token in the query string, which puts the credential into the URL and therefore into logs and browser history.
Rate limits
- Batch verification accepts a maximum of 3,000 email addresses per request.
- ListClean advertises a processing capacity of 500,000 verifications per hour and a sub-2-second average response on the single-address endpoint.
Worth knowing
- A 200 response can still be a failure: the body carries `success` as 0 or 1 plus an `error_code`, so both have to be checked on every call.
- The status enum is clean / dirty / unknown / error, and downloads are fetched per type — /downloads/{list_id}/clean, /dirty and /unknown — so reassembling a verified list means three requests plus bookkeeping.
- The published reference is a Swagger 2.0 document titled "Listclean API (Beta)" at version 0.1.0, and the /v1 root replies "Welcome to Listclean APIs (api.listclean.xyz) SANDBOX(0)" — sandbox versus live is something the response tells you rather than a separate host.
- Batch verification is asynchronous: the POST returns a list_id and the results have to be polled or downloaded separately, so a single-shot integration will find nothing to read.
Checked against Listclean API reference (2026-09-29), Email verification API (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put ListClean behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.