RESTful API's

Integrate compliance at the API level

Automate identity verification, liveness checks, and risk screening directly from your backend with our low-latency REST API.

lock api.example.com/v2
POST /identity/verify HTTP/1.1
Authorization: Bearer sk_live_...
Content-Type: application/json
200 OK 98ms
{
  "status": "verified",
  "verification_id": "req_99b4x",
  "results": {
    "liveness": "passed",
    "id_match": true
  }
}
ap-southeast-2 · Sydney
SDK v1.2.4
Global Data APIs

API Reference

Our advanced RESTful API offers an ideal solution for seamless integration into your software ecosystem. Designed for both real-time and offline access, our API ensures flexibility and reliability. Expertly developed with the same robust queries that power our SaaS platforms, it allows you to effortlessly combine and encapsulate queries to create powerful, customised products and services. By leveraging our API, you can enhance your software’s functionality, streamline operations, and deliver superior user experiences with minimal friction.

Getting Started

Introduction

The Global Data API allows external programmatic access to the full functionality of the Global Data suite of validation, verification and search functions. The API accesses the same dataset and produces the same results as the api.globaldata.net.au web system.

Environments

Sandbox vs Live

The Global Data API provides two environments. Use the Sandbox API server when working with a Sandbox API key. Use the Live API server when working with a Live API key. Requests made with a key to the wrong environment will return a 401 Unauthorized error.

Production
Live

Real data, billable transactions. Requires a Live API key issued after onboarding.

https://gdapi.globaldata.net.au/api/v2
Testing
Sandbox

Restricted dataset for integration testing. Free to use with a Sandbox API key.

https://sandbox-example.globaldata.net.au

Heads up: requests made with a key to the wrong environment return a 401 Unauthorized error.

Authorization

Authentication

The Global Data API uses API keys to authenticate requests. All API requests must be made over HTTPS. Calls made over plain HTTP will fail. Pass your key as a Bearer token in the Authorization header.

Header Format
Authorization: Bearer YOUR_API_KEY
Request Sandbox Access

API keys are provisioned for institutional partners following verification. Contact our sales team to discuss integration requirements and production credentials.

Talk to Sales

Test

1 endpoint

API Testing endpoint

GET /test

A no-op endpoint that returns Ok if your authentication is good and the API is reachable.

A no-op endpoint that returns Ok if your authentication is good and the API is reachable. Useful as a heartbeat or smoke test during integration, environment switching, and CI pipeline checks. Doesn't consume credit.

Request Schema 1 param
Authorization
Required
string

header

Example Request
GET /test

Address

7 endpoints

Address Autocomplete API

GET /address_autocomplete

Address Auto-Complete is a powerful API query that can save users time and reduce errors by predicting and suggesting Australian addresses as they are being typed.

Address Auto-Complete is a powerful API query that can save users time and reduce errors by predicting and suggesting Australian addresses as they are being typed. This feature can be integrated into any web or mobile application to streamline data entry and improve overall data accuracy.

Request Schema 3 params
partial_address
Required
integer · (4 to 100 chars)

The first 4 or more characters of the address, street, suburb or postcode.

type
Optional
string

address (full addresses with GNAF id), street (street names with suburb/postcode/state), suburb (suburbs with postcode/state), or postcode (suburbs within a postcode). Default address.

max_results
Optional
integer · (1 to 100)

Maximum number of results to return. Default 20.

Example Response 200 OK
{ 
  "partial_address": "123 Smith", 
  "type": "address", 
  "max_results": 20 
}

Address Lookup by Contact API

GET /address_lookup_by_contact

Returns the GNAF ID which corresponds to a given email address or phone number from the Global Data universe.

Returns the GNAF ID which corresponds to a given email address or phone number from the Global Data universe.

Request Schema 2 params
email
Optional
string

The email address to search for. Example: jsmith1998@example.co

phone
Optional
string

The phone number to search for. Example: 0491222111

Example Request
{
  "message": "Ok",
  "address_id": "GANSW716615055",
  "record_date": "2021-01-01",
  "api_reference": "738d9a89-b6fe-4fc1-96be-1389b2a506a2"
}

Address Validate API

POST /address_validate

Tests a supplied address against the GNAF database and returns a quality score from 0 to 10, plus the matched address with any corrections applied.

Tests a supplied address against the GNAF database and returns a quality score from 0 to 10, plus the matched address with any corrections applied. The validator will fix minor mistakes (spelling errors in the street or suburb, the wrong street type, a postcode that's one off) so long as the rest of the address is still resolvable. You get the corrected address back along with a list of every change that was made.

Request Schema 6 params
street_address
Required
string · (4 to 100 chars)

First line of the address. Requires at least one of suburb or postcode.

suburb
Optional
string · (2 to 60 chars)

Suburb name. Requires street_address.

state
Optional
enum

ACT, NSW, NT, QLD, SA, TAS, VIC, WA. Requires street_address.

postcode
Optional
string · (3 to 4 chars)

Postcode. Requires street_address.

suburb_state_postcode
Required
string · (4 to 100 chars)

Combined suburb, state and postcode. Requires street_address.

full_address
Conditional
string · (4 to 255 chars)

Full address as a single string. Use this when you don't have the components separated.

Example Request
{
  "street_address": "Unit 12B, 123-125 Smith St",
  "suburb": "Smithtown",
  "state": "ACT",
  "postcode": "2000",
  "suburb_state_postcode": "Smithtown ACT 2000",
  "full_address": "Unit 12B, 123-125, Smithtown, ACT 2000"
}

Address Validate Bulk API

POST /address_validate_bulk

The bulk version of Address Validate.

The bulk version of Address Validate. Up to 200 addresses in a single call. Each item uses the same validation rules and input modes as the single endpoint. Optional check_id per request for correlating results back to your inputs..

Request Schema 3 params
requests
Required
array · (1 to 200 items)

Array of address validation requests.

requests[].check_id
Optional
string

Optional correlation ID echoed back in the result.

requests[].street_address, suburb, state, postcode, suburb_state_postcode, full_address
Conditional
mixed

Same input modes and combinations as the single Address Validate endpoint.

Example Request
{
  "requests": [
    {
      "check_id": "check_123",
      "street_address": "Unit 12B, 123-125 Smith St",
      "suburb": "Smithtown",
      "state": "ACT",
      "postcode": "2000",
      "suburb_state_postcode": "Smithtown ACT 2000",
      "full_address": "Unit 12B, 123-125 Smith St, Smithtown, ACT 2000"
    }
  ]
}

Property Detail API

GET /property_detail

Provides the resident and contact details (phone and email) linked to an address referenced by a GNAF ID.

Provides the resident and contact details (phone and email) linked to an address referenced by a GNAF ID. Automatically performs a connectivity and DNC check.

Request Schema 2 params
gnaf_id
Required
string

The address GNAF ID.

timeout
Optional
string

Maximum seconds to wait for checks to complete.

Example Request
GET /property_detail?gnaf_id=GANSW716615055&timeout=20

Real Estate Search (Bulk) API

POST /realestate_searches

Bulk version of the real estate search endpoint that allows up to 50 address lookups to be performed in a single request.

Request Schema 2 params
date_from
Optional
string

Date filter in YYYY-MM-DD format.

requests
Required
array

The list of address lookups to perform (uses standard address parameters).

Example Request
{
  "date_from": "2020-01-01",
  "requests": [
    { "gnaf_id": "GAVIC421647320", "check_id": "asset_1" },
    { "full_address": "123 Main St, Sydney NSW", "check_id": "asset_2" }
  ]
}

Real Estate Search API

POST /realestate_search

Returns the real estate listing history (sale, sold, and rental events) for a property, sourced from the GlobalData Australian property universe.

Returns the real estate listing history (sale, sold, and rental events) for a property, sourced from the GlobalData Australian property universe. Accepts a GNAF ID, a full address as a single string, or structured address parts. Results come back most recent first, with an optional date_from filter to limit to recent activity

Request Schema 7 params
gnaf_id
Conditional
string · (max 15 chars)

The GNAF address ID. Most efficient lookup. Mutually exclusive with full_address and the structured parts.

full_address
Conditional
string · (4 to 255 chars)

A complete address as a single string. Mutually exclusive with the other modes.

street_address
Conditional
string · (4 to 100 chars)

Street address component. Use with suburb, state, postcode for structured mode.

suburb
Optional
string · (3 to 60 chars)

Suburb. Used with street_address.

state
Optional
enum

ACT, NSW, NT, QLD, SA, TAS, VIC, WA. Used with street_address.

postcode
Optional
string · (3 to 4 chars)

Postcode. Used with street_address.

date_from
Optional
date

Optional. Only return records on or after this date.

Example Request
{
  "gnaf_id": "GAVIC421647320",
  "date_from": "2015-01-01"
}

Phone

4 endpoints

Check phone connectivity API

GET /phone_ping

Tests the connectivity of one or more supplied phone numbers (Connected, Disconnected, Undetermined, Invalid).

Tests the connectivity of one or more supplied phone numbers (Connected, Disconnected, Undetermined, Invalid).

Request Schema 2 params
phones
Required
string

One or more comma-separated 10 digit Australian phone numbers.

timeout
Optional
integer

Maximum seconds to wait.

Example Request
{
  "phones": "0417034325",
  "timeout": 60
}

Check phone DNC status API

GET /phone_dnc

Tests the DNC (Do Not Call) status of one or more supplied phone numbers against the Australian DNC register.

Tests the DNC (Do Not Call) status of one or more supplied phone numbers against the Australian DNC register.

Request Schema 1 param
phones
Required
string

Comma separated 10 digit Australian phone numbers.

Example Request
{
  "phones": "0417034325"
}

Phone Contact Lookup API

POST /phone_contact_lookup

Retrieve the person or persons linked to a specific Australian phone number in the Global Data Universe.

Retrieve the person or persons linked to a specific Australian phone number in the Global Data Universe.

Request Schema 1 param
phones
Required
array

The phone numbers to search for in E.164 format.

Example Request
{
  "phones": [
    "+61491222111",
    "+61499888777"
  ]
}

Phone Contact Validate API

POST /phone_contact_validate

Validates the link between a specific Australian phone number and a person associated with that phone number.

Validates the link between a specific Australian phone number and a person associated with that phone number. Returns match, possible match, or no match.

Request Schema 4 params
requests
Required
array

List of validations.

phone
Required
string

E.164 format.

first_name
Required
string

First name

last_name
Required
string

Last name

Example Request
{
  "requests": [
    {
      "phone": "+61491222111",
      "first_name": "John",
      "last_name": "Smith"
    }
  ]
}

Email

1 endpoint

Check email deliverability API

GET /email_ping

Tests the deliverability of one or more supplied email addresses.

Tests the deliverability of one or more supplied email addresses.

Request Schema 1 param
emails
Required
string

One or more comma-separated email addresses.

Example Request
{
  "emails": "test@example.com"
}

Person

5 endpoints

Banned and Disqualified Person Search API

POST /banned_disqualified_persons

Screens an individual against multiple public authorities in one call.

Screens an individual against multiple public authorities in one call. It covers the ASIC Banned Persons Register and the ATO Disqualified SMSF Trustees list. Bulk requests are supported, with a configurable similarity threshold and three search modes (narrow, medium, broad) that change how strictly the names have to line up. Use it for both transactional checks and batch screening of director rosters or trustee lists.

Request Schema 4 params
search_type
Required
enum

narrow_search (exact first and last, middle by similarity), medium_search (exact last, partial first and middle), or broad_search (partial across all three).

banned_types
Optional
array

Filter to specific ban types: afs_banned_disqualified, banned_futures, banned_securities, credit_banned_disqualified, disqualified_director, disqualified_smsf, ato_disqualified_trustee. Leave empty to search all.

similarity_threshold
Optional
integer

Minimum average similarity percentage to include in results. Default 80.

requests
Required
array

Array of person checks, each with check_id, first_name, middle_name, last_name.

Example Request
{
  "search_type": "medium_search",
  "banned_types": ["afs_banned_disqualified"],
  "similarity_threshold": 80,
  "requests": [
    {
      "check_id": "abcd123456789",
      "first_name": "Phil",
      "middle_name": null,
      "last_name": "Smith"
    }
  ]
}

Deceased Check API

POST /deceased_check

Checks whether a person is recorded as deceased in the Global Data death check service.

Checks whether a person is recorded as deceased in the Global Data death check service. You can search by name and date of birth, by name and date of death, or by all three. The name-matching rules shift depending on which combination you send. The response is a simple Y or N indicator that drops easily into KYC pipelines and customer maintenance flows.

Request Schema 4 params
first_name
Required
string

First name and optional middle names. The matching rules depend on whether you send a DOB, DOD, or both. See the FAQs below.

last_name
Required
string

Last name.

birth_date
Optional
string

Date of birth. Triggers DOB-mode matching, which lets you skip middle names.

death_date
Optional
string

Date of death. If sent on its own (no DOB), the first name has to match exactly including any middle names.

Example Request
{
  "first_name": "John Andrew",
  "last_name": "Doe",
  "birth_date": "1971-01-23",
  "death_date": "2011-11-03"
}

Enhance Record Plus API

POST /enhance_record_plus

Hand it a partial person record and it gives you back the full picture: verified address, additional phones and emails, possible business associations, demographic indices, plus court records and social records for the matched contacts.

Hand it a partial person record and it gives you back the full picture: verified address, additional phones and emails, possible business associations, demographic indices, plus court records and social records for the matched contacts. The "Plus" tier runs the court and social checks automatically on the matched result, so you get a richer dossier than the base Enhance Record service in a single call.

Request Schema 11 params
first_name
Required
string

Required as part of the minimum-search combinations.

middle_name
Optional
string

Optional middle name.

last_name
Required
string

Required when combined with DOB or address.

dob
Required
string

Date of birth. Required if you're not sending an address (and vice versa).

phone
Required
string

0NSN format. A phone is enough on its own to meet the minimum requirement.

email
Required
string

An email is enough on its own too.

street_address
Optional
string

Address line 1.

suburb
Optional
string

Suburb.

state
Optional
enum

ACT, NSW, NT, QLD, SA, TAS, VIC or WA.

postcode
Optional
string

Four-digit postcode.

opt-in
Optional
boolean

Limit results to records opted in to marketing or public records (such as whitepages). Social records are never opt-in checked and must not be used for marketing.

Example Request
{
  "first_name": "Michael",
  "middle_name": "John",
  "last_name": "Raymond",
  "dob": "1969-06-21",
  "phone": "0412345678",
  "email": "michael.raymond@example.com",
  "street_address": "12 Conestoga Way",
  "suburb": "Upper Coomera",
  "state": "QLD",
  "postcode": "4209",
  "opt-in": false
}

Marketing Contact Lookup API

POST /marketing_contact_lookup

A contact lookup for marketing and outreach work.

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.

Request Schema 10 params
phone
Required
string

Australian phone in either 0NSN (0299995000) or E.164 (+61299995000) format. Pick one lookup key per request.

email
Required
string

Email address. Case insensitive.

gnaf_id
Required
string

GNAF address identifier, for example GANSW716615055.

full_address
Required
string

A single free-text Australian address. The API parses this and resolves it to a GNAF.

street_address
Required
string

street_address plus postcode (with optional suburb and state to improve match accuracy)

suburb
Required
string

Suburb component of the address.

state
Required
string

ACT, NSW, NT, QLD, SA, TAS, VIC or WA.

postcode
Required
string

Required when street_address is supplied.

max_records
Optional
integer

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
Optional
boolean

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.

Example Request
{
  "phone": "0299995000",
  "email": "mary_jones89@example.com",
  "gnaf_id": "GANSW716615055",
  "full_address": "35 Yaralla St, Concord West NSW 2138",
  "street_address": "35 Yaralla St",
  "suburb": "Concord West",
  "state": "NSW",
  "postcode": "2138",
  "require_marketing_optin": false,
  "max_records": 5
}

Person History API

POST /person_history

Query and retrieve additional historical data for a specific individual.

Query and retrieve additional historical data for a specific individual. Includes an automatic Australian Death Check (ADC).

Request Schema 5 params
first_name
Required
string
last_name
Required
string
birth_date
Optional
string
phone
Optional
string
email
Optional
string

(At least one optional contact/dob parameter required).

Example Request
{
  "first_name": "John",
  "last_name": "Smith",
  "birth_date": "1998-03-21",
  "phone": "0491222111",
  "email": "jsmith1998@example.com"
}

Deceased Check

2 endpoints

ADC Check API

POST /adc_check

Searches an individual against the Australian Death Check (ADC), the official death register data.

Searches an individual against the Australian Death Check (ADC), the official death register data. You get any matching records back, including the exact date of death where available (or a date range where it's not), the state the death was registered in, and the ADC reference number. Use this when your compliance posture wants verification against the official register rather than a proprietary dataset.

Request Schema 4 params
first_name
Required
string

First name. Has to match exactly.

middle_name
Optional
string

Optional. Middle names can match partially.

last_name
Required
string

Last name. Has to match exactly.

birth_date
Required
string

Date of birth in YYYY-MM-DD.

Example Request
{
  "first_name": "John",
  "middle_name": "Andrew",
  "last_name": "Smith",
  "birth_date": "1998-03-21"
}

ADC Check Bulk API

POST /adc_checks

The same as our ADC check, but you can submit a batch of lookups in one call.

The same as our ADC check, but you can submit a batch of lookups in one call. Each request carries a check_id so you can correlate results back to your inputs. Suited to periodic batch hygiene runs across customer registers, super funds, insurance books and other long-tenured populations.

Request Schema 6 params
requests
Required
array

Array of ADC check requests. Each accepts the same fields as the single check.

requests[].check_id
Optional
string

Your own ID for the request. Echoed back in the result so you can correlate.

requests[].first_name
Required
string

First name (exact match).

requests[].middle_name
Optional
string

Optional. Partial matches allowed.

requests[].last_name
Required
string

Last name (exact match).

requests[].birth_date
Required
string

YYYY-MM-DD.

Example Request
{
  "requests": [
    {
      "check_id": "abcd123456789",
      "first_name": "John",
      "middle_name": "Andrew",
      "last_name": "Smith",
      "birth_date": "1998-03-21"
    }
  ]
}

DVS

14 endpoints

Validate a birth certificate API

POST /dvs/birth_cert

Validates an Australian birth certificate against the DVS.

Validates an Australian birth certificate against the DVS. All eight states and territories are supported. Which identifiers you need (registration number, certificate number, registration date) depends on the state. The certificate number is the most reliable identifier across the board, so use it where you can.

Request Schema 7 params
preflight
Optional
string

Input validation only.

consent
Required
string

Individual's consent.

first_name, last_name, birth_date
Required
string

Name and DOB on the certificate.

registration_number
Required
string

Required (or certificate_number) for ACT, NSW, NT, SA, VIC, WA.

certificate_number
Required
string

Recommended for all states. Required for QLD or TAS if no registration_date.

registration_date
Required
string

Required for QLD or TAS if no certificate_number.

state
Required
enum

State of issue.

Example Request
{
  "consent": true,
  "first_name": "John",
  "last_name": "Smith",
  "birth_date": "1980-01-01",
  "certificate_number": "123456789",
  "state": "VIC"
}

Validate a change of name certificate API

POST /dvs/name_change

Validates a Change of Name certificate against the DVS.

Validates a Change of Name certificate against the DVS. Used when a customer has legally changed their name and you need to verify the certificate that establishes the new legal name against the issuing state Registry.

Request Schema 6 params
preflight
Optional
boolean

Input validation only.

consent
Required
boolean

Individual's consent.

first_name, last_name
Required
string

New name on the certificate.

birth_date
Required
string

YYYY-MM-DD.

registration_number, certificate_number, registration_date
Required
string

State-specific identifiers.

state
Required
enum

State of issue.

Example Request
{
  "consent": true,
  "first_name": "John",
  "last_name": "Smith",
  "birth_date": "1980-01-01",
  "certificate_number": "123456789",
  "state": "VIC"
}

Validate a citizenship certificate API

POST /dvs/citizenship

Validates an Australian citizenship certificate against the DVS using the stock number and acquisition date.

Validates an Australian citizenship certificate against the DVS using the stock number and acquisition date. Confirms the certificate was genuinely issued by the Department of Home Affairs and matches the identity you've supplied.

Request Schema 5 params
preflight
Required
boolean

Input validation only.

consent
Required
boolean

Individual's consent.

first_name, last_name, birth_date
Required
string

Identity of the document holder.

acquisition_date
Required
string

Acquisition date printed on the certificate.

stock_number
Required
string

Stock number printed on the certificate.

Example Request
{
  "consent": true,
  "first_name": "John",
  "last_name": "Smith",
  "birth_date": "1980-01-01",
  "acquisition_date": "1980-01-01",
  "stock_number": "123/45678"
}

Validate a death certificate API

POST /dvs/death_cert

Validates an Australian death certificate against the DVS.

Validates an Australian death certificate against the DVS. Confirms the certificate was genuinely issued by the Registry of Births, Deaths and Marriages in the issuing state and matches the details you've supplied. Used in estate administration, life insurance claims and superannuation death benefits work.

Request Schema 8 params
preflight
Optional
boolean

Input validation only.

consent
Required
boolean

Individual's consent.

first_name, last_name
Required
string

Names on the death certificate.

event_date
Required
string

Date of death.

registration_number
Required
string

Required (or certificate_number) in most states.

certificate_number
Required
string

Most reliable identifier. Recommended in all cases.

registration_date
Required
string

Relevant for QLD and TAS.

state
Required
string

State of issue.

Example Request
{
  "consent": true,
  "first_name": "John",
  "last_name": "Smith",
  "event_date": "1980-01-01",
  "certificate_number": "123456789",
  "state": "VIC"
}

Validate a drivers licence API

POST /dvs/drivers_licence

Validates an Australian driver licence against the DVS.

Validates an Australian driver licence against the DVS. All eight states and territories are supported. The endpoint accepts both the licence number and the card number, which is required by most states for verification. This is by far the most-used DVS document in Australian identity verification workflows.

Request Schema 7 params
preflight
Optional
boolean

Input validation only.

consent
Required
boolean

Individual's consent.

first_name, middle_name, last_name
Required
string

Names on the licence.

birth_date
Required
string

YYYY-MM-DD.

licence_number
Required
string

Licence number being validated.

card_number
Required
string

Card number printed on the physical card

state
Required
string

State of issue.

Example Request
{
  "consent": true,
  "first_name": "John",
  "middle_name": "James",
  "last_name": "Smith",
  "birth_date": "1980-01-01",
  "licence_number": "1234567890",
  "card_number": "P0001282",
  "state": "VIC"
}

Validate a marriage certificate API

POST /dvs/marriage

Validates an Australian marriage certificate against the DVS.

Validates an Australian marriage certificate against the DVS. Confirms both parties' names, the event date and registration details against the issuing state's Registry of Births, Deaths and Marriages.

Request Schema 7 params
preflight
Required
boolean

Input validation only.

consent
Required
boolean

Individual's consent.

first_name1, last_name1
Required
string

Name of the first person.

first_name2, last_name2
Required
string

Name of the second person.

event_date
Required
string

Date of marriage.

certificate details
Required
string

State-specific identifiers. Same rules as birth and death certificates.

state
Required
enum

State of issue.

Example Request
{
  "consent": true,
  "first_name1": "John",
  "last_name1": "Smith",
  "first_name2": "Mary",
  "last_name2": "Jones",
  "event_date": "1980-01-01",
  "certificate_number": "123456789",
  "state": "VIC"
}

Validate a Medicare card API

POST /dvs/medicare

Validates an Australian Medicare card against the DVS.

Validates an Australian Medicare card against the DVS. Green, yellow and blue cards are all supported. The Medicare card is one of the most-presented IDs in Australia and a core part of 100-point ID checks. The endpoint accepts the multi-line name format printed on Medicare cards (up to four lines).

Request Schema 8 params
preflight
Required
boolean

Input validation only.

consent
Required
boolean

Individual's consent.

full_name1, full_name2, full_name3, full_name4
Required
string

Name lines as printed on the card. Medicare uses up to four lines.

birth_date
Required
string

YYYY-MM-DD.

card_number
Required
string

10-digit Medicare card number

individual_ref_number
Required
string

Individual reference number for the card holder string (1 to 9).

card_expiry
Required
string

Card expiry (YYYY-MM) .

card_type
Required
string

G (green), Y (yellow) or B (blue).

Example Request
{
  "consent": true,
  "full_name1": "Marguerite",
  "full_name2": "Eleanor",
  "full_name3": "Jayne",
  "full_name4": "Salisbury",
  "birth_date": "1980-01-01",
  "card_number": "2951636283",
  "individual_ref_number": "1",
  "card_expiry": "2024-02",
  "card_type": "G"
}

Validate a registration by descent certificate API

POST /dvs/reg_by_descent

Validates an Australian Registration by Descent certificate against the DVS.

Validates an Australian Registration by Descent certificate against the DVS. Issued to people born outside Australia who are Australian citizens by virtue of being born to an Australian parent. This certificate is their proof-of-citizenship document.

Request Schema 5 params
preflight
Optional
boolean

Input validation only.

consent
Required
boolean

Individual's consent

first_name, last_name, birth_date
Required
string

Identity on the certificate.

acquisition_date
Required
string

Acquisition date printed on the certificate.

stock_number
Required
string

Stock number printed on the certificate.

Example Request
{
  "consent": true,
  "first_name": "John",
  "last_name": "Smith",
  "birth_date": "1980-01-01",
  "acquisition_date": "1980-01-01",
  "stock_number": "123/45678"
}

Validate an ASIC/MSIC Card API

POST /dvs/asic

Validates an Aviation Security Identification Card (ASIC) or Maritime Security Identification Card (MSIC) against the DVS.

Validates an Aviation Security Identification Card (ASIC) or Maritime Security Identification Card (MSIC) against the DVS. Both are federally regulated cards required for unescorted access to secure airside and maritime zones.

Request Schema 7 params
preflight
Optional
boolean

Input validation only.

consent
Required
boolean

Individual's consent.

full_name
Required
string

Full name of the card holder.

birth_date
Required
string

YYYY-MM-DD.

card_number
Required
string

Card number printed on the ASIC or MSIC card

card_expiry
Required
string

Card expiry string (YYYY-MM)

card_type
Required
enum

ASIC or MSIC.

Example Request
{
  "consent": true,
  "full_name": "John Smith",
  "birth_date": "1980-01-01",
  "card_number": "ABC123456",
  "card_expiry": "2024-02",
  "card_type": "ASIC"
}

Validate an ImmiCard API

POST /dvs/immicard

Validates an Australian Department of Home Affairs ImmiCard against the DVS.

Validates an Australian Department of Home Affairs ImmiCard against the DVS. ImmiCards are issued to non-citizens to help them establish identity in Australia, particularly refugees, humanitarian entrants and substantive visa holders who don't yet have an Australian-issued ID.

Request Schema 4 params
preflight
Optional
string

Input validation only.

consent
Required
string

Individual's consent.

first_name, last_name, birth_date
Required
string

Identity on the card.

card_number
Required
string

The card number follows a 3-letter + 6-digit format.

Example Request
{
  "consent": true,
  "first_name": "John",
  "last_name": "Smith",
  "birth_date": "1980-01-01",
  "card_number": "ABC123456"
}

Validate Australian travel documents API

POST /dvs/passport

Validates an Australian Passport, Certificate of Identity, Document of Identity or UN Convention Travel Document against the DVS.

Validates an Australian Passport, Certificate of Identity, Document of Identity or UN Convention Travel Document against the DVS. The passport check is high-assurance. Pair it with another DVS document and you've covered most of the strongest tiers of identity verification.

Request Schema 6 params
preflight
Optional
string

Input validation only.

consent
Required
string

Individual's consent.

first_name, last_name
Required
string

Name as printed on the document.

birth_date
Required
string

YYYY-MM-DD.

travel_document_number
Required
string

Document number being validated.

gender
Required
enum

M, F or X.

Example Request
{
  "preflight": false,
  "consent": true,
  "first_name": "John",
  "last_name": "Smith",
  "birth_date": "1980-01-01",
  "travel_document_number": "M1234567",
  "gender": "M"
}

Validate Australian visas API

POST /dvs/visa

Validates an Australian visa using the holder's foreign passport against the DVS.

Validates an Australian visa using the holder's foreign passport against the DVS. Confirms that the foreign passport holder has a current valid Australian visa attached to that travel document. Used for employment, tenancy and financial services verification of temporary residents.

Request Schema 4 params
preflight
Optional
boolean

Input validation only.

consent
Required
boolean

Individual's consent.

first_name, last_name, birth_date
Required
string

Identity on the document.

passport_number
Required
string

Foreign passport number linked to the visa.

Example Request
{
  "consent": true,
  "first_name": "John",
  "last_name": "Smith",
  "birth_date": "1980-01-01",
  "passport_number": "M1234567"
}

Validate with the AEC API

POST /dvs/aec

Validates a name, date of birth and address against the Australian Electoral Commission roll via the DVS.

Validates a name, date of birth and address against the Australian Electoral Commission roll via the DVS. The AEC is one of the broadest identity datasets in the country, which makes this a good low-friction identity check for customers who don't want to hand over a document ID.

Request Schema 7 params
preflight
Optional
string

Validates the input shape without performing the check.

consent
Required
string

The individual's consent to perform the check.

first_name and last_name
Required
string

Name on the AEC roll.

birth_date
Required
string

YYYY-MM-DD.

state, postcode, suburb
Required
string

Address components.

street_address
Optional
string

Full street line. Don't combine this with the parsed parts below.

street_number, street_name, street_type, flat_unit_number, habitation_building_name
Optional
string

Parsed components as an alternative to street_address.

Example Request
{
  "consent": true,
  "first_name": "John",
  "last_name": "Smith",
  "birth_date": "1980-01-01",
  "state": "VIC",
  "postcode": "3000",
  "suburb": "Melbourne",
  "street_address": "The Rialto 5/123 Smith St"
}

Caspar

2 endpoints

Caspar Person Autotrace API

POST /caspar_person_autotrace

Where Caspar Person Search returns matches against your criteria, Autotrace orchestrates dozens or hundreds of internal searches to assemble a ranked list of likely matches.

Where Caspar Person Search returns matches against your criteria, Autotrace orchestrates dozens or hundreds of internal searches to assemble a ranked list of likely matches. Each one is scored by how well it lines up with the identifiers you supplied. Optionally include possible relatives in the results. Suited to collections, investigations and skip-tracing where the goal is "find this person, and tell me how confident you are".

Request Schema 8 params
name_combined, name_first, name_middle, name_last
Conditional
string

Name fields. name_last is the minimum requirement.

dob
Optional
string · YYYY-MM-DD

Date of birth.

phone1, phone2, phone3, phone4
Optional
string

Up to four known phone numbers.

email1, email2, email3, email4
Optional
string

Up to four known email addresses.

Address components
Optional
string · full_address, suburb_state_postcode

Address scoping for distance-based scoring.

option_relatives
Optional
boolean

Include possible relatives. Records that don't match the full name but have an association.

first_result, max_results
Optional
integer · max_results is capped at 30

Pagination.

sort_by, sort_order
Optional
enum

Default is score DESC, which is the most useful ordering for autotrace.

Example Request
{
  "name_first": "MARY",
  "name_last": "JONES",
  "dob": "1989-08-12",
  "phone1": "0299995000",
  "email1": "mary_jones89@example.com",
  "full_address": "35 YARALLA ST CONCORD WEST NSW 2138",
  "option_relatives": true,
  "max_results": 10
}

Caspar Person Search API

POST /caspar_person_search

The most flexible identity search in the Global Data universe.

The most flexible identity search in the Global Data universe. Caspar accepts any combination of name, address, phone, email, IP address or social profile URL and returns matching person records with their full known contact and address history. Six "smart" options let you widen or narrow the search, including the smart-search mode that treats name and address as one criterion and the other identifiers as independent matchers.

Request Schema 16 params
name_combined, name_first, name_middle, name_last
Conditional
string

Person name fields. At minimum, name_last (or another search key) has to be supplied.

dob_from, dob_to
Optional
date

DOB range bounds.

secondary_name_first, secondary_name_last, secondary_dob_from, secondary_dob_to
Required
string

Secondary person search. Finds two people at the same address.

street_address, suburb, state, postcode, full_address, suburb_state_postcode
Conditional
string

Address components, a full address, or address line 2.

phone
Conditional
string · 0NSN or E.164 format

Phone number.

email
Conditional
string

Email address.

ip_address
Optional
string · IPv4

IPv4 only. IPv6 is not supported.

social_url
Optional
boolean · URL

Facebook, LinkedIn, Twitter/X, YouTube, Instagram, Indeed, GitHub, Meetup, Quora, Gravatar, Foursquare or Pinterest profile URL.

option_smartname
Optional
boolean

Matches initials, first-name equivalents (Robert / Bob / Rob) and similar-sounding last names (Smith / Smyth).

option_smartemail
Optional
boolean

Matches the email username across different domains and TLDs.

option_smartphone
Optional
boolean

Matches partial phone numbers across area codes and mobile prefixes.

option_smartaddress
Optional
boolean

Matches similar or misspelled addresses in the selected area or neighbouring suburbs.

option_smartsearch
Optional
boolean

Changes the search logic to (Name AND Address) OR Phone OR Email OR IP OR Social

option_marketing_opt_in
Optional
boolean

Include per-contact marketing_opt_in flags on each record.

first_result, max_results
Optional
integer

Pagination. max_results is capped at 30.

sort_by, sort_order
Optional
enum

Result ordering.

Example Response 200 OK
{
  "name_first": "MARY",
  "name_last": "JONES",
  "full_address": "35 YARALLA ST CONCORD WEST NSW 2138",
  "option_smartsearch": true,
  "option_marketing_opt_in": true,
  "max_results": 10
}

Payroll and Super Check

3 endpoints

Payroll and Super Check API

POST /payroll_super_check

Runs a Payroll Check and a Super Check in a single call, with independent consent flags for each dataset.

Runs a Payroll Check and a Super Check in a single call, with independent consent flags for each dataset. You get separated super and payroll result objects in the response. Lets your workflow react to a match in either dataset without two round-trips

Request Schema 8 params
super_consent
Required
boolean

Individual's consent to search super records.

payroll_consent
Required
number

Individual's consent to search payroll records.

first_name, last_name, birth_date
Required
string

Minimum required for a valid lookup.

middle_name
Optional
string

Optional Middle name.

address
Optional
object · (street_address, suburb, state, postcode)

Address components for cross-matching.

email
Optional
string

Additional fields evaluated for match outcome.

phone
Optional
string

Additional fields evaluated for match outcome.

employer_abn
Optional
string

Additional fields evaluated for match outcome.

Example Request
{
  "first_name": "John",
  "middle_name": "James",
  "last_name": "Doe",
  "birth_date": "1990-01-01",
  "address": {
    "street_address": "4/123 Fake Street",
    "suburb": "Fakeville",
    "state": "VIC",
    "postcode": "3987"
  },
  "email": "john@example.com",
  "phone": "0400123456",
  "employer_abn": "12345678901",
  "super_consent": true,
  "payroll_consent": true
}

Payroll Check API

POST /payroll_check

Validates a person's identity against Australian payroll records.

Validates a person's identity against Australian payroll records. Each input field comes back as MATCHED or UNMATCHED (name, date of birth, middle name, address, email, phone, employer ABN). Gives you a useful employment-data signal for KYC, particularly for thin-file individuals who don't have a credit history yet.

Request Schema 5 params
consent
Required
boolean

Individual's consent to search payroll records.

first_name, last_name, birth_date
Required
mixed

Minimum required for a valid lookup.

middle_name
Optional
string

Optional Middle name.

address
Optional
object · (street_address, suburb, state, postcode)

Address components for cross-matching.

email, phone, employer_abn
Optional
string

Additional fields evaluated for match outcome.

Example Request
{
  "first_name": "John",
  "middle_name": "James",
  "last_name": "Doe",
  "birth_date": "1990-01-01",
  "address": {
    "street_address": "4/123 Fake Street",
    "suburb": "Fakeville",
    "state": "VIC",
    "postcode": "3987"
  },
  "email": "john@example.com",
  "phone": "0400123456",
  "employer_abn": "12345678901",
  "consent": true
}

Super Check API

POST /super_check

Validates identity details against Australian superannuation records.

Validates identity details against Australian superannuation records. Per-field MATCHED / UNMATCHED responses across name, DOB, middle name, address, email, phone and employer ABN. Gives you an independent identity signal sourced from the super system, which covers nearly every working Australian.

Request Schema 7 params
consent
Required
string

Individual's consent to search super records.

first_name, last_name, birth_date
Required
mixed

Minimum required for a valid lookup.

middle_name
Optional
string

Optional Middle name

address
Optional
string

street_address, suburb, state, postcode

email
Optional
string

Additional fields evaluated for match outcome.

phone
Optional
integer

Additional fields evaluated for match outcome.

employer_abn
Optional
string

Additional fields evaluated for match outcome.

Example Request
{
  "first_name": "John",
  "middle_name": "James",
  "last_name": "Doe",
  "birth_date": "1990-01-01",
  "address": {
    "street_address": "4/123 Fake Street",
    "suburb": "Fakeville",
    "state": "VIC",
    "postcode": "3987"
  },
  "email": "john@example.com",
  "phone": "0400123456",
  "employer_abn": "12345678901",
  "consent": true
}

Sanctions

2 endpoints

PEP / Sanction Bulk Search API

POST /pep_sanction_checks

The bulk version of PEP / Sanction Search.

The bulk version of PEP / Sanction Search. Submit multiple individual, company or vessel screens in one call, sharing the search type, similarity threshold and country filters across all of them. Suited to periodic batch screening of customer registers, supplier lists and counterparty databases.

Request Schema 2 params
Shared config: search_type, pep_countries, sanction_countries, max_results, similarity_threshold, pep_sanction_extended_result
Required
mixed

Applied to every request in the batch.

requests
Required
array

Individual, company or vessel checks. Each one can carry a check_id for result correlation.

Example Request
{
  "search_type": "broad_search",
  "pep_countries": ["au"],
  "sanction_countries": ["au"],
  "max_results": 20,
  "similarity_threshold": 80,
  "pep_sanction_extended_result": true,
  "requests": [
    {
      "check_id": "abcd123456789",
      "first_name": "Phil",
      "last_name": "Smith",
      "birth_date": "1938-10-24"
    }
  ]
}

PEP / Sanction Search API

POST /pep_sanction_check

Screens individuals, companies and vessels against global PEP (Politically Exposed Persons) and sanctions lists.

Screens individuals, companies and vessels against global PEP (Politically Exposed Persons) and sanctions lists. Search modes run from narrow exact-match through to broad partial-match, with configurable similarity thresholds and country-scoped filters. The response gives you matched sources, similarity scores, and optional extended record data for full investigation context.

Request Schema 10 params
first_name, middle_name, last_name, full_name
Conditional
string

For individuals, supply first and last (or full_name). For companies, use company_name. For vessels, use vessel_name.

company_name
Conditional
string

Search a company entity against sanctions.

vessel_name
Conditional
string

Search a vessel against sanctions.

birth_date
Optional
string

Individual's birth date.

search_type
Required
string

narrow_search (exact first + last + DOB), medium_search (exact last + DOB year + partial others), or broad_search (partial everything).

pep_countries
Optional
array · array of country codes

Scope PEP records to specific countries.

sanction_countries
Optional
string · array of country codes

Scope sanctions to specific countries.

similarity_threshold
Optional
integer · (0 to 100)

Default 80.

max_results
Optional
string · (1 to 100)

Default 20.

pep_sanction_extended_result
Optional
boolean

Return full extended dataset details for each match.

Example Request
{
  "first_name": "Phil",
  "last_name": "Smith",
  "birth_date": "1938-10-24",
  "search_type": "broad_search",
  "pep_countries": ["au"],
  "sanction_countries": ["au"],
  "similarity_threshold": 80,
  "pep_sanction_extended_result": true
}

Global Data Check

1 endpoint

Global Data Check API

POST /globaldata_check

The most detailed identity-matching endpoint in the platform.

The most detailed identity-matching endpoint in the platform. You send a person's identity attributes (names, address parts, DOB, up to four phones and four emails) and it returns a per-field outcome map for every input. Supports a graded match ladder (exact / alias / partial / fuzzy), multi-candidate responses, error tolerance, and configurable per-name matching policies. Use it when you need to know not just whether identity matched, but exactly how.

Request Schema 14 params
last_name
Required
string

The only required field. Everything else is optional.

first_name, middle_name
Optional
string

Optional name parts. Match outcomes graded as match, alias_match, partial_match, fuzzy_match, or no_match.

birth_date
Optional
date · YYYY-MM-DD.

Date of Birth.

gnaf_id
Optional
string · GAVIC421647320 or GANT_717247498

GNAF identifier. Mutually exclusive with full_address and the address parts.

full_address
Optional
string

Free-text address. Mutually exclusive with gnaf_id and the parts.

street_address, suburb, state, postcode
Optional
string

Individual address parts. Any combination can be supplied. They don't all have to be there together.

phone, phone2, phone3, phone4
Optional
string · 0NSN or E.164 format

Up to four phones (with or without leading +).

email, email2, email3, email4
Optional
string

Up to four emails.

return_multiple_candidates
Optional
boolean

Return up to five best-first candidates instead of a single best.

ignore_errors
Optional
boolean

Soft-drops fields that fail validation and reports them as not_used instead of failing the request with a 400.

include_deceased
Optional
boolean

Include deceased records in the candidate pool. Defaults to false.

first_name_matching
Optional
array · Default ["exact"].

Accepted match types for first_name: exact, alias, partial, fuzzy.

middle_name_matching
Optional
array · middle_name does not gate candidates.

Same options for middle_name.

last_name_matching
Optional
array · Exact or fuzzy.

Adding fuzzy widens the candidate search to metaphone-equivalent surnames sharing a leading letter

Example Request
{
  "first_name": "John",
  "middle_name": "James",
  "last_name": "Doe",
  "birth_date": "1990-01-01",
  "full_address": "4/123 Fake Street, Fakeville VIC 3987",
  "phone": "0400123456",
  "email": "john@example.com",
  "first_name_matching": ["exact", "alias"],
  "return_multiple_candidates": false,
  "ignore_errors": false,
  "include_deceased": false
}

ID Pass

3 endpoints

Cancel an ID Pass API

POST /idpass/cancel

Cancels an in-flight ID Pass.

Cancels an in-flight ID Pass. Only passes in new, opened or in_progress status can be cancelled. Terminal statuses (complete, expired, failed, cancelled) return an error. A fee refund applies if no verification steps had been taken yet (status still new or opened). Cancelling after any verification activity doesn't refund.

Request Schema 1 param
id
Required
uuid

The ID Pass to cancel.

Example Request
{
  "id": "fe4291ca-d831-4760-96df-c9cb03b3cd95"
}

Create an ID Pass API

POST /idpass/register

Generates a secure, configurable identity verification link for a customer.

Generates a secure, configurable identity verification link for a customer. ID Pass supports Australian driver licences, Australian passports, foreign passports with an Australian visa, Centrelink cards and Medicare cards. The flow routes through the DVS, with optional face liveness, biometric document-photo matching, customer-supplied ID photo, webhook event notifications, and configurable image retention. Sensitive fields are encrypted at rest using a per-pass cipher key that's returned once and never logged.

Request Schema 11 params
link_validity_days
Optional
integer · (1 to 14)

How many days the link stays live. Default 7.

image_retention_days
Optional
integer · (0 to 5000)

How many days to retain captured images. 0 deletes them on completion. Default 0.

check_liveness
Optional
boolean

Whether to run face liveness during the flow.

document_1_allowed_types, document_2_allowed_types, document_3_allowed_types
Optional
array

Allowed document types per slot: licence, passport, medicare, visa, centrelink.

document_verification
Optional
enum

dvs (full DVS verification, requires DVS Identity OAC), basic (format-only validation), or idsp (Global Data acts as IDSP on the customer's behalf, requires liveness plus IDSP enrolment). Default dvs.

require_id_photo
Optional
boolean

Require a customer-supplied ID photo.

id_photo_purpose
Conditional
string · (3 to 255 chars)

Required when require_id_photo is true. Shown on the photo capture page (for example "the SampleCo Membership Card").

webhook_url
Optional
url

Webhook receiver for lifecycle events.

webhook_events
Optional
array

Which events to notify on: opened, in_progress, complete, expired, failed, cancelled.

return_url
Optional
url

Page to link to from the completion screen.

requested_identity
Optional
object

Customer identity to be verified. Optional first_name, middle_name, last_name, date_of_birth. At least one of first_name or last_name is required if the object is supplied.

Example Request
{
  "link_validity_days": 3,
  "image_retention_days": 5,
  "check_liveness": true,
  "document_1_allowed_types": ["licence", "passport"],
  "document_2_allowed_types": ["licence", "passport"],
  "document_verification": "dvs",
  "require_id_photo": true,
  "id_photo_purpose": "the SampleCo Membership Card",
  "webhook_url": "https://example.com/webhook",
  "webhook_events": ["opened", "in_progress", "complete", "expired", "failed", "cancelled"],
  "return_url": "https://example.com/return",
  "requested_identity": {
    "first_name": "John",
    "middle_name": "Andrew",
    "last_name": "Johnson",
    "date_of_birth": "1980-01-01"
  }
}

Read an ID Pass API

POST /idpass/details

Retrieves the full result of an ID Pass.

Retrieves the full result of an ID Pass. You get validation outcomes, biometric results, captured document images, OCR data, and the verified identity. Supply the cipher key returned at registration to receive decrypted values, or omit it and decrypt locally. Optional flags let you pull debug logs, document detail and captured images.

Request Schema 5 params
id
Required
uuid

The ID Pass identifier returned from register.

cipher_key
Optional
string

Supply to receive decrypted sensitive fields. Omit to receive encrypted payloads for local decryption.

return_logs
Optional
boolean

Include the debug log of user steps.

return_images
Optional
boolean

Include captured images (within retention window).

return_documents
Optional
boolean

Include full OCR and validation detail for each document.

Example Request
{
  "id": "fe4291ca-d831-4760-96df-c9cb03b3cd95",
  "cipher_key": "IHm81bkcMsTL7J1ilxhDNE59+p5OQkvUJ3mZQhlUNHA=",
  "return_logs": true,
  "return_images": true,
  "return_documents": true
}

Court Check

2 endpoints

Court Check API

POST /court_check

Searches Australian court records against an individual or company name and state.

Searches Australian court records against an individual or company name and state. Supports summary reports (count by type) or detailed reports (full record list), scoped to civil, criminal, or both listings. Used in KYC, EDD, supplier due diligence and litigation pre-screening.

Request Schema 8 params
type
Required
enum

name (individual) or company.

report
Required
enum

summary (counts) or detail (full records).

listing
Required
enum

civil, criminal, or all.

name_first, name_middle, name_last
Conditional
string

Required for type=name summary reports.

name_full
Conditional
string

Required for type=name detailed reports. Format is "LAST, FIRST MIDDLE".

company
Conditional
string

Required for type=company.

state
Optional
enum

ACT, NSW, NT, QLD, SA, TAS, VIC, WA. Omit to search all states.

max_results, first_result
Optional
integer

Pagination.

Example Request
{
  "type": "name",
  "report": "summary",
  "listing": "civil",
  "name_first": "Michael",
  "name_last": "Raymond",
  "state": "VIC",
  "max_results": 10,
  "first_result": 0
}

Court Check Multiple API

POST /court_check_multiple

The bulk version of Court Check.

The bulk version of Court Check. Up to 20 requests in a single call, sharing report type, listing, pagination and an optional start date across all items. Suited to batch screening of customer rosters, supplier lists or director groups.

Request Schema 2 params
Shared config: report, listing, max_results, first_result, optional start_date
Required
string

Applied across all requests in the batch.

requests
Required
array · (1 to 20 items)

Each item carries an optional check_id plus type and the right name or company fields, with an optional state filter.

Example Request
{
  "report": "summary",
  "listing": "all",
  "first_result": 1,
  "max_results": 10,
  "requests": [
    { "check_id": "name_check_001", "type": "name", "name_first": "Michael", "name_last": "Raymond", "state": "VIC" },
    { "check_id": "company_check_002", "type": "company", "company": "Samplemart", "state": "VIC" }
  ]
}

Business Intelligence

2 endpoints

Create a Business Intelligence Request API

Experimental
POST /business_intelligence

Pulls together a deep-dive intelligence report on the business behind an ABN.

Pulls together a deep-dive intelligence report on the business behind an ABN. The report combines ABN status and history, ACN data, recent ASIC documents, business names, domains, websites, ANZSIC code, AUSTRAC remitter details and a generated summary. The query takes a few minutes to compile. Queue it with this endpoint, then poll the retrieve endpoint with the returned request_uuid.

Request Schema 1 param
abn
Required
string

The 11-digit ABN to investigate.

Example Request
{
  "abn": "12345678901"
}

Retrieve a Business Intelligence Request API

Experimental
GET /business_intelligence/{request_uuid}

Retrieves the result of a queued Business Intelligence request API .

Retrieves the result of a queued Business Intelligence request API . Returns pending, processing, complete or failed status. When complete, the response contains the full intelligence payload: ABN history, ACN data, recent ASIC documents, business names, domains, websites, ANZSIC code, AUSTRAC remitter details and a generated business summary.

Request Schema 1 param
request_uuid
Required
uuid · (path parameter)

The request UUID returned by the create call.

Example Request
GET /business_intelligence/fe4291ca-d831-4760-96df-c9cb03b3cd95

ASIC

8 endpoints

ASIC Banned Persons Search API

POST /asic_banned_persons

Searches the ASIC register of banned persons specifically.

Searches the ASIC register of banned persons specifically. Covers AFS banned/disqualified, banned futures representatives, banned securities representatives, credit banned/disqualified, and disqualified directors. Same search-mode and similarity-threshold logic as the broader Banned and Disqualified Person Search, but scoped to ASIC-sourced data only.

Request Schema 4 params
search_type
Required
enum

narrow_search, medium_search or broad_search.

banned_types
Optional
array · strings

afs_banned_disqualified, banned_futures, banned_securities, credit_banned_disqualified, disqualified_director.

similarity_threshold
Optional
number · (0 to 100)

Default 80.

requests
Required
array · objects

Bulk-style array with check_id, first_name, middle_name, last_name.

Example Request
{
  "search_type": "medium_search",
  "banned_types": ["afs_banned_disqualified"],
  "similarity_threshold": 80,
  "requests": [
    {
      "check_id": "abcd123456789",
      "first_name": "Phil",
      "middle_name": null,
      "last_name": "Smith"
    }
  ]
}

ASIC Extract API

POST /asic_extract

Orders a full ASIC company or person extract.

Orders a full ASIC company or person extract. Supports current, historical and relational extract types for companies. Current or historical for persons. The job is queued and returns an api_reference. Poll the retrieve endpoint until the extract payload is read

Request Schema 9 params
type
Required
enum

company or person.

extract_type
Required
enum

Companies: current, historical, or relational. Persons: current or historical only.

abn
Conditional
string

Required for company when ACN isn't supplied. 11 digits, whitespace ignored.

acn
Conditional
string · 9 digits.

Required for company when ABN isn't supplied.

person_id
Conditional
string

Required for person extracts. From asic_extract_person_search.

additional_person_ids
Optional
array · (unique)

Linked ASIC person IDs from the search result. Don't repeat the primary person_id.

search_id
Conditional
string

Required for person extracts. From the search response.

name
Conditional
string

Required for person extracts. Uppercase legal name matching the search result.

birth_date
Conditional
date

Required for person extracts. From the search result.

Example Request
{
  "type": "company",
  "extract_type": "current",
  "abn": "32111111114"
}

ASIC Extract Company Search API

POST /asic_extract_company_search

Finds the ASIC identifiers you need when ordering a company extract via /asic_extract.

Finds the ASIC identifiers you need when ordering a company extract via /asic_extract. Supports ABN, ACN and free-form name search modes, auto-detected from the input format. Name searches accept registration status filters (registered / deregistered / all) and optional postcode or state filters to narrow large name-match result sets.

Request Schema 5 params
search
Required
string

Company name, ABN, or ACN. Whitespace ignored for numbers. Letter casing ignored for names.

max_results
Optional
integer

Max results for name searches. Default 20. Ignored for ABN/ACN lookups.

status
Optional
enum

registered, deregistered, or all (default). Ignored for ABN/ACN.

postcode
Optional
string · (4 chars)

Limits name searches to registered offices in that postcode or neighbouring postcodes.

state
Optional
string

State code filter for name searches. If both postcode and state are supplied, only postcode applies.

Example Request
{
  "search": "ACME CORPORATION PTY LTD",
  "max_results": 25,
  "status": "registered"
}

ASIC Extract Person Search API

POST /asic_extract_person_search

Finds the ASIC person_id identifiers you need to order a full person extract.

Finds the ASIC person_id identifiers you need to order a full person extract. You send legal name, date of birth and extract type. The response is matched ASIC identities, including any linked person IDs (where someone has the same name and DOB recorded across different shareholdings, for example). Pass those linked IDs through to the extract call so the resulting extract stitches together every related role

Request Schema 5 params
first_name
Required
string

First given name. Combined with middle_name, maximum three given names allowed.

middle_name
Optional
string

Optional middle names.

last_name
Required
string

Family name as recorded with ASIC.

birth_date
Required
date · YYYY-MM-DD

Must be after 1900-01-01.

extract_type
Required
enum

current (people with current roles or shareholdings) or historical (includes ceased roles).

Example Request
{
  "first_name": "John",
  "middle_name": "Michael",
  "last_name": "Doe",
  "birth_date": "1980-05-15",
  "extract_type": "historical"
}

ASIC ID Check API

POST /asic_id_check

Verifies an individual against the ASIC officeholder and shareholder register using their name and date of birth.

Verifies an individual against the ASIC officeholder and shareholder register using their name and date of birth. The response is a compact match_results summary telling you whether the details match an ASIC record, without exposing PII. Use it when you need to confirm a person is on the ASIC register without ordering the full extract.

Request Schema 4 params
first_name
Required
string

First given name.

middle_name
Optional
string

Middle names. Soft-matched (doesn't gate the result).

last_name
Required
string

Family name.

birth_date
Required
date · YYYY-MM-DD.

Must be after 1900-01-01.

Example Request
{
  "first_name": "John",
  "middle_name": "Michael",
  "last_name": "Doe",
  "birth_date": "1980-05-15"
}

ASIC Search API

POST /asic_search

Searches the ASIC register for a company or business name.

Searches the ASIC register for a company or business name. You can look up by number (ABN, ACN, or state business registration number) for a direct hit, or by exact business name. Returns the full ASIC profile: identifier, jurisdiction, name, type, class, subclass, status, ABR entity details, registration dates, addresses, and recent ASIC documents.

Request Schema 2 params
number
Conditional
string · (format JURISDICTION:number, e.g. NSW:1234567).

ABN (11 digits), ACN (9 digits), or state number.

business_name
Conditional
string

Exact business name to search for.

Example Request
{
  "number": "12345678901",
  "business_name": "Acme Services"
}

ASIC Search Bulk API

POST /asic_searches

The bulk version of ASIC Search.

The bulk version of ASIC Search. Submit multiple company or business-name lookups in one call, with an optional check_id for result correlation. Suited to portfolio onboarding, supplier roster checks and periodic register hygiene.

Request Schema 3 params
requests
Required
array

Array of search items.

requests[].check_id
Optional
string

Optional correlation ID.

requests[].number, requests[].business_name
Conditional
string

Same input options as the single ASIC Search.

Example Request
{
  "requests": [
    {
      "check_id": "abcd123456789",
      "number": "12345678901",
      "business_name": "Acme Services"
    }
  ]
}

Retrieve ASIC Extract API

GET /asic_extract/{api_reference}

Polls the status of an ASIC extract previously queued via POST /asic_extract.

Polls the status of an ASIC extract previously queued via POST /asic_extract. Returns 202 while still processing, 200 with the full JSON payload when complete. Append ?pdf=true to get a formatted PDF copy instead of JSON. Retrieval calls aren't billable, so you can poll until the extract is ready without extra cost.

Request Schema 2 params
api_reference
Required
uuid · (path)

Reference returned by the order call.

pdf
Optional
boolean · (query)

When true, returns a PDF document (application/pdf) instead of JSON

Example Request
GET /asic_extract/fe4291ca-d831-4760-96df-c9cb03b3cd95
GET /asic_extract/fe4291ca-d831-4760-96df-c9cb03b3cd95?pdf=true

Company Risk

3 endpoints

ASIC Company Search (Risk) API

POST /asic_company_search

Finds the ASIC identifiers needed to order a Company Risk report.

Finds the ASIC identifiers needed to order a Company Risk report. Same input modes as the extract company search: ABN, ACN, or free-form name, with optional status, postcode and state filters to narrow large name-match result sets.

Request Schema 5 params
search
Required
string

Company name, ABN, or ACN.

max_results
Optional
integer · (1 to 90)

Max results for name searches. Default 20.

status
Optional
enum · all (default).

registered, deregistered, or all (default).

postcode
Optional
string · (4 chars)

: Limits name searches to registered offices in that postcode or neighbouring postcodes.

state
Optional
string

State code filter for name searches.

Example Request
{
  "search": "ACME CORPORATION PTY LTD",
  "max_results": 25,
  "status": "registered"
}

Company Risk Report API

POST /company_risk

Orders a company risk report using an ABN or ACN.

Orders a company risk report using an ABN or ACN. The job is queued and an api_reference is returned. Poll the retrieve endpoint until the report is complete.

Request Schema 2 params
abn
Conditional
string

Supply ABN or ACN, not both. 11 digits, whitespace ignored.

acn
Conditional
string

9 digits.

Example Request
{
  "abn": "94782610486"
}

Retrieve Company Risk Report API

GET /company_risk/{api_reference}

Polls the status of a Company Risk report queued via POST /company_risk.

Polls the status of a Company Risk report queued via POST /company_risk. Returns 202 while still compiling, 200 with the full JSON report when complete. Append ?pdf=true for a formatted PDF. Polling isn't billable.

Request Schema 2 params
api_reference
Required
uuid · (path)

Returned by the create call.

pdf
Optional
boolean · (query)

When true, returns a PDF instead of JSON.

Example Request
GET /company_risk/fe4291ca-d831-4760-96df-c9cb03b3cd95
GET /company_risk/fe4291ca-d831-4760-96df-c9cb03b3cd95?pdf=true

Social

2 endpoints

Social Check API

GET /social_check

Runs a social media intelligence check using phone numbers, email addresses or social profile URLs.

Runs a social media intelligence check using phone numbers, email addresses or social profile URLs. The response is a rich social profile: linked accounts, employment history, education history, interests, skills, location, and a confidence-graded match score. Accepts batch input in a single call (a comma-separated list of phones, emails and profile URLs).

Request Schema 1 param
records
Required
string

Comma-separated list of phones (0NSN or E.164), emails, and/or social media profile URLs. URLs must include a profile path (for example linkedin.com/in/handle) and come from one of 28 supported networks.

Example Request
{
  "records": "test@example.com,0412345678,https://www.linkedin.com/in/johnsmith"
}

Social Contact Expand API

POST /social_contact_expand

Take a contact identifier (phone, email, or social profile URL) and surface additional phones and emails associated with the same person.

Take a contact identifier (phone, email, or social profile URL) and surface additional phones and emails associated with the same person. Each input runs through a two-stage process: a social media check on the original input, plus a universe lookup for each phone or email known for that contact. The response keeps social_search and universe_search blocks separate so you can see which lookup found what. Suppressed phones and emails are excluded.

Request Schema 3 params
requests
Required
array · (1 to 50)

Up to 50 records to expand per call.

requests[].search_id
Optional
string · (≤50 chars)

Optional correlation ID.

requests[].search
Required
string · (≤200 chars)

Phone (0NSN or E.164), email, or social profile URL.

Example Request
{
  "requests": [
    {
      "search_id": "abc-1",
      "search": "john@example.com"
    }
  ]
}

Likeness Check

1 endpoint

Likeness (Face Similarity) Check API

POST /likeness_check

Compares two face images and returns a similarity score plus a threshold-based pass or fail.

Compares two face images and returns a similarity score plus a threshold-based pass or fail. Use it to validate whether an ID document portrait (typically from a driver licence) and a live selfie represent the same individual. The configurable similarity threshold lets you tighten or loosen the pass bar to suit your risk appetite.

Request Schema 3 params
photo
Required
string · (base64 / data URI)

Reference image. Typically the ID document portrait. JPEG or PNG. Max 5 MB.

probe_image
Required
string · (base64 / data URI)

Probe image. Typically a live selfie. JPEG or PNG. Max 5 MB.

similarity_threshold
Optional
number · (0 to 100)

Override the default threshold. If omitted, the system default is applied.

Example Request
{
  "photo": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQ...",
  "probe_image": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQ...",
  "similarity_threshold": 80
}

Liveness Check

2 endpoints

Create a Liveness Check API

POST /liveness_check

Creates a hosted liveness verification link.

Creates a hosted liveness verification link. The end user is guided through a face liveness capture flow in their browser. The result (live human vs spoof attempt) can then be retrieved via the GET endpoint or pushed to your webhook. Configurable link validity, threshold and audit-image retention give you control over the flow without writing your own capture UI.

Request Schema 5 params
return_url
Required
url

Where to redirect the user after the flow completes (or hits a terminal state).

webhook_url
Optional
url

Optional webhook for lifecycle events.

link_valid_mins
Optional
integer · (5 to 30)

Link validity window. Default 10.

threshold
Optional
integer · (0 to 99)

Custom liveness score threshold. Default is the system value (currently 70).

audit_images
Optional
integer · (0 to 4)

Number of additional audit frame images to retain (beyond the single probe image).

Example Request
{
  "return_url": "https://example.com/return",
  "webhook_url": "https://example.com/webhook",
  "link_valid_mins": 10,
  "threshold": 70,
  "audit_images": 2
}

Retrieve a Liveness Check Result API

GET /liveness_check

Retrieves the status or final result of a liveness check using the token returned from the create endpoint.

Retrieves the status or final result of a liveness check using the token returned from the create endpoint. Idempotent and safe to poll. Returns 202 while the check is pending or in progress, 200 when complete (with result object), and 410 if the link expired without completion.

Request Schema 1 param
token
Required
string · (query)

Token from the create endpoint response.

Example Request
GET /liveness_check?token=u2Qe8C9vYl1kP4a7bD6fT3mN9xR5sZ0q

ID Document

1 endpoint

Extract ID Document Data & Face Image API

POST /id_extract

Performs OCR and data extraction on an Australian identity document (passport, driver licence, or Medicare card) and returns parsed identity fields plus a cropped face portrait where available.

Performs OCR and data extraction on an Australian identity document (passport, driver licence, or Medicare card) and returns parsed identity fields plus a cropped face portrait where available. Use it when you're embedding into a custom KYC or onboarding flow and need extracted identity data without committing to the full ID Pass hosted flow.

Request Schema 3 params
document_type
Required
enum

passport, licence, or medicare.

document_photo
Required
string · (base64 JPEG)

Front of the document. JPEG only. Max 16 MB.

document_back
Conditional
string · (base64 JPEG)

Required when document_type is licence. Same format and limits.

Example Request
{
  "document_type": "passport",
  "document_photo": "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQ..."
}

Adverse Media

1 endpoint

Adverse Media Check API

Experimental
POST /adverse_media_check

Searches for adverse media coverage of a person or business.

Searches for adverse media coverage of a person or business. Returns a generated summary, citation links to the source articles, and category tags spanning financial crime, violent crime, organised crime, drug offences, sexual offences, regulatory action, terrorism, scams and fraud, environmental violations, employment violations, and corruption and abuse of office. Built to inform enhanced due diligence on high-risk customers and counterparties.

Request Schema 7 params
type
Required
enum

person or business.

first_name
Conditional
string

Required for person checks.

middle_name
Optional
string · string or null

Optional.

last_name
Conditional
string

Required for person checks.

birth_date
Optional
date · date or null

Optional. Used to filter results when the source mentions an age or age range.

business_name
Conditional
string

Required for business checks.

country
Optional
string · (ISO 3166)

Prefer results from this country.

Example Request
{
  "type": "person",
  "first_name": "John",
  "middle_name": "James",
  "last_name": "Doe",
  "birth_date": "1990-01-01",
  "country": "AU"
}

UK Companies House

7 endpoints

Company House Officer Search API

POST /company_house_officer_search

Searches UK Companies House for officers (directors, secretaries and other officials).

Searches UK Companies House for officers (directors, secretaries and other officials). Fuzzy name match across all UK companies, with an optional date-of-birth filter (year and month only — Companies House doesn't publish the day). Returns matching officer IDs, addresses, appointment counts and role summaries.

Request Schema 3 params
name
Required
string · (≤255 chars)

Officer name to search.

date_of_birth
Optional
date · (YYYY-MM-DD)

Optional DOB filter (YYYY-MM-DD). Day component is accepted but not used. Only year and month match.

max_results
Optional
integer · (1 to 100)

Default 50.

Example Request
{
  "name": "John Smith",
  "date_of_birth": "1975-06-15",
  "max_results": 50
}

Company House Search API

POST /company_house_search

Searches the UK Companies House register for a company by name or company number.

Searches the UK Companies House register for a company by name or company number. The endpoint auto-detects whether the input is a company number (for example 12345678, SC123456, NI012345, FC012345, OC123456) or a free-form name, then dispatches the right search. Returns the company number, registered name, status, type, incorporation date and registered office address.

Request Schema 3 params
company
Required
string

Company name or company number.

is_operational
Optional
boolean · (≤255 chars)

When true, filters results to companies with an active or operational status. Default false.

max_results
Optional
integer · (1 to 200)

Max records returned. Default 200.

Example Request
{
  "company": "Test Company",
  "is_operational": false,
  "max_results": 50
}

Create Company House Officer Report API

POST /company_house_officer_report

Orders a UK officer report.

Orders a UK officer report. Covers personal details, current and former appointments, and disqualification records (when disqualified: true). Async queue and retrieve pattern. The returned api_reference is used to poll the retrieve endpoint.

Request Schema 3 params
officer_id
Required
string

Officer ID returned from the officer search.

disqualified
Optional
boolean

When true, searches the disqualified officers register instead of the standard one.

type
Optional
enum

natural (individual) or corporate. Only used when disqualified is true.

Example Request
{
  "officer_id": "ABC123DEF456",
  "disqualified": false,
  "type": "natural"
}

Create UK Company Report API

POST /company_house_report

Orders a UK Companies House company report.

Orders a UK Companies House company report. The report covers registration details, registered office, current and previous names, officers (directors and secretaries), persons with significant control, filing history summary, accounts information and any charges. The job is queued and async. Poll the retrieve endpoint with the returned api_reference.

Request Schema 1 param
company_number
Required
string · (8 chars)

UK Companies House company number, including any jurisdiction prefix.

Example Request
{
  "company_number": "12345678"
}

Retrieve Company House Report API

GET /company_house_report/{api_reference}

Polls the status of a UK Companies House company report queued via POST /company_house_report.

Polls the status of a UK Companies House company report queued via POST /company_house_report. Returns 202 while compiling, 200 when ready with the full JSON payload. Append ?pdf=true for a formatted PDF copy. Retrieval calls aren't billable.

Request Schema 2 params
api_reference
Required
uuid · (path)

Returned by the create call.

pdf
Optional
boolean · (query)

When true, returns the report as a PDF.

Example Request
GET /company_house_report/fe4291ca-d831-4760-96df-c9cb03b3cd95
GET /company_house_report/fe4291ca-d831-4760-96df-c9cb03b3cd95?pdf=true

Retrieve UK Officer Report API

GET /company_house_officer_report/{api_reference}

Polls the status of a UK officer report queued via POST /company_house_officer_report.

Polls the status of a UK officer report queued via POST /company_house_officer_report. Returns 202 while compiling, 200 when ready with the full JSON payload: appointments, personal details and disqualifications. Append ?pdf=true for a PDF copy. Retrieval calls aren't billable.

Request Schema 2 params
api_reference
Required
uuid · (path)

Returned by the create call.

pdf
Optional
boolean · (query)

PDF response when true.

Example Request
GET /company_house_officer_report/fe4291ca-d831-4760-96df-c9cb03b3cd95
GET /company_house_officer_report/fe4291ca-d831-4760-96df-c9cb03b3cd95?pdf=true

UK Company House Document API

GET /company_house_document/{documentId}

Retrieves a specific UK Companies House document by its document ID.

Retrieves a specific UK Companies House document by its document ID. The document ID is usually pulled from a company report's filing history. Documents come back as PDF and cover annual accounts, confirmation statements, articles of association, certificates of incorporation, change of director notifications and similar filings.

Request Schema 1 param
documentId
Required
string · (path)

The unique document ID from a company's filing history.

Example Request
GET /company_house_document/DOC123456789
HTTP Status

Response Codes

Every endpoint returns one of the HTTP status codes below. The exact response body for each status is documented on the relevant endpoint page.

200

OK

The request was successful. The response body contains the result payload for the endpoint.

400

Bad Request

A required input parameter is missing or malformed. Check the request body and query string against the endpoint schema.

401

Unauthorized

The request is not authorized. Common causes: API Key Inactive, Account Inactive, Account Expired, or IP Restricted.

402

Insufficient Credit

The account has run out of credit and cannot process this request. Top up the account or contact sales.

403

No Access

The API key has no permission to process this request. Contact your account administrator to enable the relevant endpoint scope.

429

Rate Limited

The request rate limit has been reached. Inspect the x-ratelimit-remaining response header and back off until the window resets.

503

Service Unavailable

An upstream dependency (e.g. DVS) returned a system error. The request was not successful and should be retried later.

5XX

Internal Error

An internal system error occurred. All 5xx errors generate an internal audit trail and automatic investigation ticket.

Throttling

Rate Limits

Every response includes rate-limit headers. Inspect them to throttle your integration before the limit is breached. When the limit is exceeded the API returns a 429 Rate Limited response and rejects further requests until the window resets.

x-ratelimit-limit

Maximum requests permitted per time window.

x-ratelimit-remaining

Number of requests remaining in the current window.

Release Notes

Versioning & Changes

The Global Data API uses a major-version path prefix (e.g. /api/v2). Breaking changes are introduced in a new major version. Backwards-compatible additions, such as new optional response fields, are made within the current major version. Subscribe to release notes for advance notice of deprecations.

Need a hand with integration?

Our technical team can help with implementation questions, error investigation, and architecture review.

sales@globaldata.net.au
help FREQUENTLY ASKED QUESTIONS

Common Questions About Our API

Our RESTful API is designed to make integration into your software effortless and seamless.

rocket_launch Implementation

What are the benefits of using an API for my business?

add

The benefits of using an API for your business can include streamlining operations, automating processes and gaining access to new data sources.

rocket_launch Implementation

How does an API integrate with my current systems and processes?

add

Our API can be easily integrated with your current systems and processes through simple API calls and webhooks.

rocket_launch Implementation

What kind of data can I access through the API?

add

Our API allows you to access a wide range of data, including consumer information, market insights and demographics

shield_lock Security

How does your API handle security and data privacy?

add

Our API uses industry-standard security protocols to ensure that your data is kept safe and secure.

rocket_launch Implementation

Can you provide examples of businesses similar to mine that have successfully integrated your API?

add

Yes, we have a diverse range of clients across various industries that have successfully integrated our API into their business operations.

rocket_launch Implementation

Are there any limitations or usage restrictions on the API?

add

There may be certain usage restrictions and limitations based on your specific plan or subscription. We recommend reviewing the API documentation or speaking with our team for more information.

Trusted & Compliant Data Solutions

We recognise the vital need for reliable, privacy-compliant data in today’s landscape. Our solutions provide you access to billions of data points, drawing from a wide range of trusted sources, including AML-CTF data, credit bureau data, superannuation and payroll data, government authoritative data, high-net asset data, as well as insurance and treasury data. Our data ensures that clients receive the most accurate, reliable, and trustworthy information available

  • check_circle Direct-to-source verifications
  • check_circle Real-time dynamic updates
  • check_circle Continuous quality assurance

50 M+

Phone & Email Records

40 M+

Adverse Court records

980 M+

Social Media & Employment Records

18 M+

Real Estate Records

7 M+

Deceased Records

2 BN+

Australian Universe Record

Our Products

A comprehensive suite of verification and data enrichment tools engineered to protect your platform.

radar

WatchEye

WatchEye brings everything together, including real-time KYC/KYB alerts, ongoing monitoring, plus identity, document, and biometric verification. It is an all-in-one customer onboarding system.

Program Active
Identity Verification Passed
Screening Clear
Monitoring Configured
Explore WatchEye arrow_forward
id_card

IDFEX ID Check

IDFEX provides fast, one-to-one Australian identity, document, and data verification checks, in an easy-to-use SaaS platform. Instantly verify government IDs online.

Identity Verified
check_circle Customer Data Verified
check_circle ID Documents Authenticated
check_circle AML/CTF Checks Passed
Explore IDFEX ID Check arrow_forward
mobile_camera_front

ID Pass

ID Pass lets customers verify their identity and biometrics on their smartphone easily while keeping full control of their data. Generate and send your customers a link to verify themselves.

Self Customer Identity Verification
face
Match 99.2%
Explore ID Pass arrow_forward
deceased

Australian Death Check

The Australian Death Check is Australia’s only official national death data source. Our platform provides accurate, compliant, and instant access to millions of death records.

Verify & Remove Deceased Records
> Establishing secure connection...
> Connected to National Registry
> Querying records
> Status: CLEARED
> Latency: 42ms
Explore Australian Death Check arrow_forward
conditions

Caspar KYC

CASPAR is Australia’s top data tool for finding, verifying, and identifying consumers. It uncovers hidden KYC data with rich background and contact details on your customers.

Precision Search Functions
check_circle Verify KYC and KYB entities
check_circle Reveal critical ECDD data
check_circle Investigate High-Risk Profiles
check_circle Discover hidden connections
Explore Caspar KYC arrow_forward
code_blocks

API

Our RESTful API connects smoothly with all software environments, providing tailored, pre-configured, and ready-to-use queries within our SaaS systems. Built to address data issues and drive automation.

Embed Our API's directly into your existing systems
> const response = await client.verify({
> applicantId: "app_8x92m...",
> document: {
> type: "driver_licence",
> country: "AU",
> images: [frontImage, backImage] } });
Explore API arrow_forward
insights

Insiight Enrichment

Insiight improves customer data quality by verifying, correcting, and enriching records so they remain accurate and useful. Instantly append fresh information across your database.

Automated Data Cleansing & Enrichment
Profile Completion 100%
Data Accuracy High
New Data Appended 100,000
Explore Insiight Enrichment arrow_forward
campaign

Quester Marketing

Quester makes it easy to build targeted Australian marketing lists. Use smart filters to create privacy-compliant campaigns that match your audience. Only pay for the data that you download

Create Targeted B2C Marketing Lists
Campaign Ready group
Segment Matching
Audience: 1.2M
Explore Quester Marketing arrow_forward
enquire now

Ready to see our API in action?

SOME OF OUR TRUSTED CLIENTS

Request a Demo

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Full Name*