Phone Contact Validate API
/phone_contact_validate
Validates the link between a specific Australian phone number and a person associated with that phone number. Returns match, possible match, or no match.
Example Request
POST{
"requests": [
{
"phone": "+61491222111",
"first_name": "John",
"last_name": "Smith"
}
]
}
Request Schema
List of validations.
E.164 format.
First name
Last name
Available Response Data
4 Data PointsBatch Message Status
Array of Validation Results
Primary Match Status
Match, Possible Match, No Match
Component Match Granularity
Exact, Partial, or Alias matches across First, Middle, and Last name fields
Technical Use Cases
Synthetic Identity Protection
Ensure the user claiming a specific phone number matches the actual recorded owner of that number.
Data Verification Workflows
Pass/fail users silently in the background based on exact or possible match scores without adding friction to the UI.
Webhooks & Events
validation-mismatch-alert
Fire an alert to your compliance team if a high-value transaction is tied to a "no match" phone identity.
Compliance & Security
Enterprise-grade infrastructure audited against the standards your regulators require.
Common Questions
Everything you need to know about implementation details and compliance infrastructure.
help_center General
What triggers a "possible_match"?
add
What triggers a "possible_match"?
If the last name matches perfectly, but the first name is a known alias or initial (e.g., “Bob” instead of “Robert”), the system will gracefully return a possible match rather than failing the user.