Outbound webhooks — Qliva notifying your external systems in real time when events happen in your clinic — are not yet available. This page describes the planned design and what to use in the meantime.
Outbound webhooks are a roadmap item, not a live feature. There is currently no event dispatch, no signing secret, and no configuration UI for outbound webhooks anywhere in Qliva. Don't build an integration that assumes this exists yet — contact Qliva support if outbound webhooks are a blocker for your integration.
What's planned
The intent is for Qliva to push a JSON payload to a URL you configure whenever a specific event occurs — for example, when an appointment is booked, an invoice is paid, or a patient signs a consent document — instead of your system having to poll Qliva for changes.
Likely candidate events include appointment lifecycle changes, pathology result release, form completion, consent signing, and membership changes. None of this is implemented yet, so treat any event names as provisional.
What Qliva supports today: inbound integrations
Qliva doesn't send outbound webhooks yet, but it does receive webhooks and callbacks from several third-party systems as part of its existing integrations:
| Integration | Direction | What it's for |
|---|---|---|
| Stripe | Inbound | Payment and invoice status updates |
| Tyro | Inbound | In-clinic terminal payment and HICAPS/Medicare claim status |
| Squarespace | Inbound | Storefront order and booking events |
| Shopify | Inbound | Storefront order events |
| Parchment Health | Inbound | prescription.created events for eRx status |
| Medical Objects (HL7) | Inbound | Pathology results and clinical correspondence |
These are all cases where an external system notifies Qliva — the reverse of the outbound webhooks described above. See Pathology HL7 and eRx (Parchment) for details on two of these.
In the meantime
If you need to sync Qliva data to an external system today, options include:
- Using Qliva's existing integrations (Stripe, Tyro, Xero, Squarespace, Shopify) directly, where applicable
- Exporting data via the Admin Portal's reporting/export tools
- Contacting Qliva support to discuss your specific integration need
If outbound webhooks would unblock an integration you're planning, let Qliva support know — real usage requests help prioritise the roadmap.