Court Check API

POST
/court_check
LIVE

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.

calendar_today Request a Demo Contact Sales

Example Request

POST
request.json
key Auth: BearerAuth 
{
  "type": "name",
  "report": "summary",
  "listing": "civil",
  "name_first": "Michael",
  "name_last": "Raymond",
  "state": "VIC",
  "max_results": 10,
  "first_result": 0
}

Request Schema

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.

Available Response Data

4 Data Points
01
data_object

Array of court records

summary or detail, depending on report

02
person

Summary records: full_name, total count, listing type, entity type

individual or company

03
monitor_heart

Detail records: case title, court, location, state, case number, listing type, case_title, listing_type, additional_info

04
tag

total_records_available count

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

policy

Enhanced due diligence

Include a court records check as part of EDD on high-risk customers, large transactions or counterparties in regulated industries.

business_center

Pre-engagement supplier and contractor checks

Run a court-records summary on suppliers and contractors before signing engagement letters. Civil disputes and criminal listings come up that warrant investigation.

manage_search

Litigation history checks

Background research on individuals or companies for legal teams, investigative journalism and pre-investment due diligence.

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 the name fields different between summary and detail reports?

add

Summary reports use the structured name_first, name_last and name_middle fields. Detail reports use a single name_full field in “LAST, FIRST MIDDLE” format (for example “DOE, JOHN JAMES”). Don’t mix the two. If name_full is set on a detail report, the structured fields are ignored.

gavel Compliance

How should I use court records in compliance decisions?

add

Court records are returned because a name and state appear in public court records. They’re a signal worth investigating, not a determinative match. The person on the record might not be your subject. Verify before acting on the information.

Try it Live

API Testing Sandbox tag

Test the Court Check 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.

(03) 9948 4089
Request a Demo
BACK TO TOP