Skip to main content
The request body contains one registry country and an array of phone-number strings:

​
Registry country

All inputs in one request are interpreted against the selected country. Split mixed-country data into separate requests with separate idempotency keys. Catalog presence does not replace entitlement or operational admission; a country can be pending activation, in maintenance, or temporarily unavailable. mx, ar, and co are the live commercial catalog. es, au, and sg are coming end of September 2026 (not live yet).

​
Accepted formats

The API accepts supported local and international formats and normalizes them before performing an exact match against the selected registry. Each array entry may be at most 64 characters. A longer string fails the whole request with 400 phone_too_long before any per-item validation; it is not returned as an invalid_numbers entry. Examples of supported Mexico representations:
Examples of supported Argentina representations:
The API returns the original string in the corresponding response array. It does not replace your input with the internal canonical representation.

​
Structural validation

Validation determines whether an input can be normalized for matching. It does not verify that a number is assigned, active, reachable, or owned by a specific person. Invalid inputs are returned per item and do not fail the rest of the batch:

​
Duplicates

Every submitted array element counts as one checked input. If the same number appears three times, it is counted and returned three times. The service may deduplicate normalized values internally for lookup efficiency, but the response preserves occurrences and relative order within each response category.