ASIC Extract API

POST
/asic_extract
LIVE

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

Example Request

POST
request.json
key Auth: BearerAuth
{
  "type": "company",
  "extract_type": "current",
  "abn": "32111111114"
}

Request Schema

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.

Available Response Data

2 Data Points
01
fingerprint

api_reference

used to poll /asic_extract/{api_reference} for the payload

02
mail

Acknowledgement message

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

assignment

Extract Full ASIC company record

Order a current, historical or relational extract for any registered company. Feeds downstream KYC, due diligence and litigation processes

history

Extract Historical roles and shareholdings

Historical person extracts include ceased roles and shareholdings. Important for investigating an individual's full ASIC footprint over time.

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

What extract types are available?

add

Companies: current (Current Extract), historical (Current plus Historical Extract), relational (Relational Extract). Persons: current (current roles or shareholdings only) or historical (includes ceased).

rocket_launch Implementation

When do I use additional_person_ids?

add

When the asic_extract_person_search response includes linked person IDs in the additional array. Pass those IDs (not the primary one) in additional_person_ids so the resulting extract stitches together every related role.

Try it Live

API Testing Sandbox tag

Test the ASIC Extract 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