Integrate DNC LATAM with Aircall

DNC LATAM · Compliance guides

The pattern is the same as any contact center: your backend calls the DNC LATAM API before Aircall connects. Aircall is the phone system. Official Mexico REPEP (PROFECO), Argentina Registro Nacional No Llame (AAIP), and Colombia RNE (CRC) are the destination lists. A US National DNC wash sitting next to Aircall does not cover +52, +54, or +57.

Contact-center persona: DNC for contact centers. Nearshore floors: DNC for nearshore call centers. Twilio sibling: integrate with Twilio.

Where the check belongs

1. Agent or automation is about to place an outbound call.
2. Your server reads the destination and maps it to mx, ar, or co.
3. You POST to DNC LATAM. Server-side only. Bearer key. Never in the browser.
4. Prohibited: do not create or connect the Aircall outbound call.
5. Safe on that registry: continue your existing Aircall flow.
6. Invalid: stop and fix the number. Do not "try the call anyway."

Click-to-call is the hole a morning CSV cannot close. If a lead can be dialed the minute it hits the CRM, you need a realtime one-number array as well as a batch at list load. Batch vs realtime.

Request shape (public docs)

Same contract as docs.dnclatam.com. No Aircall-specific fields. Every POST /v1/scrub requires Idempotency-Key. Generate a new opaque UUID per logical batch. Reuse it only for an exact retry of the same country and phones array. Absent header: 400 missing_idempotency_key.

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

{
  "country": "ar",
  "phones": ["+54 11 1234 5678"]
}

One number at dial time. A larger phones array at campaign import. v1 up to 10,000 inputs. Durable v2 for larger jobs. We will not invent Aircall webhook names or Smartflow step IDs here. Put the POST on the server hop you already own.

Response shape (public docs)

{
  "prohibited_numbers_to_call": [],
  "safe_numbers_to_call": ["+54 11 1234 5678"],
  "invalid_numbers": [],
  "summary": {
    "total_checked": 1,
    "prohibited_numbers": 0,
    "safe_numbers": 1,
    "invalid_numbers": 0
  },
  "scrub_record": {
    "record_id": "00000000-0000-4000-8000-000000000002",
    "record_version": "1",
    "surface": "api_v1",
    "request_id": "req_bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
    "organization": { "name": "Your company" },
    "country": "ar",
    "registry": {
      "authority": "AAIP",
      "mode": "snapshot"
    },
    "status": "succeeded",
    "counts": {
      "submitted": 1,
      "prohibited": 0,
      "safe": 1,
      "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"
  }
}

Gate on prohibited_numbers_to_call. Persist scrub_record next to the ticket or campaign. That object is the dated screening record: counts and metadata, no phones. v1 does not keep it. Successful v1 responses document x-retention: zero.

Empty prohibited in the sample above is format, not a promise about that line on No Llame. Example numbers are illustrative. Dictionary: responses.

What Aircall teams still own

• US National DNC / TCPA only for numbers you have resolved as US. +1 is NANP, not "United States."
• Calling hours and scripts. A registry hit is not a hours engine.
• Direct opt-outs the moment the person says stop.
• Client evidence if you are a BPO. The screening record is the artifact.

BPO path: DNC for BPOs. Records: screening records. Generic predictive / power dialer: integrate with a dialer. From $500/month per country at 10,000 checks. Estudio Miotti. Not a US TCPA scrubber. API. Call center compliance.