And honour everyone who does not. Scrub your calling list against the do-not-contact preferences of verified number owners — before you dial. Paste a list here, or call the API for your whole database. Built for do-not-call, not against you.
POST /api/scrub
X-API-Key: <your key>
{ "numbers": ["+16285550177",
"+12135559988"],
"channel": "voice" }
→ { "summary": { "suppress": 1,
"no_match": 1,
"unknown": 0 },
"results": [ ... ] }Full API docs →Most people ignore calls from numbers they do not recognise, and a list full of people who never wanted to hear from you is wasted effort on both sides. We believe a phone number is a person's digital identity — something they should be proud to own, not a target to be dialled against their wishes. So we built scrubbing to do one thing well: help you reach the people who genuinely want your call, and quietly step around everyone who has asked to be left alone. It is the anti-data-broker approach — we make outreach more trusted without selling anyone's private details.
One honest caveat: this is a compliance aid, never a legal guarantee. Scrubbing against do-not-contact preferences does not, on its own, make you compliant with the TCPA, the Singapore PDPA and its Do Not Call provisions, the GDPR, or any other law. You remain responsible for your own lawful basis and consent, for checking every applicable do-not-call registry, and for re-scrubbing regularly so your suppression list stays current. Read the full terms at our terms before you build a campaign on it.
You submit a list of phone numbers and a contact channel (voice, SMS or WhatsApp). For each number we return SUPPRESS (the verified owner has asked not to be contacted on that channel — remove them), NO_MATCH (no suppression preference is on record), or UNKNOWN (the number could not be resolved). You use that to leave alone everyone who has asked to be, and proceed on the rest under your own consent obligations. NO_MATCH is not consent.
Anyone who verifies their number with numbers.online controls their own marketing-call preference. Consent comes first by default: a verified number is treated as do-not-contact until its owner chooses to opt in.
Yes. POST { "numbers": ["+1...", ...] } with your API key to /api/scrub, up to 1,000 numbers per request, and receive a per-number SUPPRESS / NO_MATCH / UNKNOWN status plus a summary. The on-page tool uses a shared, rate-limited demo key; real volume needs your own key. Re-scrub regularly so you keep honouring fresh opt-outs.
No. Scrubbing against do-not-contact preferences is a compliance aid, not a legal guarantee. You remain responsible for your own consent and for checking the official do-not-call registries and the laws in your jurisdiction. Treat our results as one honest signal among several.