ASIC Extract Person Search API

POST
/asic_extract_person_search
LIVE

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

Example Request

POST
request.json
key Auth: BearerAuth
{
  "first_name": "John",
  "middle_name": "Michael",
  "last_name": "Doe",
  "birth_date": "1980-05-15",
  "extract_type": "historical"
}

Request Schema

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).

Available Response Data

6 Data Points
01
fact_check

Array of matches

02
fact_check

Per-match person_id

pass to /asic_extract as person_id

03
fact_check

Per-match search_id

pass to /asic_extract as search_id

04
fact_check

Matched name

full uppercase formatted, birth_date, state, suburb

05
data_object

additional array

linked ASIC person IDs to include in additional_person_ids on the extract call

06
fingerprint

API reference UUID

lock Full API documentation provided after vetting from our compliance team.
By The Numbers

API Data Scale & Coverage tag

Unmatched data depth to power your compliance and verification workflows.

50M+
Phone & Email Records
40M+
Adverse Court Records
2BN+
Australian Universe Records
18M+
Real Estate Records
7M+
Deceased Records
980M+
Social Media & Employment Records
Practical Applications

Technical Use Cases tag

search

Director and officeholder discovery

Resolve an individual's ASIC person_id before ordering a full extract. The necessary first step in any officer-of-companies investigation or due diligence work

link

Surfacing linked identities

Surface related ASIC records (joint shareholdings, for example) via the additional array. Means the downstream extract captures every association, not just the primary identity.

Trust & Assurance

Compliance & Security tag

Enterprise-grade infrastructure audited against the standards your regulators require.

verified_user
ISO 27001 Certified
enhanced_encryption
AES-256 Encryption
public
Australian Data Sovereignty
Integration & Support

Common Questions tag

Everything you need to know about implementation details and compliance infrastructure.

rocket_launch Implementation

Why are there linked person IDs in the response?

add

ASIC sometimes has multiple person records for the same individual (where someone is recorded across different shareholdings, for example). The additional array surfaces these linked IDs so you can pass them through to the extract call via additional_person_ids. That way the resulting extract contains every related role.

Try it Live

API Testing Sandbox tag

Test the ASIC Extract Person Search API directly in your browser with live mock data and see instant results.

rocket_launch Request Sandbox Access

Access to live sandbox environments requires manual approval from our compliance team.

BACK TO TOP