Do-not-call API: what the national registry offers
The FTC's own pages describe no API for the National Do Not Call Registry. A seller opens an account, downloads the numbers for its area codes as full or change lists, or searches up to 10 numbers at a time on the web, and refreshes at least every 31 days. DNC lookup APIs are services built on that data. Your own do-not-call list, people who asked you to stop, is separate.
Checked 2026-11-15 against the sources linked at the end.
How sellers get registry data
- Full list download: every registered number in the area codes you pay for.
- Change list: numbers added to or deleted from the registry since a date.
- Interactive search: an area code and up to 10 numbers at a time, and 100 numbers in one web session.
- Downloads are allowed once in any 24-hour period, and your lists must be synchronized with the registry at least every 31 days.
What it costs
Data for up to five area codes is free. From October 1, 2026 the FTC lists $85 a year for each area code after five, up to a maximum of $23,425 a year. Access is by the seller's subscription account number (SAN); a telemarketer or service provider calling for that seller can use the seller's SAN without paying again, but may not use one seller's registry data to call for another.
Two lists, two jobs
- The national registry: people who don't want telemarketing calls from anyone. You scrub against it, or a scrub vendor does with your SAN.
- Your own list: people who told you to stop. The Telemarketing Sales Rule requires honoring those requests even for numbers not on the national registry.
- State lists and calling hours add to both. dialerseat.com keeps a state-by-state table of calling rules.
The safe harbor
The TSR forgives an inadvertent call to a registered number only when the seller meets each of its conditions, among them: written procedures, trained staff, its own do-not-call list, a process that keeps registered numbers from being called, access to the registry no more than 31 days before the call with records of it, and a call that was an error. A scrub that is 40 days old is outside it.
What DialerSeat's DNC API does
POST /v1/dnc suppresses a number on every campaign on your platform, GET /v1/dnc lists the suppressed numbers with how each got there, and DELETE /v1/dnc/{phone} removes one added by mistake. A disposition mapped to the do-not-call outcome adds the number automatically. This is your own list. Scrubbing against the national registry is not automated: it stays with you or your scrub vendor.
Related: calling rules by US state, call disposition codes list, answering machine detection and dispositions in the docs.
Sources
- FTC: Q&A for telemarketers and sellers about the DNC provisions in the TSR
- National Do Not Call Registry: telemarketer access
- Telemarketing Sales Rule, 16 CFR Part 310 (eCFR)
More: the developer FAQ, the comparisons, Answering machine detection (AMD), explained for developers, Salesforce Open CTI retirement: what it means, Webhook signature verification failed? Find the cause, Moving from VICIdial's API to an embedded dialer, A click-to-call button in your CRM, Your own UI on the dialer, with DialerSeat.connect, A live status board for managers, or the quickstart, free in sandbox mode.