POST /v1/scrub and POST /v2/scrub request requires an
Idempotency-Key header.
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
countryandphonesarray. - 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.
Completed retry
When a v1 request completed successfully, an exact retry is recalculated in memory and returns:job_id and may include Idempotency-Replayed: true.
The status is 202 while the job is still active and 200 after it has
terminalized.
Concurrent retry
If the original v1 request is still running, the API returns HTTP409:
Retry-After header and retry the same payload with the same
idempotency key.
For v2, polling the job status is the normal way to observe a running job;
resubmitting the same key is safe but unnecessary.
Reused key with a different payload
If the same key is used with a different country or phone array, either API returns HTTP409: