Scrub a small batch of phone numbers synchronously
Use v1 for batches of up to 10,000 inputs and 25 MiB of JSON body, whichever limit is reached first, that should complete within the 15-second synchronous execution budget. The response is one complete result or an error; no partial result is returned. Every v1 response, including 4xx and 5xx errors, carries x-retention: zero and Cache-Control: no-store, max-age=0. Phone Input and per-number Scrub Result exist only in request memory; bounded non-phone request metadata (including idempotency digests and quota state) and approved aggregate usage data may remain. Country examples are contractual and still require a matching Country Purchase and operational/activation gates. Use v2 for larger batches or work that may wait on a country service.
Authorizations
Headers
Opaque key for one logical request, scoped to the authenticated API key. Use a high-entropy value and never include phone numbers or other PII. Exact retries are protected for at least 7 days for v1; v2 keeps the accepted job identity for the job metadata lifetime.
1 - 255^[\x21-\x7e]+$Body
The v1 body is limited by both 10,000 phone entries and a 25 MiB JSON body. The first limit reached controls admission.
Technical country code. The current sellable catalog is mx/ar/co. es/au/sg are planned product coverage, end of September 2026, and are not sellable at checkout until their catalog and runtime are released together. Every real request requires a matching Country Purchase and country availability/activation. Colombia is sellable and operational, and a successful initial payment activates its complete API access immediately without manual approval; entitlement and operational availability are still evaluated at admission.
mx, ar, co, es, au, sg Response
Scrub completed
One complete result for the submitted Scrub Batch. No provider chunks or partial result are exposed.