Integrate DNC LATAM with a Dialer

DNC LATAM · Compliance guides

A predictive or power dialer should call the DNC LATAM API before a LATAM number becomes dialable and again before connect. Official lists are Mexico REPEP (PROFECO), Argentina Registro Nacional No Llame (AAIP), and Colombia RNE (CRC). A US National DNC file will mark those numbers clean because they were never in scope.

Platform packaging: DNC for dialer platforms. Operations split: batch vs realtime DNC checks. Blog walkthrough: dialer or CRM API guide.

Batch at list load

When a campaign CSV or CRM sync becomes dialable, send the whole country slice in one request. Do not mark the campaign ready until the result is back. Panel CSV is the no-code version of this step. The public API version is a larger phones array on the same contract.

POST https://api.dnclatam.com/v1/scrub
Authorization: Bearer $DNC_LATAM_API_KEY
Idempotency-Key: $DNC_LATAM_IDEMPOTENCY_KEY
Content-Type: application/json

{
  "country": "co",
  "phones": ["+57 300 123 4567", "300 765 4321", "abc"]
}

Every POST /v1/scrub requires Idempotency-Key. Generate a new opaque UUID for each logical batch. Reuse it only when retrying the exact same country and phones array. Absent header: 400 missing_idempotency_key. v1: up to 10,000 inputs, 15-second budget, one complete result or an error. Larger files: durable POST /v2/scrub as documented. We will not invent a "partial page" field. The job succeeds or fails as a unit. API reference.

Realtime at dial time

When the predictor pulls the next record, or an agent clicks Call, send a one-number array. If the API returns the number in prohibited_numbers_to_call, refuse the connect. Do not warn-and-continue. Numbers added after this morning's batch are why this hook exists.

{
  "country": "mx",
  "phones": ["+52 55 1234 5678"]
}

Response you gate on

{
  "prohibited_numbers_to_call": ["+52 55 1234 5678"],
  "safe_numbers_to_call": [],
  "invalid_numbers": [],
  "summary": {
    "total_checked": 1,
    "prohibited_numbers": 1,
    "safe_numbers": 0,
    "invalid_numbers": 0
  },
  "scrub_record": {
    "record_id": "00000000-0000-4000-8000-000000000003",
    "record_version": "1",
    "surface": "api_v1",
    "request_id": "req_cccccccccccccccccccccccccccccccc",
    "organization": { "name": "Your company" },
    "country": "mx",
    "registry": {
      "authority": "PROFECO",
      "mode": "snapshot"
    },
    "status": "succeeded",
    "counts": {
      "submitted": 1,
      "prohibited": 1,
      "safe": 0,
      "invalid": 0
    },
    "submitted_at": "2026-09-04T00:00:00.000Z",
    "completed_at": "2026-09-04T00:00:00.000Z",
    "record_issued_at": "2026-09-04T00:00:00.000Z"
  }
}

Sample classification explains the shape. It is not a live REPEP statement about that illustrative number. Persist scrub_record. v1 does not keep it. Full result classes: responses. Invalid reason codes in the public docs include empty, unparseable, wrong_country, too_short, too_long, and provider_rejected.

Schedule for lists that sit

Re-check parked leads when Mexico publishes a new 15-day REPEP release, and on a current-consult cadence for Argentina and Colombia. Cadence we will edit as site facts change: LATAM registry updates. Do not apply a 31-day US TSR habit to all three.

Country routing

Route on the resolved destination, not the campaign nickname. +52 is REPEP. +54 is No Llame. +57 is RNE. A leading +1 is NANP: United States, Canada, and Caribbean share that country code. Resolve the area code before you pick a DNC service. Send US numbers to your FTC / TCPA vendor. Do not map every +1 there. We do not sell Canada or Caribbean registry checks. DNC.com alternative, EVS7 alternative, PossibleNow vs DNC LATAM. Keep the registry name on the stored result. A boolean "DNC clean" that merges three countries hides which list fired.

Persist the screening record next to the campaign. CPaaS and contact-center copies of this hook: Twilio, Aircall. From $500/month per country at 10,000 checks. Batch and realtime share that allowance. Estudio Miotti. Not a US TCPA scrubber. API. How to scrub a calling list.

Questions, answered

Where should a predictive or power dialer call DNC LATAM? +

At list load (batch), at dial time (realtime), and on a schedule for long-lived campaigns. A CSV that ops ran last week is not enough if the predictor can pull a new lead.

Is batch a different API from realtime? +

No. The public contract is country plus a phones array. Use a large array at import. Use a one-number array at dial time. Same country quota. See docs.dnclatam.com for v1 vs durable v2.

What do we do with prohibited_numbers_to_call? +

Remove them from the dialable queue or refuse the live connect. Do not toast a warning and proceed. A log line that does not stop the call is monitoring, not a gate.

Can one toggle cover US and LATAM? +

One integration, three destination lists plus your existing US vendor. Route Mexico to REPEP, Argentina to No Llame, Colombia to RNE. Resolve the full E.164 destination first. +1 is NANP, not automatically the United States. Keep FTC National DNC on the US tool only for numbers you have resolved as US.

When should a dialer platform buy? +

When any tenant campaign can dial +52, +54, or +57. From $500/month per country at 10,000 checks. OEM if you need to resell. Estudio Miotti is the legal entity.