Halo Connect

Halo Connect is an Australian healthcare interoperability platform, founded in 2021 and headquartered in Brisbane, Queensland, that makes primary-care data integration simple by exposing on-premise practice management system (PMS) databases through a modern cloud API. Its Halo Link agent and Halo Cloud service let approved software integrators query systems such as Best Practice, Zedmed, and Dental4Windows using either SQL passthrough or a standards-based FHIR R4 (4.0.1) API built toward the AU Base 4.1.0 implementation guide, without maintaining a separate database agent per integration. Halo Connect built the first FHIR API for the Best Practice Premier medical-practice industry. The platform runs on Microsoft Azure hosted in Australia, and access is gated behind a Halo Cloud subscription using Azure API Management subscription keys and, for desktop applications, bearer JWT tokens issued from a token endpoint; there is no self-serve public API.

Halo Connect publishes 5 APIs on the APIs.io network, including FHIR API, Registered Queries API, Sites API, and 2 more. Tagged areas include Healthcare, Australia, FHIR, HL7, and Interoperability.

The Halo Connect catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Halo Connect’s developer surface includes authentication, documentation, API reference, getting-started guide, engineering blog, changelog, sandbox, and 27 more developer resources.

🌐 Visit website 📡 Source on GitHub

57.7/100 strong ▬ flat Agent 29/100 agent ready saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0

2 APIs

Healthcare Australia FHIR HL7 Interoperability EHR Practice Management Primary CareAU BaseHealth Data

Kin Score

Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0

Composite quality — 57.7/100 · strong

Contract Quality 13.6 / 21

Developer Ergonomics 11.2 / 17

Access Clarity 6.3 / 17

Operational Transparency 5.5 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 7.7 / 15

Agent readiness — 29/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/halo-connect: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

AsyncAPI

AsyncAPI

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

LLMsTxt

AgentSkill

WellKnown

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Lifecycle

ErrorCatalog

Conventions

Conformance

Webhooks

DataModel

Access & Security 6

Authentication, authorization, and security posture

DomainSecurity

Authentication

TrustCenter

Compliance

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Operate 4

Status, limits, changes, and where to get help

StatusPage

ChangeLog

Deprecation

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Overlay

Overlay

Source (apis.yml)

aid: halo-connect
url: https://raw.githubusercontent.com/api-evangelist/halo-connect/refs/heads/main/apis.yml
name: Halo Connect
kind: company
description: Halo Connect is an Australian healthcare interoperability platform, founded in 2021 and headquartered in Brisbane,
  Queensland, that makes primary-care data integration simple by exposing on-premise practice management system (PMS) databases
  through a modern cloud API. Its Halo Link agent and Halo Cloud service let approved software integrators query systems such
  as Best Practice, Zedmed, and Dental4Windows using either SQL passthrough or a standards-based FHIR R4 (4.0.1) API built
  toward the AU Base 4.1.0 implementation guide, without maintaining a separate database agent per integration. Halo Connect
  built the first FHIR API for the Best Practice Premier medical-practice industry. The platform runs on Microsoft Azure hosted
  in Australia, and access is gated behind a Halo Cloud subscription using Azure API Management subscription keys and, for
  desktop applications, bearer JWT tokens issued from a token endpoint; there is no self-serve public API.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Healthcare
- Australia
- FHIR
- HL7
- Interoperability
- EHR
- Practice Management
- Primary Care
- AU Base
- Health Data
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.23'
apis:
- aid: halo-connect:halo-connect-fhir-api
  name: Halo Connect FHIR API
  description: Query practice data using FHIR resources.
  humanURL: https://docs.haloconnect.io/halo-cloud/overview/
  baseURL: https://api.haloconnect.io
  tags:
  - FHIR
  properties:
  - type: OpenAPI
    url: openapi/halo-connect-fhir-api-openapi.yml
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/overview/
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/integrator-openapi.html
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/desktop-openapi.html
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/overview/
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/capabilities/
- aid: halo-connect:halo-connect-registered-queries-api
  name: Halo Connect Registered Queries API
  description: The Registered Queries API from Halo Connect — 6 operation(s) for registered queries.
  humanURL: https://docs.haloconnect.io/halo-cloud/overview/
  baseURL: https://api.haloconnect.io
  tags:
  - Registered Queries
  properties:
  - type: OpenAPI
    url: openapi/halo-connect-registered-queries-api-openapi.yml
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/overview/
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/integrator-openapi.html
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/desktop-openapi.html
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/overview/
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/capabilities/
- aid: halo-connect:halo-connect-sites-api
  name: Halo Connect Sites API
  description: Endpoints for practice onboarding and site metadata.
  humanURL: https://docs.haloconnect.io/halo-cloud/overview/
  baseURL: https://api.haloconnect.io
  tags:
  - Sites
  properties:
  - type: OpenAPI
    url: openapi/halo-connect-sites-api-openapi.yml
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/overview/
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/integrator-openapi.html
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/desktop-openapi.html
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/overview/
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/capabilities/
- aid: halo-connect:halo-connect-sql-passthrough-api
  name: Halo Connect SQL Passthrough API
  description: "Send SQL queries to practices as immediate, async or registered queries.\n\n**Immediate queries** are small,\
    \ time-sensitive queries that return a result in seconds. Response size is limited to 8MB.\n\n**Async queries** are queued\
    \ for execution and results can be retrieved later. The workflow is:\n\n  1. **Submit async query** – Creates a query\
    \ and returns a `queryId` on success.\n  2. **Get query status** – Check query status. When complete, includes pagination\
    \ details.\n  3. **Get query result page** – Retrieve result pages using the pagination info from the status response.\n\
    \n**Registered Queries** are also supported. See the [Registered Queries](#tag/Registered-Queries) section for more information."
  humanURL: https://docs.haloconnect.io/halo-cloud/overview/
  baseURL: https://api.haloconnect.io
  tags:
  - SQL Passthrough
  properties:
  - type: OpenAPI
    url: openapi/halo-connect-sql-passthrough-api-openapi.yml
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/overview/
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/integrator-openapi.html
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/desktop-openapi.html
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/overview/
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/capabilities/
- aid: halo-connect:halo-connect-tokens-api
  name: Halo Connect Tokens API
  description: Obtain authorization tokens for desktop applications to authenticate API requests.
  humanURL: https://docs.haloconnect.io/halo-cloud/overview/
  baseURL: https://api.haloconnect.io
  tags:
  - Tokens
  properties:
  - type: OpenAPI
    url: openapi/halo-connect-tokens-api-openapi.yml
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/overview/
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/integrator-openapi.html
  - type: APIReference
    url: https://docs.haloconnect.io/api-reference/desktop-openapi.html
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/overview/
  - type: Documentation
    url: https://docs.haloconnect.io/halo-cloud/fhir-api/capabilities/
common:
- type: CapabilityMap
  url: capabilities/halo-connect-capability-edges.yml
  name: Halo Connect Business Capability Map
- type: AgenticAccess
  url: agentic-access/halo-connect-agentic-access.yml
- type: DomainSecurity
  url: security/halo-connect-domain-security.yml
- type: Authentication
  url: authentication/halo-connect-authentication.yml
- type: Website
  url: https://haloconnect.io/
- type: DeveloperPortal
  url: https://docs.haloconnect.io/
- type: Documentation
  url: https://docs.haloconnect.io/
- type: APIReference
  url: https://docs.haloconnect.io/api-reference/integrator-openapi.html
- type: GettingStarted
  url: https://docs.haloconnect.io/halo-cloud/getting-started/
- type: StatusPage
  url: https://status.haloconnect.io/
- type: TrustCenter
  url: https://haloconnect.io/trust
- type: Blog
  url: https://haloconnect.io/blog
- type: ChangeLog
  url: changelog/halo-connect-changelog.yml
- type: Lifecycle
  url: lifecycle/halo-connect-lifecycle.yml
- type: Deprecation
  url: https://haloconnect.io/sla
- type: ErrorCatalog
  url: errors/halo-connect-error-codes.yml
- type: Conventions
  url: conventions/halo-connect-conventions.yml
- type: Sandbox
  url: sandbox/halo-connect-sandbox.yml
- type: Conformance
  url: conformance/halo-connect-conformance.yml
- type: Compliance
  url: https://haloconnect.io/trust
- type: AsyncAPI
  url: asyncapi/halo-connect-webhooks-asyncapi.yml
- type: Webhooks
  url: asyncapi/halo-connect-webhooks-asyncapi.yml
- type: VulnerabilityDisclosure
  url: security/halo-connect-vulnerability-disclosure.yml
- type: Security
  url: https://docs.haloconnect.io/security/
- type: X-MCPServerCandidate
  url: mcp/halo-connect-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/halo-connect-llms.txt
- type: DataModel
  url: data-model/halo-connect-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Overlay
  url: overlays/halo-connect-integrator-overlay.yaml
- type: Overlay
  url: overlays/halo-connect-desktop-overlay.yaml
- type: WellKnown
  url: well-known/halo-connect-well-known.yml
- type: TermsOfService
  url: https://haloconnect.io/terms-and-conditions
- type: PrivacyPolicy
  url: https://haloconnect.io/privacy-policy
- type: Support
  url: https://haloconnect.io/contact-us
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/halo-connect"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/halo-connect/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/halo-connect/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

Halo Connect

Kin Score

APIs 5

Halo Connect FHIR API

Halo Connect Registered Queries API

Halo Connect Sites API

Halo Connect SQL Passthrough API

Halo Connect Tokens API

Open Collections 2

Halo Cloud API for Desktop Applications

Halo Cloud API for Integrators

Event Specifications 1

Halo Connect Webhooks

Security Posture 4

Halo Connect Authentication

Halo Connect Domain Security

Halo Connect Vulnerability Disclosure

Halo Connect Trust Center

Agentic Access 1

Halo Connect Agentic Access

Resources