Build the Verified Record Into Your Product.

Your product serves the people who hire, roster, or dispatch contractors. Build ComplyFlow’s verified record of the supplier and the Worker into it, through the open REST API and the MCP server, on terms agreed in writing.

Become a Partner Open the API Documentation

A product manager and a software engineer at a standing desk review a dispatch app on a large monitor, a whiteboard of screen sketches behind them, in a converted warehouse office

What Your Product Gains

Compliance Your Users Can Prove, Inside the Screen They Use.

Your users already ask whether the contractor they are about to send is cleared. Build the answer into your product instead of sending them to a second system.

The Worker’s Status, in Your Screen

Inductions, licences, and insurances checked against each Worker, read through documented endpoints and shown where your users already work.

The Supplier’s Status, by ABN

Prequalification, insurances, and certificates on the supplier’s record, with the documents and expiries behind each status.

A Documented API to Build On

REST endpoints, one per module, JWT sign-in, and a test environment for the build before production.

Terms Before the Build

How ComplyFlow appears in your product, the volume it runs at, and what it costs, agreed in writing before your team starts.

How It Builds In

Your Product on the Outside. Our Record Underneath.

Three places the build shows: the token your product holds, the supplier list it reads, and the assistant your customer’s team asks.

A Token Scoped Module by Module.

Your product connects on a personal token made by a ComplyFlow user on your customer’s account. It carries the read or write scopes chosen for each module, and never reaches further than that user’s own permissions and sites.

Read or write, per module
No further than its creator’s permissions
Expires within a year, revoked at once

Security

Permissions · Lena Hoang

Scheme Site Safety Lead · assigned sites: Kwinana Terminal, Port Botany Wharf 7

Sites No accessRRW Assigned sites only
Workers & training No accessRRW Assigned sites only
Suppliers & contractors No accessRRW Entire organisation
Incidents No accessRRWAdmin Assigned sites only
Inspections No accessRRWAdmin Assigned sites only
Forms & permits No accessRRWAdmin Assigned sites only
Risk register No accessRRW Entire organisation
Staff No accessRRW

The Supplier List, Already Verified.

Your product reads the supplier list and each company’s status, with the documents and expiries behind it, so your users choose from contractors the client has already approved.

Supplier list and details
Status per company
Documents and expiries behind each status

Integrations

Suppliers 128

Every contractor company on your panel, measured against the requirements you set.

Add Suppliers

Supplier Categories Status Sites Next expiry

Tallis Civil Pty LtdABN 41 … Civil, High Risk Cleared Kwinana Terminal and 2 others PL insurance, 28 Feb 2027

Southline ElectricalABN 77 … Electrical Pending review Ballarat Line Prequal awaiting review

Harbour Lifts Pty LtdABN 19 … Lifts, High Risk Not cleared Port Botany Workers comp expired 02 Sep

Northgate CleaningABN 58 … Cleaning Cleared Kwinana Terminal and 4 others Modern slavery form, 14 Oct

Ridgeway ScaffoldABN 63 … Scaffold, High Risk Cleared Ballarat Line and 1 other SWMS review, 30 Nov

Your Customer’s Team Asks the Record Too.

Your customer’s own ComplyFlow users can connect the assistant they already use through the MCP server, on a token of their own, and ask which suppliers lapse this month or who is on site. It sees only what that user may see.

ChatGPT, Claude, or Microsoft Copilot
On the user’s own token and permissions
Read-only unless write scopes are added

AI in ComplyFlow

You

Which sites reported incidents this month, and what was the most serious at each?

Assistant

Reading ComplyFlowlist_incidentsget_site

Three sites reported incidents in September. From your ComplyFlow record:

Site	Incidents	Most serious
Marlow Point Terminal	3	Medical treatment
Greyhaven Wharf 9	2	First aid
Wattle Creek Line	1	Near miss

I can read your incidents, inspections, suppliers, workers, risks, plant, sites, and permits with the scopes on your token. This token has read scopes only, so I cannot change anything.

Products That Build It In

Where the Verified Record Belongs Inside a Product.

Any product that hires, sends, or lets in a contractor makes a decision the record can answer.

Rostering & Dispatch

Send only the Workers whose tickets and inductions are current.

See how

Maintenance & Work Orders

Release the job to a supplier the client has approved.

See how

Building & Site Platforms

Show who is on site and whether they were cleared at the gate.

See how

Procurement & Supplier Portals

Put the prequalification outcome beside the vendor record.

See how

Fleet & Plant

Read the plant item’s documents and the operator’s ticket together.

See how

Devices at the Gate

Kiosks, readers, and key cabinets that need one answer at the scan.

See how

See All Integrations

How to Start

From First Call to a Product That Ships It.

Every step is with a person on the ComplyFlow team, and nothing is built until the terms are in writing.

1 A 20-minute call
Your product, your users, and the decision in it that a verified record would answer.
2 We map the build
Which records your product reads, through which endpoints, and what the test environment covers.
3 Terms in writing
How ComplyFlow appears in your product, the volume, and the cost, agreed before your team starts.
4 Build, test, ship
Your team builds against the test environment with ours answering the questions, then goes live.

Worth Reading

Worth Reading Before You Build.

All posts

Become a Partner

Tell Us About Your Product.

A short form, read by a person on the team setting the partner program up. Say what your product does, who uses it, and where a contractor decision sits inside it.

Which records your product would read
What the build looks like on the test environment
Terms in writing before your team starts

All Partner Types

Become a Partner

Start the message box with 'OEM', so it reaches the right person.

Send Message

The form loads from HubSpot. If it does not appear, the button takes you to the contact page.

Questions

Questions OEMs Ask First.

How is building ComplyFlow in different from connecting to it?

A connection sits beside your product, and your customer runs ComplyFlow as well. Building it in puts the record inside your product, so your users see the answer without leaving it. Software companies that connect have their own page.

What can our product read?

Supplier and Worker records, compliance status, documents and expiries, sites, plant, inspections, and more, through the endpoints set out in the API documentation. Which of them your product reads is agreed at the start.

Is there a limit on how much our product can call the API?

Usage limits apply to every account, and use beyond standard needs approval first, as the API fair use policy sets out. That is why the volume is part of the terms agreed before you build.

Who owns the data?

The customer’s record stays the customer’s. Your product reads what the customer’s token allows, within the permissions of the user who made it, and the token can be revoked at once.

Where is the data hosted?

Data is hosted on AWS in Australia. ComplyFlow has held ISO 27001 since 2019, and the security page sets out the rest.

Your Product, With the Answer Built In.

Tell us what your product does and who uses it. The API documentation shows what it could read before you talk to us.

Become a Partner Open the API Documentation

ISO 27001
Hosted on AWS
REST API
MCP Server