Documentation
Two tracks, same product. Use the web app to upload a phone list and pull back cleaned CSV exports in a minute. Or skip the UI and call the REST API from your own code, with the same validation engine, the same pricing, and signed webhooks for batch events.
Platform
For teams who want to drop a CSV in a browser and walk away. The guides below cover the full path from your first signup to a clean SMS-ready list, what the input file needs to look like, which rows we charge for, how to read every column we add, and the questions customers ask us in the first week. Read Quickstart first if you have five minutes.
Quickstart
Sign up, buy credits, upload a phone list, download a cleaned list, in five minutes.
CSV format
What valid input files look like, what fields you get back, and which export to download.
Batches
What a batch is, who uses it, what you give it, what you get back, and the filtered download presets.
Pricing
Prepaid credit packs, what counts as a debit, and what's free.
FAQ
Common questions about providers, data handling, refunds, and limits.
API
For developers wiring Phone List Cleaner into a product, a worker queue, or a nightly job. The /v1 API covers single-number lookup, 100-per-call bulk lookup, account snapshots, and batch status/result URLs for dashboard-created batches. Bearer-token auth uses scoped keys, Idempotency-Keysupport makes retries safe, and HMAC-signed webhooks include redelivery from the dashboard. The reference is contract-style, the explorer lets you fire requests without writing code.
API reference
Endpoint contracts, auth, scopes, idempotency, errors. Single lookup and bulk.
Try the API
Browser-based explorer, paste your key, send a request, see the response live.
Webhooks
Signing, retry behaviour, redelivery, auto-disable, and event payload schemas.
Limits and quotas
Every cap, timeout, and tier the API enforces, and what happens when each is exceeded.
Need help?
Email hello@phonelistcleaner.com for anything not covered here. Bug reports, feature requests, and weird edge-case CSVs are all genuinely welcome, real customer questions are the fastest way these docs get better.