Skip to main content
This guide uses synthetic numbers and placeholder credentials. Replace them only inside your own controlled backend or terminal.

Prerequisites

  • An active DNC LATAM organization.
  • A country entitlement for mx or ar.
  • A live API key created in the DNC LATAM dashboard.
  • A secure server-side environment. Do not call the API from browser code.
1

Store the API key securely

Keep the key in your secret manager or a local environment variable. Never commit it, paste it into AI chat, or expose it to a browser.
2

Generate an idempotency key

Create one random UUID for this logical request. Reuse it only if you retry the exact same country and phone array.
3

Submit a synthetic batch

The example deliberately contains one invalid value so the complete response shape is visible.
4

Interpret the response

A successful request returns HTTP 200:
summary.total_checked includes every submitted input, including duplicates and invalid values.
safe_numbers_to_call means that the number was not found in the selected DNC registry at the time of this check. It does not prove consent or compliance with every other calling rule.
Example phone numbers are illustrative. Their sample classification explains the response format and is not a statement about the live registry.

Verify zero data retention

Every API response includes:
Customer phone numbers exist only in request memory. DNC LATAM persists aggregate usage counts, not the request body, phone numbers, or response.

Next steps

Authentication

Store and send Bearer API keys safely.

Idempotency

Implement exact retries without double-counting usage.

Error handling

Handle quotas, rate limits, conflicts, and temporary capacity.

Response dictionary

Review field-by-field semantics and invariants.