Back to Platform API Guides
HealthcarePartner API only· workaround available

Jane App API

Jane App has no public developer API, leaving allied health practices and healthtech teams with no programmatic path to patient records, appointments, billing, or clinical documentation. Integuru can generate a production-ready HTTP API — chat with us to get started.

Backed byY CombinatorFree sandbox trial before production

<3 sec

Response latency per call

99.9%+

Reliability rate on generated APIs

24/7

On-call maintenance on production plans

$0

Sandbox trial before production

What Jane App currently offers publicly

Partner API only

Jane App operates the Jane Developer Platform (JDP), a REST API available exclusively to vetted technology partners who complete an official approval process. Access is not self-serve: there is no open developer account, no sandbox available outside the partner program, and Jane's own Integrations Hub FAQ confirms that API keys are not provided to general users. The JDP covers a subset of clinical and scheduling data for approved extensions. Teams outside the partner program have no programmatic path to patient records, appointments, billing, or clinical documentation through official channels.

Jane App official site

How Integuru fills the gap

Integuru generates a production-ready HTTP API for Jane App without a partner agreement. It maps the authenticated network requests the Jane App web app already makes, handles the login flow including 2FA, covers the branching states real accounts hit, and keeps the API running with 24/7 on-call maintenance on production plans.

Planned endpoints

Actions Integuru could expose

Final scope is confirmed when the integration is built
list_patients

Return a paginated list of patient profiles with demographics, contact information, and insurance coverage details

get_patient_detail

Retrieve the complete record for a single patient including contact details, insurance policies, and appointment history

create_patient

Create a new patient profile with demographic, contact, and insurance information in the practice's Jane App instance

list_appointments

List scheduled appointments filtered by practitioner, date range, and appointment status across the practice

get_appointment_detail

Retrieve the full record for a single appointment including practitioner, location, treatment type, and billing status

create_appointment

Book a new appointment for an existing patient against a specific practitioner and available time slot

list_documents

List clinical forms, intake documents, and chart notes attached to a patient record including type and completion status

upload_document

Upload a clinical or administrative document to a patient record in Jane App's chart management system

get_clinical_notes

Retrieve chart notes and SOAP notes for a patient encounter including note content, treatment details, and practitioner sign-off status

list_claims

Return billing records and insurance claims for a patient or date range with status, insurer, and reimbursement amounts

list_insurance_policies

List insurance policies on file for a patient with insurer name, policy number, and coverage details

...many more

These actions reflect what Integuru would generate based on the workflows Jane App exposes through its web interface.

Need a different Jane App action?

Tell us the workflows and accounts you need. Requested integrations are delivered to a sandbox you can test free before production.

Process

What happens after you book a call

  1. 1Tell us the Jane App workflows you need

    Book a call and list the actions, account types and call volume. There is no separate build fee to start.

  2. 2Integuru builds the API in days

    The team maps the authenticated requests Jane App makes into a direct HTTP API, covering the edge cases you named, and delivers it to a sandbox you test free.

  3. 3Move to production, maintained

    Call documented REST endpoints from your stack, and hand breakage to Integuru: production integrations are maintained around the clock, with auth auto-healing included.

Guide

Jane App integration guide

Overview

Jane App is a cloud-based practice management platform built specifically for allied health: physiotherapy, chiropractic, massage therapy, occupational therapy, mental health, and multi-disciplinary clinics. It is the dominant practice management system for Canadian allied health practices and has a growing user base across Australia, the United Kingdom, and the United States. The platform covers online booking, patient charts, clinical documentation, insurance billing, and practitioner scheduling, all in a single system designed for practices that do not use traditional medical EHR software.

For healthtech companies and clinical AI tools trying to build on Jane App data, the official path is narrow: the Jane Developer Platform (JDP) exists for vetted technology partners, but access requires completing a formal approval process with no self-serve entry point. Jane's own Integrations Hub FAQ is direct that API keys are not available to general users. A telehealth platform whose customers use Jane App for clinical records, a mental health AI tool that needs to read chart notes and push session summaries, or a billing automation product targeting allied health practices faces the same situation: even teams who apply to the JDP partner program encounter a multi-step approval process and coverage gaps in billing, claims, and document management that the partner API does not address.

Integuru generates a production-ready HTTP API for Jane App using direct HTTP requests against the same endpoints the Jane App web application uses internally. Patient records, appointment schedules, clinical notes, billing claims, insurance policies, and documents are all reachable through Integuru's API. The Production plan's 24/7 on-call maintenance handles session management and endpoint changes before they affect your calls. Integuru can be deployed in HIPAA-compliant environments; discuss your compliance requirements when you chat with us.


Why Teams Need This Integration

Jane App's absence of any official API means that the workarounds in use today are universally fragile: manual CSV exports, browser automation scripts that break on every Jane App update, and human-driven data entry between systems. None of those approaches scale past a handful of practices.

Mental health and allied health AI tools. A growing category of products assists allied health practitioners with documentation: AI-generated session summaries, between-session check-in tools, outcome tracking platforms, and care planning assistants. These tools need to read existing chart notes and push new documentation back to the patient record. get_clinical_notes and upload_document make this bidirectional workflow possible without requiring the practitioner to copy and paste between Jane App and a separate tool after every session.

Multi-practice billing and insurance automation. Allied health billing companies and insurance claims automation tools that serve Canadian or Australian practices encounter Jane App as a standard platform in their customer base. list_claims, list_insurance_policies, and get_patient_detail give these platforms structured access to the billing and insurance data they need to process claims, check eligibility, and reconcile reimbursements without exporting from Jane App manually. For a billing platform serving dozens of physiotherapy or chiropractic clinics, a reliable programmatic connection to Jane App is a recurring customer request with no current solution.

Telehealth and care coordination platforms. Telehealth products that serve allied health practitioners frequently need to pull patient schedules and appointment records from Jane App to avoid double-booking, synchronize availability, or track care delivery. list_appointments, get_appointment_detail, and list_patients feed these coordination workflows as live API calls. Practices that run both telehealth sessions and in-clinic appointments through Jane App represent a scheduling coordination problem that manual processes solve badly at scale.

Data portability and practice migration tooling. Allied health practices moving from Jane App to another platform, or migrating patient data to a new system, need structured access to their full patient and clinical record history. list_patients, get_patient_detail, get_clinical_notes, and list_documents give migration tools the data access they need to execute a clean transfer. Jane App's export tools provide flat CSV files that lose relational structure; Integuru's API access preserves it.


Healthcare Workflows This Integration Covers

The eleven planned actions cover the full patient and clinical lifecycle for an allied health practice:

  • Patient management: list_patients and get_patient_detail surface the practice's patient roster with demographics, contact details, and insurance coverage. create_patient supports intake automation and external registration flows that need to write new patient profiles into Jane App.
  • Appointment scheduling: list_appointments and get_appointment_detail return live appointment data with practitioner, treatment type, and billing status. create_appointment gives external booking tools and care coordination platforms write access to the Jane App schedule.
  • Clinical documentation: get_clinical_notes retrieves SOAP notes and chart note content for a patient encounter, including treatment details and practitioner sign-off status. upload_document pushes clinical notes, intake forms, and supporting documentation back to the patient chart.
  • Billing and claims: list_claims returns structured billing records with insurer, reimbursement amounts, and claim status for billing automation and insurance reconciliation tools.
  • Insurance data: list_insurance_policies surfaces insurance policies on file for a patient, the starting data point for eligibility verification and claims processing workflows in allied health billing.

Adjacent Integrations

Integuru already covers the healthcare and EHR vertical in production across multiple platforms, demonstrating that the direct HTTP approach works reliably in clinical environments. The DrChrono integration provides 4 live actions including patient creation, patient listing, medication records, and allergy data. The eClinicalWorks integration covers 5 live actions across patient demographics, insurance data, document management, and patient creation. The Canvas Medical integration provides 2 live actions for modern primary care practices. The NextGen integration delivers 10 live actions across patients, appointments, locations, and calendar resources. The Modmed integration is Integuru's most comprehensive EHR integration with 21 live actions spanning claims, payments, insurance policies, and full patient management.

Live in Healthcare

Integuru already supports these platforms in the same vertical

Live, production-ready integrations, not requests

Good to know

Before you book a call

How long does this take?
Most managed-service integration requests are built within a few days, including the workflows and edge cases you ask for.
What if Jane App changes or breaks?
Every managed integration includes 24/7 on-call maintenance, so your team is never pulled into patching target-platform changes.
What does it cost?
You test the Jane App integration free in a sandbox before paying anything. Production pricing follows the standard Production plan (starts at $499/month, including 24/7 on-call maintenance), scoped to the platforms, workflows and call volume you need.

FAQ

Frequently asked questions