Phone

Phone Contact Validate API

Phone Contact Validate confirms whether a specific person is linked to a specific Australian phone number in the Global Data Universe. It returns a match, possible match, no match or error for each request, with the name-by-name detail behind it, and no personal data.

Names standardised and aliases resolved before matching, so Bill matches William and Johnathan matches John
Up to 100 phone-and-name pairs per call, each with a result and the first, middle and last name match detail

Get API access Talk to us

For developers

After the technical detail?

For the technical detail, go to the API documentation. It holds the request and response schema, the integration guides and the error codes for this endpoint.

Request and response schema
Name match rules and sandbox records

View developer documentation

Accounts start in the sandbox. Production keys are issued once the account is approved.

Encrypted in transit and at rest Handled under the Australian Privacy Principles

What the check gives you

Confirming the phone number a customer gives you is theirs

A phone number is only useful as an identifier if it belongs to the person who gave it. Phone Contact Validate takes the number and the name and reports whether the two are linked in the Global Data Universe. Nothing but the match result comes back, which suits a signup or fraud check where you already hold the details.

Whether the number belongs to the person

Each request returns match when every name matched exactly, possible match when any name matched partially or through an alias, and no match when none did.

How each name matched

The first name and middle name each return exact, partial, alias or no match. The last name returns exact or no match, and must match exactly for any match to be returned.

What partial and alias mean

A partial match is a substring starting with the name on record, such as John for Johnathan. An alias match is a known equivalent, such as Bill for William.

Many pairs at once

Up to 100 requests per call, answered in the same order, with a per-request message where a check could not be completed.

Reading the result

What each answer means for the record in front of you

The result is decided by the name matches. A last name that does not match exactly always gives no match.

Match

The person is linked to the number

Every name supplied matched the record exactly.

Possible match

Linked, with a name difference

The last name matched exactly and a first or middle name matched partially or through an alias. Decide by your own rules whether that is enough.

No match

No link found

No record links the person to the number, or the last name did not match exactly.

Error

The request could not be checked

The phone number is not a valid Australian phone number or could not be searched, so the request was skipped.

What it costs

A monthly subscription, drawn down as you run checks

Your subscription is credited to your account each month and each check consumes credits from it. If you go past the included amount, further checks are charged at a per-check rate. The rate depends on the volume you commit to, so the sales team is the fastest way to find where your business lands.

Volume-based pricing
No lock-in contract

How billing works

Subscribe monthly, spend it as credits

The monthly subscription arrives as credits on your account.
Each check draws down credits as it runs.
Checks beyond the included credits are billed per check.
Higher monthly volume moves you to a lower rate.

Talk to sales about volume

Related checks

Others in Phone

Phone Contact Lookup returns the people linked to a number when you do not hold a name. Global Data Check confirms a phone alongside other details in one call.

Check phone connectivity API Check phone DNC status API Phone Contact Lookup API

All Phone endpoints

Questions

Questions we get asked about Phone Contact Validate

Do we need a developer to implement this?

Yes. Phone Contact Validate is a REST endpoint that takes a JSON array of requests and returns a JSON array of results, so a developer connects it to your signup or fraud process. A sandbox with a deterministic test dataset is provided at no usage cost, so the integration can be built and tested before production keys are issued.

What does our system need to send?

A requests array of up to 100 items, each with a phone number in E.164 format, a first name, an optional middle name and a last name.

What comes back?

A results array in the same order. Each carries the number, a result of match, possible match, no match or error, a message, and the first, middle and last name match detail. No personal data is returned.

Where does the data come from?

The Global Data Universe, an in-house dataset of person and contact records aggregated from many sources. The reference documentation does not publish a refresh cycle.

Are the names and numbers we send stored by Global Data?

Personally identifiable information sent in a request is not stored or retained unless it is needed to process that request. Query data is stripped of PII before it is kept for audit. Data in transit and at rest is encrypted, and retention follows the Australian Privacy Act and the Australian Privacy Principles. Global Data is not a credit bureau and does not create an access footprint on any record.

How many calls can we make?

The API allows 600 requests per minute by default, measured as a rolling average, and returns a 429 response above that rate. A higher limit can be requested through Global Data support with a description of the operational need.

Getting started

The first step to access is a conversation

New accounts begin with sandbox access, and production API keys are issued once the account has been commercially approved.

Get API access Talk to us

Call 03 9948 4089, 9am–5pm AEST Monday to Friday

Encrypted in transit and at rest

Handled under the Australian Privacy Principles

ISO 27001 Certified