Payroll and Super Check API

Q: Do I need both consent flags?

At least one of super_consent or payroll_consent has to be true. If you only set one, only that dataset is searched and the other object doesn’t appear in the response.

POST

/payroll_super_check

LIVE

Runs a Payroll Check and a Super Check in a single call, with independent consent flags for each dataset. You get separated super and payroll result objects in the response. Lets your workflow react to a match in either dataset without two round-trips

calendar_today Request a Demo Contact Sales

Home
API
Endpoints
Payroll and Super Check
Payroll and Super Check API

Payroll and Super Check API

Example Request

POST

request.json

key Auth: BearerAuth

{
  "first_name": "John",
  "middle_name": "James",
  "last_name": "Doe",
  "birth_date": "1990-01-01",
  "address": {
    "street_address": "4/123 Fake Street",
    "suburb": "Fakeville",
    "state": "VIC",
    "postcode": "3987"
  },
  "email": "john@example.com",
  "phone": "0400123456",
  "employer_abn": "12345678901",
  "super_consent": true,
  "payroll_consent": true
}

Request Schema

super_consent

Required

boolean

Individual's consent to search super records.

payroll_consent

Required

number

Individual's consent to search payroll records.

first_name last_name birth_date

Required

string

Minimum required for a valid lookup.

middle_name

Optional

string

Optional Middle name.

address

Optional

object · (street_address, suburb, state, postcode)

Address components for cross-matching.

email

Optional

string

Additional fields evaluated for match outcome.

phone

Optional

string

Additional fields evaluated for match outcome.

employer_abn

Optional

string

Additional fields evaluated for match outcome.

Available Response Data

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

Higher-assurance KYC

Match identity against both employment datasets in one call to satisfy stricter KYC controls. Relevant for enhanced due diligence customers, sponsored visa holders and high-value account openings.

compare_arrows

Discrepancy detection

When payroll and super disagree on something like address or employer ABN, that's worth surfacing. Might be a customer in transition, or a data hygiene issue worth investigating.

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.

Filter by topic

help

Compliance Team

Global Data Support

Need help planning your custom integration or understanding our compliance coverage? Our team is here to assist.

rocket_launch Implementation

Do I need both consent flags?

add

At least one of super_consent or payroll_consent has to be true. If you only set one, only that dataset is searched and the other object doesn’t appear in the response.

help_center General

Why might payroll and super give different match outcomes?

add

They’re independent datasets. Payroll updates more frequently (each pay cycle). Super can lag if a person’s address or details have changed. Differences usually mean a stale record on one side, or a person whose details have changed recently.

Try it Live

API Testing Sandbox tag

Test the Payroll and Super 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.