Marketing Contact Lookup API
/marketing_contact_lookup
A contact lookup for marketing and outreach work. You give it one piece of information about a person (a phone, an email, a GNAF ID, or an address) and it returns up to 25 matching records from the GlobalData universe, ordered most recent first. Every phone and email comes back with its own opt-in flag so you know what you can actually use in a campaign. Deceased and suppressed records are filtered out before you see them.
Example Request
POSTRequest Schema
phone
Australian phone in either 0NSN (0299995000) or E.164 (+61299995000) format. Pick one lookup key per request.
email
Email address. Case insensitive.
gnaf_id
GNAF address identifier, for example GANSW716615055.
full_address
A single free-text Australian address. The API parses this and resolves it to a GNAF.
street_address
street_address plus postcode (with optional suburb and state to improve match accuracy)
suburb
Suburb component of the address.
state
ACT, NSW, NT, QLD, SA, TAS, VIC or WA.
postcode
Required when street_address is supplied.
max_records
Sets the maximum number of person records to return from 1 to 25 with a default of 1. All results are deduplicated by unique identity so an individual with multiple historical tenancies appears as a single record.
require_marketing_optin
Filters contact methods based on marketing consent when set to true. Any records lacking opted-in contact information are excluded and the system automatically continues searching to fulfill the requested record count.
Available Response Data
9 Data PointsFull name: title, first, middle, last
Date of birth, or a from/to DOB range when the exact date is unknown
Gender
All known phones, each with its own marketing_opt_in flag
All known emails, each with its own marketing_opt_in flag
GNAF address ID, street, suburb, state, postcode
Tenancy dates at the address
date_start and date_end; date_end is null while the person still lives there
Latitude and longitude
The API reference for the request
API Data Scale & Coverage tag
Unmatched data depth to power your compliance and verification workflows.
Technical Use Cases tag
Building an outbound marketing list
Resolve a postcode, suburb or GNAF down to a list of opted-in marketing contacts you can actually use, without having to scrub DNC and opt-in flags row by row.
Appraisal outreach for real estate
Look up the current and past residents of a property using just its GNAF ID, with the opt-in status sitting right there on each phone and email.
Enriching an inbound lead
A new enquiry comes in with just a phone number or email. Pull the full identity record so the rep can verify the caller and personalise the follow-up without re-asking for basic details.
Resolving who lives at an address right now
When a GNAF has had multiple residents over time, the most-recent-first ordering surfaces the current household first. Useful for delivery, service activation and change-of-tenancy work.
Webhooks & Events tag
person.updated
A phone number, email, or address record has changed.
person.compliance_changed
The marketing_opt_in flag has been toggled.
person.status_changed
A record has been flagged as deceased or added to suppressions.
Compliance & Security tag
Enterprise-grade infrastructure audited against the standards your regulators require.
Common Questions tag
Everything you need to know about implementation details and compliance infrastructure.
help_center General
What does this endpoint NOT do?
add
What does this endpoint NOT do?
It does not run a social check, a DNC check, an email or phone deliverability check, return court records, or surface business associations. Each of those has its own dedicated endpoint (Social Check, DNC, Email Ping, Phone Ping, Court Check and Enhance Record Plus).
gavel Compliance
How does the opt-in flag work?
add
How does the opt-in flag work?
Opt-in is recorded against the combination of a person and a specific phone or email, not against the address. The address comes back for reference only. Do not assume an address itself is opted in.
rocket_launch Implementation
What happens when I set require_marketing_optin: true and the best-match person has no opted-in contacts?
add
What happens when I set require_marketing_optin: true and the best-match person has no opted-in contacts?
That person is skipped and the API keeps scanning further down the candidate list until it fills the max_records quota. If no one in the candidate set has any opted-in contacts at all, you get records: [] back.
gavel Compliance
Are deceased people filtered out?
add
Are deceased people filtered out?
Yes. Deceased records are excluded from every response, along with anything caught by the suppressions system.
rocket_launch Implementation
What's the biggest result set I can pull?
add
What's the biggest result set I can pull?
25 records via the max_records parameter. The default is 1. Persons are deduplicated by identity before that slice happens, so someone who lived at an address across multiple tenancies still only counts as one record.
Ready to integrate Marketing Contact Lookup API?
Talk to our team about credentials, sandbox access and the right combination of endpoints for your workflow.