Person

Person Report API

Person Report takes whatever you know about a person and resolves it to a single subject in the Global Data universe. The request is queued and answered at once with a request UUID. The consolidated report, with every fact cited to the lookup it came from, is collected from the Person Report Result call. The endpoint is experimental and may change.

A name, a date of birth, an address or locality, a phone number, an email address, or any combination, resolved to one person
Identity, address timeline, contacts, household, business, ASIC, UK Companies House, watchlist, court, judgement and social sections in one report

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
Resolution outcomes and sandbox inputs

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

Building one picture of a person from partial details

A file rarely holds a complete identity. Person Report accepts what is known, searches the person universe, the ASIC person register, the commercial universe and social enrichment in rounds, and feeds each new identifier into the next round until nothing new appears. The result is one report about one person, with a plain-English research log of what was searched, found, decided and rejected.

Whether one person was found

The resolution outcome states what happened. Resolved means one subject was identified with medium or high confidence and a report is attached. Low confidence, ambiguous, too many and not found each explain what to add or confirm next.

Everything held about them

A resolved report carries the identity, an address timeline with tenure, co-residents and real-estate events, contacts, possible relatives, business and ASIC records, UK Companies House officer records, watchlist matches, court record summaries, judgements and a social profile.

Where each fact came from

Every fact cites the source lookup it came from. Provenance lists every lookup with its exact query, every inference with the rule applied and the evidence behind it, and the chronological research notes. It is always returned in full.

A way to narrow an uncertain match

An ambiguous or low-confidence outcome returns a redacted candidate list. Your system re-submits with the candidate token of the right person, or adds a phone, an email or a date of birth. Tokens are valid for one hour in the same environment.

How a check runs

Request now, collect when the report is ready

The request is queued and answered at once with a request UUID and a result URL. Resolution runs in the background. Your system polls the Person Report Result call, which is free, until the status is complete or error, and then reads the resolution outcome.

At least a first and last name, a phone, an email or a candidate token is required. Up to four phones and four emails can be sent. The last name is matched exactly. Common first-name equivalents, such as Bob and Robert, are searched automatically. Results are retained for 24 hours.

Reading the result

What each resolution outcome means for the record in front of you

The resolution outcome on the completed result tells your team whether to read the report or to supply more detail. Only a resolved outcome carries a report.

Resolved

One subject was identified

The match is at medium or high confidence and the report is attached. Same-name records that were examined and set aside are listed with the reason they were not selected.

Low confidence

One candidate matched on name only

The details supplied did not corroborate the candidate. Confirm with the candidate token, or add a phone, an email or a date of birth.

Ambiguous

Several people match

A redacted candidate list is returned with a token for each. Re-submit with the token of the right person, or add narrowing details.

Too many or not found

The name is too common, or nothing matched

Too many returns distribution hints by state and birth decade, so add a date of birth, postcode, phone or email. Not found means nothing matched; check the details or try a different identifier.

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.

Pay as you go available
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 Person

Person Report Result collects the report started here. Person History returns the dated address and contact records for a person. Global Data Check confirms details without returning any.

Banned and Disqualified Person Search API Deceased Check API Enhance Record Plus API Marketing Contact Lookup API Person History API Person Report Result

All Person endpoints

Questions

Questions we get asked about Person Report

Do we need a developer to implement this?

Yes. The request is a REST endpoint that queues the report and returns a request UUID, and the result is collected with a second call, so a developer connects the two-step flow to your system. A sandbox that runs against a sample universe 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?

Whatever is known about the person. At least a first and last name, a phone, an email or a candidate token is required. Optional fields are a middle name, a date of birth in YYYY-MM-DD format, up to four Australian phone numbers, up to four email addresses, a street address, and a suburb, state or postcode to narrow the search.

What comes back from this call?

An acknowledgement only: a message of Ok, an API reference that is also the billing correlation ID, the request UUID, a status of pending and the URL of the result endpoint. The resolution, report and provenance are collected from Person Report Result.

How is the person identified?

Resolution is iterative. Each source consulted can return new identifiers, which feed the next round of searches until no new information appears. The last name is matched exactly. A date of birth is treated as evidence rather than a key, so a date that is a day out or has the day and month swapped still matches and is reported as a near miss.

What happens when more than one person matches?

An ambiguous outcome returns a redacted candidate list, each with a name, birth year, localities, tenure, score and the evidence for and against. Re-submit with the candidate token of the right person, or add narrowing details. A too-many outcome returns distribution hints instead of a list.

How long does it take, and what does it cost to poll?

Typical turnaround is a few seconds. Allow up to a minute when the court and social sections are included. Polling the result endpoint is free; only this request is billed, and nothing is billed when the status is error. Results are retained for 24 hours.

Is this endpoint stable?

No. The reference marks the Person Report API as experimental and subject to change.

Are the details 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.

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