ASIC

ASIC Extract Person Search API

ASIC Extract Person Search locates an individual on the ASIC officeholder and shareholder register from their legal name and date of birth. It returns the ASIC identifiers a person extract requires, together with any linked identities, so the extract that follows covers every role and shareholding recorded against the person.

Matches are drawn from the register held by the Australian Securities and Investments Commission, with the state and suburb on the person's ASIC address
Each match carries the person_id and search_id for ASIC Extract, plus linked identities that share the same name or name and date of birth

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
ASIC Extracts guide and person extract workflow

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

Identifying the right person before ordering their extract

A person extract cannot be ordered from a name alone. ASIC Extract Person Search takes the legal name and date of birth, finds the matching identities on the ASIC register and returns the identifiers that ASIC Extract needs. Because one person can hold several ASIC identities, for example through a joint shareholding, the search also lists the linked identities so the extract can be ordered for all of them at once.

The matching ASIC identities

Each match carries the person_id and search_id, the date of birth on the record, and the state and suburb of the person's ASIC address.

Linked identities

Each match may carry an additional list of linked ASIC person identifiers with the same name, or the same name and date of birth. Their person_id values are passed as additional_person_ids when the extract is ordered.

Which extract the search is for

The extract type sent with the search, current or historical, shapes the search_id returned. A current search returns people with current roles or shareholdings. A historical search also includes ceased roles and can take longer.

How long the identifiers last

The person_id, search_id and any additional identifiers are valid for 24 hours. An extract ordered after that needs a new search.

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 orders the person extract using the identifiers returned here, and Retrieve ASIC Extract collects it. ASIC ID Check confirms a person is on the register without ordering an extract.

ASIC Banned Persons Search API ASIC Extract API ASIC Extract Company Search API ASIC ID Check API ASIC Search API ASIC Search Bulk API Retrieve ASIC Extract API

All ASIC endpoints

Questions

Questions we get asked about the person search

Do we need a developer to implement this?

Yes. The search is the first step of a REST workflow whose results feed ASIC Extract and Retrieve ASIC Extract, so a developer connects the three calls to your system. A sandbox with deterministic test people is provided at no usage cost, so the workflow 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, plus the extract type, current or historical. A middle name is optional. Names must be provided exactly as they appear on ASIC records, with no more than three given names across the first and middle name fields.

What comes back?

A list of matches. Each carries the person_id and search_id to pass to ASIC Extract, the date of birth on the record, the state and suburb of the ASIC address, and an additional list of linked identities with their own person_id, name, state, suburb and date of birth.

Why does one person return more than one identity?

ASIC can hold several person identifiers for the same individual, for example where a shareholding is held jointly. The search lists these under additional. Passing every linked person_id as additional_person_ids when ordering the extract ensures the extract stitches together all associated roles and shareholdings.

Where does the data come from?

Matches are drawn from 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. Data in transit and at rest is encrypted, and retention follows the Australian Privacy Act and the Australian Privacy Principles. Global Data is not a credit bureau and does not create an access footprint on any record.

How many searches can we run?

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

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