ASIC

ASIC ID Check API

ASIC ID Check confirms whether a person's name and date of birth match a record on the ASIC officeholder and shareholder register. The answer is a match result and nothing more, so a director or shareholder can be confirmed without retrieving their ASIC record.

Checked against the officeholder and shareholder register maintained by the Australian Securities and Investments Commission
The response carries only match or no_match for the person and a separate result for the middle name, with no personal information returned

Get API access Talk to us

For developers

After the technical detail?

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

Request and response schema
Match rules and name normalisation

View developer documentation

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

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

What the check gives you

Confirming a director or shareholder is who they say they are

Onboarding a company often means confirming that the person in front of you is the officeholder or shareholder ASIC has on record. ASIC ID Check takes the name and date of birth and reports whether they match a record on the register. It returns the result and no record, which suits a workflow that needs a yes or no rather than the extract. Where the record itself is needed, ASIC Extract Person Search and ASIC Extract are the calls to use.

Whether the person is on the register

The person result is match when the first name, last name and date of birth all match an ASIC record, and no_match otherwise. A no_match also covers a search too broad to evaluate against a single record.

Whether the middle name agrees

The middle name is reported separately as match, no_match or not_provided. It does not decide the result, because ASIC middle-name records are often missing, an initial only, or partial. A check can pass with a middle name that does not match.

How names are compared

Comparison is exact after normalisation. Case is ignored, accents are transliterated, apostrophes and dots are removed, bracketed content is stripped and repeated spaces are collapsed. Hyphens are significant, so a hyphenated name must be sent as ASIC holds it. There is no fuzzy matching.

No personal information in the response

The match_results object carries no PII. Only the two results and an API reference for the audit trail are returned.

Reading the result

What each answer means for the person in front of you

The person result decides the check. The middle name result is context for your team, not a gate.

Match

The person is on the register

The first name, last name and date of birth supplied match an ASIC officeholder or shareholder record. The middle name result shows whether the middle name also agreed, was different, or was not sent.

No match

No record matched the details

No ASIC record matched the first name, last name and date of birth, or the details were too broad to evaluate against a single record. Check the spelling against the ASIC record, including any hyphen, and the date of birth, then run it again.

What it costs

A monthly subscription, drawn down as you run checks

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

Volume-based pricing
No lock-in contract

How billing works

Subscribe monthly, spend it as credits

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

Talk to sales about volume

Related checks

Others in ASIC

ASIC Extract Person Search and ASIC Extract return the person's actual record, with officeholdings, shareholdings and addresses. ASIC Search confirms the company itself.

ASIC Banned Persons Search API ASIC Extract API ASIC Extract Company Search API ASIC Extract Person Search API ASIC Search API ASIC Search Bulk API Retrieve ASIC Extract API

All ASIC endpoints

Questions

Questions we get asked about the ASIC ID check

Do we need a developer to implement this?

Yes. ASIC ID Check is a REST endpoint that takes a JSON request and returns a JSON response, so a developer connects it to your onboarding system. A sandbox with deterministic test people is provided at no usage cost, so the integration can be built and tested before production keys are issued.

What does our system need to send?

The first name, the last name and the date of birth in YYYY-MM-DD format after 1900-01-01, all required. A middle name is optional. Names should be provided as they appear on ASIC records, with no more than three given names across the first and middle name fields.

What comes back?

A match_results object with two values. The person result is match or no_match. The middle name result is match, no_match or not_provided. An API reference is returned for the audit trail. No personal information is returned.

Why can a check pass when the middle name does not match?

ASIC's middle-name records are inconsistent. It is common for a middle name to be missing entirely, recorded as an initial only, or only partially recorded. The middle name is therefore treated as a soft signal and reported on, while the first name, last name and date of birth decide the result.

Does the check tolerate spelling differences?

No. Comparison is exact after normalisation. Case, accents, apostrophes, dots, bracketed text and extra spaces are normalised on both sides, so O'Donnell and ODonnell match. Hyphens are significant, so Smith-Jones and Smith Jones do not match. There is no fuzzy matching.

Where does the data come from?

The check is run against the officeholder and shareholder register maintained by the Australian Securities and Investments Commission. The reference documentation does not state a refresh cycle for the register.

Is the name and date of birth we send stored by Global Data?

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

Getting started

The first step to access is a conversation

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

Get API access Talk to us

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

Encrypted in transit and at rest

Handled under the Australian Privacy Principles

ISO 27001 Certified