Jane App API and Integration Guide (2026)
CTO & Co-Founder
CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

Jane is a practice management and EMR platform used by allied health clinics, such as physiotherapy, chiropractic, massage and counselling practices. Jane does have an API. It is open only to approved partners, through a program Jane calls Jane Integrations. Jane describes it as "an official, approval-based, API partner program", and states it is "not launching an open, public API".
This guide is for a product lead or buyer who has to connect a product to Jane, and for the engineer who will build it. It covers how a vendor applies and what the Jane Developer Platform exposes. It also covers the limits Jane publishes, what it leaves out, and what Jane's own pages say about prescriptions. If you want a team to scope it with you, see our Jane App integration services. Last checked: Nov 18, 2026.
Jane App API at a glance
| Question | Short answer |
|---|---|
| Who grants access? | Jane. A vendor applies through the partner intake form, and Jane reviews the product, its data flows, privacy and support. Each practitioner then approves the extension on a consent screen. |
| Who signs? | Jane asks PHI-handling partners for a signed Business Associate Agreement and a SOC 2 Type II report not older than 12 months. |
| Are there public documents? | Yes. A Quick Start guide and an API reference at developers.jane.app, with an OpenAPI definition on each page. |
| Which routes exist? | The Jane Developer Platform (JDP) REST API with OAuth 2.0 and PKCE, appointment webhooks, and the Extensions Service. |
| What does it cost? | Jane publishes no partner fee or API fee. |
| How long does it take? | Jane publishes no approval time, and no launch date for the full program. |
| What is the biggest limit? | Appointments are read only. Jane states that "Posting directly into Jane's calendars is not supported." |
What can you build with the Jane App API?
Eight use cases follow. Each points to a row in the read and write table in section 6 (rows R1 to R10). Jane publishes no build times, so this guide gives no build estimate. Build complexity is our own rating. Jane also states it is "not ready to support single-use-case integrations", so a product that does only one of these does not meet that rule.
1. Send reminders and follow-ups when a Jane appointment changes
- Who it is for: patient engagement, reminder and recall products.
- The value: your product hears about a booking, cancellation or reschedule as it happens, and acts on it.
- Build complexity: low to medium.
- How well it works: well. Jane webhooks send APPOINTMENT_BOOKED, APPOINTMENT_CANCELLED, APPOINTMENT_UNCANCELLED and APPOINTMENT_RESCHEDULED. You then read the appointment and patient. See rows R1, R2 and R9.
2. Assign home exercise programs and track them as care plans
- Who it is for: home exercise and rehab software, the category Physitrack and Wibbi serve as official Jane integrations.
- The value: the plan the patient follows at home sits in the Jane record next to the visit.
- Build complexity: medium.
- How well it works: supported. The API creates and updates care plans and care plan activities. See row R4.
3. Write vital signs, lab values and exam findings into the Jane chart
- Who it is for: remote monitoring, device and outcome measure products.
- The value: coded readings land in the patient record without retyping.
- Build complexity: medium.
- How well it works: well. Observations take a category of vital_signs, laboratory or exam, with coded values such as LOINC or SNOMED CT, and can attach uploaded documents. See rows R5 and R8.
4. Keep a patient's medication list current from outside Jane
- Who it is for: supplement and dispensary platforms, pharmacy and medication reconciliation tools.
- The value: the clinician sees what the patient takes, with dose, route, frequency and change history.
- Build complexity: medium.
- How well it works: partly. The API creates and updates medication records with a source of patient_reported, external_provider or clinic_practitioner. It cannot write a record as "prescribed", and it cannot send a prescription. See row R7.
5. Sync allergies for safety checks
- Who it is for: clinical decision support, intake and pharmacy tools.
- The value: one allergy list across your product and Jane.
- Build complexity: low.
- How well it works: well. Allergies can be listed (severe first), created, updated and archived. See row R6.
6. Attach reports and outside documents to the Jane record
- Who it is for: imaging, lab, fax and referral products.
- The value: the PDF or image sits with the record it belongs to.
- Build complexity: low.
- How well it works: supported for PDF, JPEG and PNG up to 50 MB. An uploaded document can be read back only by the user who uploaded it. See row R8.
7. Report on bookings across a multi-location clinic group
- Who it is for: BI and reporting products, and multi-location groups.
- The value: visits, no-shows and cancellations by location, practitioner and treatment.
- Build complexity: medium.
- How well it works: well for scheduling data. Appointments come with state, location, staff member and treatment, and reference lists cover locations, staff, disciplines and treatments. Jane publishes no billing endpoints, so revenue reporting is out of reach. See rows R2 and R3.
8. Look up the right patient from an intake or contact tool
- Who it is for: intake form, referral and contact center products.
- The value: staff find the Jane patient by name, email, phone or patient number.
- Build complexity: low.
- How well it works: supported for reads. POST /patients/search runs a free-text search with the terms in the request body. Patients cannot be created or updated through the API. Jane also states it is not working with AI scheduling tools for now. See row R1.
The eight Jane use cases compared
| Use case | Who it is for | Build complexity (our rating) | Row in the read and write table |
|---|---|---|---|
| 1. Reminders on appointment changes | Engagement products | Low to medium | R1, R2, R9 |
| 2. Home exercise programs as care plans | Rehab software | Medium | R4 |
| 3. Vitals, labs and exam findings | Monitoring and device products | Medium | R5, R8 |
| 4. Medication list from outside Jane | Dispensary and pharmacy tools | Medium | R7 |
| 5. Allergy sync | Safety and intake tools | Low | R6 |
| 6. Reports and documents | Lab, fax and referral products | Low | R8 |
| 7. Booking reports across locations | BI and multi-location groups | Medium | R2, R3 |
| 8. Patient lookup for intake | Intake and contact tools | Low | R1 |
How do you get access to the Jane App API?
You apply to Jane as a software vendor, and Jane decides. Jane's partner post lists the steps: read the JDP API Quick Start Guide and The Jane 10, then "fill out our intake form and we'll get it to the right person". Partners "go through an intake and approval process before they can connect to Jane".
Jane's ground rules for partners
Jane lists five rules for vendors.
- Jane is not ready to support single-use-case integrations.
- Clinics cannot build their own integrations.
- For now, Jane is not working with AI scheduling or AI scribe tools.
- Posting directly into Jane's calendars is not supported.
- Tools that need shared logins or two-factor authentication turned off are not supported.
Jane also says community interest and partner support count when it chooses partners, and that it "can't promise that every partner or tool will be the right fit". Marketing and growth tools are still under review.
Registering the extension
Once Jane accepts you, you give your Jane partnerships contact four things: the extension name, the exact HTTPS redirect URIs (no wildcards), a description, and support contacts. Jane then issues the environment (Partner Development or Production), a client ID, a client secret, the scopes and the identity service URL. The general contact is partnerships@jane.app.
What the clinic side does
Jane's docs name no developer agreement for the clinic to sign. Each practitioner logs in to their clinic and approves your extension's scopes on a consent screen. One authorization covers one practitioner in one clinic.
What does Jane App API access give you?
Two environments. A sandbox realm, jane_partner_sandbox, and the production realm, jane. The API reference runs against a "Partner playground clinic" at jdpdocsdemo.jane.qa.
At each stage you get the scopes Jane granted at registration and nothing more. Each token is tied to one practitioner and one clinic, and adding a scope later means sending the practitioner through consent again. Each clinic has its own database, so every call goes to that clinic's own URL.
What are the ways to integrate with Jane?
Jane documents three technical routes, all behind partner approval.
| Route | What it is | When it fits |
|---|---|---|
| JDP REST API | Version 2026-01-01, OAuth 2.0 authorization code with PKCE, Bearer token per practitioner and clinic | Reading and writing clinical records, reading scheduling data |
| Webhooks | Subscriptions to four appointment events, signed with an HMAC secret | Acting on bookings, cancellations and reschedules |
| Extensions Service | Version 2025-02-28-beta on partner-extensions.janeapp.com, Bearer JWT | Managing your extension listing and reading the catalog of approved extensions |
| Official partner integrations | Integrations Jane lists on its marketplace, such as Fullscript, Physitrack, Claim.MD and TELUS eClaims | When a listed partner already does what the clinic needs |
Jane documents no FHIR or HL7 interface. Jane advises clinics against browser extensions that scrape data and against anything that asks them to turn off two-factor authentication.
What can you read and write with the Jane App API?
All paths below start with /api/2026-01-01 on the clinic's own URL.
| Row | Resource | Read | Write | Endpoints |
|---|---|---|---|---|
| R1 | Patients | Yes | No | GET /patients, GET /patients/{patient_id}, POST /patients/search |
| R2 | Appointments | Yes | No | GET /appointments, GET /appointments/{appointment_id} |
| R3 | Locations, staff, disciplines, treatments, company | Yes | No | GET /locations, /staff_members, /disciplines, /treatments, /company and single-record gets |
| R4 | Care plans and activities | Yes | Create, update | /medical-record/care-plans and /medical-record/care-plans/{care_plan_id}/activities |
| R5 | Observations | Yes | Create, update | /medical-record/observations |
| R6 | Allergies | Yes | Create, update, archive | /medical-record/allergies, DELETE is a soft delete |
| R7 | Medications | Yes, with change history | Create, update | /medical-record/medications, GET /medical-record/medications/{medication_id}/history |
| R8 | Documents | Uploader only | Upload | POST /document-uploads, GET /document-uploads/{document_id} |
| R9 | Webhook subscriptions | Yes | Register, delete | /webhooks, /webhooks/{webhook_id} |
| R10 | Extensions and catalog | Yes | Create, update, delete | /api/2025-02-28-beta/extensions and /catalog/extensions on partner-extensions.janeapp.com |
Does the Jane API expose prescriptions?
Partly. The medication record has prescription fields: a source value of "prescribed", prescription_valid_until, prescription_refills, prescription_days_supply and prescription_reason. On create and update, the source field accepts only patient_reported, external_provider or clinic_practitioner, so a partner cannot write a prescription. No endpoint sends a prescription to a pharmacy.
Prescribing in Jane runs through DoseSpot. Jane announced ePrescribe for US clinics "this winter" as a per-prescriber add-on. Prescriptions written in DoseSpot "sync back to the patient's Medications tab in Jane overnight" and are read-only in Jane once synced. Jane does not say which source value those synced records carry in the API. Ask Jane before you build on it.
How lists, filters and errors work
Lists use cursor paging with page[limit] up to 1,000 and a Base64 page[cursor]. Filters take the form field[operator]=value with eq, gt, gte, lt and lte, and sort takes a minus sign for descending order. Errors come back as an errors array with a message and a JSON Pointer path.
What is not possible with the Jane App API?
- Booking, moving or cancelling appointments. No write endpoint exists, and Jane's rules exclude posting into calendars. The workaround is to send patients to Jane's own online booking.
- Creating or editing patients. Patients are read only.
- Sending a prescription. No eRx endpoint. Prescribing runs inside Jane through DoseSpot.
- Billing, payments and claims. No billing or claim endpoints are published. Claims run through official integrations such as Claim.MD and TELUS eClaims.
- Chart notes and messages. Scopes named conversations, messages and chart_entries:push_to_chart appear in the spec, with no endpoints published for them.
- Clinical events. Webhooks cover appointment events only. To catch clinical changes, poll with an updated_at filter.
- FHIR or HL7. Not documented.
- Clinic-built integrations. A clinic cannot build its own.
What are the Jane App API limits?
Jane publishes these numbers.
| Limit | Value |
|---|---|
| Rate limit | 100 requests per minute per endpoint per clinic. A 429 comes back with Retry-After. |
| Page size | Up to 1,000 records |
| Upload size | 50 MB, PDF, JPEG or PNG |
| Access token | 5 minutes |
| Refresh token | Single use, expires after 30 days unused |
| Scope of one token | One practitioner in one clinic |
Medication history returns every entry with no paging. Date-time filters must be precise to the second.
How much does a Jane integration cost?
Jane publishes no partner fee, API fee or revenue share. Clinics pay for Jane on published plans (Balance, Practice and Thrive), listed on Jane's pricing page. ePrescribe will be a per-prescriber add-on, and its price is not in the announcement.
On the partner side, the main cost is meeting The Jane 10. It asks for a SOC 2 Type II report, a signed BAA, annual penetration testing and 12 months of audit logs. Ask Jane for any fee in writing before you sign.
How long does a Jane integration take?
Jane publishes no review or approval time for partner intake. It gives no launch date for the full program and says it is "already partnering with a small number of early partners". Once you are registered, each practitioner connects in one browser consent step. Ask Jane for the expected review time when you apply.
How do you build a Jane App API integration, step by step?
The build has four stages, and starts after Jane accepts the partner application.
Stage 1. Register the extension
Send Jane the extension name, redirect URIs, description and support contacts, and store the client ID and secret it returns on your server.
Stage 2. Connect a practitioner with OAuth and PKCE
Send the practitioner's browser to Jane's identity service with a code challenge and a state value.
https://<jane_iam_service_base_url>/realms/<realm_name>/protocol/openid-connect/auth
?client_id=<partner_client_id>
&scope=<list_of_api_scopes>
&resource=<jane_clinic_url>
&redirect_uri=<partner_redirect_uri>
&response_type=code
&code_challenge=<random_string>
&code_challenge_method=S256
&state=<random_string>
After consent, exchange the code at /protocol/openid-connect/token with the code verifier. Jane's docs show this response:
{
"access_token": "eyJhbGciOiJSUzI1...",
"expires_in": 300,
"refresh_expires_in": 0,
"refresh_token": "eyJhbGciOiJIUzI1...",
"token_type": "Bearer",
"id_token": "eyJhbGciOiJSUzI1...",
"not-before-policy": 0,
"session_state": "a856fb91-eabc..."
}
Read the clinic domain from the token's aud claim.
Stage 3. Read and write records
Call the clinic's URL with the Bearer token. Jane's example:
GET https://<jane_clinic_url>/api/2026-01-01/medical-record/observations/00491e05-c82f-4171-88cd-1d04e9c5fa7c
HEADER
Authorization: Bearer eyJhbGciOiJSUzI1NiIsIn...
Content-Type: application/json
Writes wrap the record in a data object. A medication needs patient_id, medication_code, status and source.
Stage 4. Listen for appointment events
Register a webhook with an event topic and an HTTPS target URL. Store the signing secret from the response, because Jane returns it only once, and check the HMAC signature on every event. Refresh access tokens before they expire, and send the practitioner through consent again if a refresh fails.
Which Jane App API quirks should you know?
Scope names do not match on medications
The scope list in the spec has medications:read only, while create and update need medications:create and medications:update. Confirm the scopes Jane grants you.
redirect_url or redirect_uri
The token parameter table says redirect_url, and the example body says redirect_uri. Follow the example.
Single-tenant and multi-tenant in one guide
The Quick Start uses both words. Both mean each clinic has its own database.
Documents are private to the uploader
Only the user who uploaded a document can read it back.
Class bookings have no patient
For class bookings, patient_id is null.
Allergy delete keeps the row
Archived allergies leave the default list but stay in the record.
Revoked access lingers
After you revoke a refresh token, the current access token can work for up to 5 minutes.
Two hosts, two versions
The Extensions Service is on its own host and is still a beta version.
Scopes with no endpoints
Conversations, messages and chart entry push have scopes and no published endpoints.
What should you check before you sign with Jane?
Security, as The Jane 10 sets it
Jane expects PHI-handling partners to show:
- a SOC 2 Type II report not older than 12 months, HIPAA and GDPR compliance, and a signed BAA
- AES-256 at rest and TLS 1.2 or higher in transit, with agreed data residency
- role-based access, single sign-on, least privilege and MFA for privileged accounts
- breach notice within 24 hours of detection
- audit logs kept for at least 12 months
- set fix times for vulnerabilities, such as 30 days for critical issues
- SAST and DAST tools and a yearly penetration test
- a full list of subprocessors and a documented security program with staff training
Testing
Build against the jane_partner_sandbox realm and the partner playground clinic before production. Test token refresh, the 429 path and webhook signature checks.
Questions to ask Jane before you sign
- How long does partner review take, and what does it cost?
- Which scopes will you grant us, including medications:create?
- Which source value do DoseSpot prescriptions carry when read through the API?
- When will the conversations, messages and chart entry endpoints be published?
- Are more webhook events planned, for example for patients or clinical records?
- Will you add calendar writes, and under what conditions?
- How are extensions listed and sold on the marketplace?
What is the next step for a Jane integration?
If your product fits Jane's rules, the first job is a partner application that shows your security posture and a clear multi-use product. Our Jane App integration services page covers how we help, and our EHR and EMR integration services cover the wider work.
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does Jane App have an API?
Can my clinic build its own Jane integration?
How does a software vendor apply to Jane?
Does the Jane API have a prescription endpoint?
Can I book appointments in Jane through the API?
Does Jane support FHIR or HL7?
What is the Jane API rate limit?
Is there a Jane sandbox?
Which webhooks does Jane send?
Does Jane work with AI scribe or AI scheduling tools?


