Lab testing API
Choosing a lab testing API in Australia
A lab testing API lets your product order tests and receive results without a separate integration per laboratory. Here is what to check, with an Australian lens.
By Benjamin Novakovic, CTO and Co-founderLinkedInPublished
Start with where the labs are
Several well-known lab testing APIs serve US laboratories. Junction and Health Gorilla are examples: they connect to labs in the United States. If your clients collect samples in Australia, the first question is whether the API reaches Australian laboratories and collection centres.
Eirly Health is an Australian company, and its API orders from Australian labs and returns structured results.
What to look for
Lab coverage
Which laboratories can you order from, and which collection centres can your clients walk into? Ask for the list.
Ordering model
Can one request carry commercial tests and Medicare tests ordered under a practitioner's own provider number?
Normalised results
Are results normalised across labs to one biomarker identity? Do you get the lab's own value as well as a value in one agreed unit, so nothing is overwritten?
Report text
Do reports with no individual biomarkers, such as some histology, still arrive whole?
Webhooks
Can you manage subscriptions over the API and look up past events? Are webhooks notifications you answer with a fetch?
Collection centres
Can your product find the nearest centre, with opening hours?
Paging and errors
Is there one paging contract across list endpoints, and a documented list of error codes?
A sandbox
Is there a staging environment with its own keys, so you can build before you commit?
How Eirly Health answers these
- Labs. Healius (Dorevitch, QML, Laverty, Abbott and Western Diagnostic), Sonic Healthcare (Douglass Hanly Moir, Sullivan Nicolaides and Clinipath), Australian Clinical Labs, 4Cyte, NutriPATH, Microba and Fatty Acid Labs, with 4,000+ collection centres.
- Medicare. Medicare referral ordering under a practitioner's own provider number, with provider records and signatures managed through the API.
- Results. A consistent biomarker identity across labs, the lab's own value plus a canonical value, and the lab's report text.
- Developer experience. One paging contract on every list endpoint, webhook management over REST, a staging environment with its own keys and a public read-only developer MCP server.
Details are on the pathology API, lab results API and MCP server pages. Pricing is on request: see API access.
Keep reading
- Pathology API
Referrals, results, webhooks, bundles and collection centres in one REST API.
- Lab results API
Results normalised across labs, with canonical values and the lab's own report text.
- Developer MCP server
Let your coding assistant read the API reference while it writes your integration.
- Guides
LOINC, HL7 v2 and e-requesting in Australia, with sources.
Build on the Eirly Health API.
Start in the staging environment with its own keys, then talk to us about production access. Pricing is on request.