DNC API vs CSV: Which Scrub Path to Use
DNC LATAM · Compliance guides
DNC LATAM has two customer surfaces: a public REST API (country field plus a phone array) and a CSV scrub in the authenticated panel. Both check official Mexico REPEP (PROFECO), Argentina Registro Nacional No Llame (AAIP), and Colombia RNE (CRC). Both return a determination and a dated screening record. They are not the same integration.
Pick the surface that matches how numbers reach the dialer. Do not pick based on which registry you need. The country field does that. Contract: DNC API. Workflow: how to scrub a calling list.
What stays the same
- Official government source for the selected country. Nothing scraped.
- Independent monthly allowance per country SKU.
- Prohibited, safe, and invalid classifications.
- Dated screening record: country, registry context, counts. No phones.
- Mexico, Argentina, and Colombia live today. Immediate activation after payment.
What changes
| REST API | Panel CSV | |
|---|---|---|
| Who uses it | Engineering, dialer, CPaaS, CRM | Ops, compliance, campaign managers |
| Where it lives | Public contract, docs.dnclatam.com | Authenticated panel only |
| Shape |
POST with country and phones
|
File upload of rows |
| Best fit | List load, scheduled re-check, dial-time gate | One-shot campaign files |
| Gap | Needs an integration | Cannot see numbers added after export |
| Retention | v1 zero-retention; v2 bounded | Bounded encrypted lifecycle |
CSV is not "the batch API." If a platform needs a programmatic batch, that is still the public API (synchronous v1 or durable v2). Domain language: a CSV scrub is panel-only. A scrub batch is one API request resolved as one unit.
When CSV is enough
Use the panel when a human already exports the campaign, the list is stable until launch, and nobody can click-to-call leftovers in the CRM. Typical: a weekly insurance or home-services file, a BPO receiving a locked client list, a first Mexico test before anyone writes code.
Stop using CSV as the only control when reps add leads all day, a predictive queue restocks after the file, or you run three countries from one platform. Those cases need batch plus realtime gates.
When the API is the product
Wire the API when the check must happen without a person. Send
mx, ar, or co. Keep the rest of
the request. Dialer walkthrough:
API integration for dialers and CRMs.
Platforms:
DNC for dialer platforms,
DNC for CPaaS,
for platforms (OEM).
Pricing does not change with the surface
You buy a country, not "API vs CSV." From $500/month at 10,000 checks per country. Tiers step through 25k, 50k, 100k, 250k, 500k, and 1,000,000. Annual billing charges ten months for twelve. No all-countries plan. Details: DNC scrubbing cost, live configurator.
Privacy: zero-retention DNC scrubbing. Coming end of September: Spain, Australia, and Singapore. Not live API or CSV countries today.
Questions, answered
Is panel CSV the same as the public API? +
Same official registries and the same dated screening record. Different surface. The REST API is the public contract for corporate integrations. CSV scrub exists only in the authenticated panel. It is not a public batch API.
Do both paths consume quota? +
Yes. Array entries through the API and data rows through panel CSV both count against that country's monthly allowance. Invalid and duplicate inputs count. Unused quota expires at the end of the window.
Which path has zero-retention? +
Synchronous v1 is zero-retention: no source list or per-number result kept after the request, advertised with x-retention: zero and Cache-Control: no-store. Durable v2 and CSV scrub have their own explicitly bounded encrypted lifecycles.
Can I start on CSV and move to the API? +
Yes. Buy the country SKU once. Ops can upload while engineering wires country mx, ar, or co. You do not buy a second product to switch surfaces.
When should I buy? +
When you need official REPEP, No Llame, or RNE checks. Pick the surface that matches how you launch campaigns. From $500/month per country at 10,000 checks.