Skip to main content
Every POST /v1/scrub request requires an Idempotency-Key header.
An idempotency key identifies one logical request for the authenticated API key.

​
Rules

  • Generate a random UUID or another opaque high-entropy value.
  • Use a new key for every new logical request.
  • Reuse the key only when retrying the exact same country and phones array.
  • Preserve the original array order and values on a retry.
  • Never derive the key from phone numbers, customer IDs, email addresses, or other PII.
  • Keep the value between 1 and 255 visible ASCII characters with no spaces.
Exact retries are protected for at least seven days. DNC LATAM retains only a keyed, non-reversible fingerprint—not the raw idempotency key, request body, phone numbers, or response.

​
Completed retry

When the original request completed successfully, an exact retry is recalculated in memory and returns:
The replay does not consume quota or write a second usage event.

​
Concurrent retry

If the original request is still running, the API returns HTTP 409:
Respect the Retry-After header and retry the same payload with the same idempotency key.

​
Reused key with a different payload

If the same key is used with a different country or phone array, the API returns HTTP 409:
Do not retry this response. Generate a new idempotency key for the new logical request. Store the idempotency key beside your own internal job identifier and a non-sensitive status. Do not store the phone-number payload merely to support API retries if your own retention policy does not otherwise require it.