Jane App
Practice management software for health and wellness clinics
What Jane App does
Jane App is practice management software for clinics and wellness practitioners. It combines scheduling, online booking, charting, billing, reminders, and practice operations so healthcare-adjacent clinics can run bookings and administrative workflows from one system.
Where Jane App falls short
Jane gives clinics a strong online booking page and practice workflow stack, but it is not a full marketing website system or a broad self-serve API platform for arbitrary custom builds. Teams that want deep custom website behavior, public SEO content, or unsupported back-office syncs still need an external website layer and must stay inside Jane's documented partner-oriented API surface.
How we set Jane App up
On the native website path, a patient clicks a Jane Book Online button from the clinic website and lands on the clinic's Jane online booking site. From there the patient chooses a practitioner, treatment, and time slot, and Jane creates the Appointment inside the clinic's schedule. On the partner path, a documented Jane Extension can authenticate a practitioner through Jane's OAuth2 flow and make versioned API calls on that clinic's behalf, but most public website projects still stop at the hosted Jane booking handoff rather than building a fully custom scheduling layer.
Integration method: rest-api
What Jane App already owns
Jane App is practice management software for clinics and wellness practitioners. It combines scheduling, online booking, charting, billing, reminders, and practice operations so healthcare-adjacent clinics can run bookings and administrative workflows from one system.
Primary users: Clinic owners, front desk teams, physiotherapists, chiropractors, massage therapists, and allied-health practitioners
Typical fit: Independent practitioners through multi-practitioner clinics
Core functions
- Manage practitioner schedules
- Run online booking
- Store patient records and charting
- Handle billing and payment workflows
- Send reminders and confirmations
- Manage locations and treatment offerings
- Support clinic operations and reporting
What still has to happen around Jane App
Jane gives clinics a strong online booking page and practice workflow stack, but it is not a full marketing website system or a broad self-serve API platform for arbitrary custom builds. Teams that want deep custom website behavior, public SEO content, or unsupported back-office syncs still need an external website layer and must stay inside Jane's documented partner-oriented API surface.
Jane's documented developer platform is aimed at technology partners building practitioner-authorized extensions, not arbitrary public website developers looking for a broad self-serve API key flow.
Its public website tooling is centered on booking pages and booking buttons rather than a broader CMS or landing-page system.
It does not support Google Tag Manager or Meta Pixel because Jane avoids deep embedding within the booking site.
Advanced qualification logic and nonstandard intake usually need an external website flow before sending users into Jane booking.
Client-side login and multi-clinic account handling are recurring pain points in reviews.
Teams that want custom data syncs or server-side write automation still need to work inside Jane's approved partner model and exposed API objects rather than assume arbitrary write access.
Website and CRM integration surface
Native website path
Jane publicly documents HTML embed codes and direct URL buttons for clinic, practitioner, and location booking pages. Jane also surfaces Book now flows that can route people from Google Search or Maps directly into the Jane online booking site.
Developer surface
- Public API
- Yes
- API style
- rest-v1
- Auth
- oauth2-authorization-code
- Webhooks
- No
- Rate limits
- Not public
- Sandbox
- No
Integration patterns that make sense
Native First
FitUse Jane's online booking pages and booking buttons when the clinic mainly needs patients to book directly into Jane with minimal technical overhead.
The website places Jane-provided booking buttons or links that send the patient into the clinic's Jane online booking site, where availability, treatment rules, and booking controls are enforced by Jane.
Api First
LimitedOnly use the API-first path when the project fits Jane's documented Technology Partner model and the required data objects are exposed in the current public reference.
A technology partner authenticates a practitioner through Jane's documented OAuth2 authorization flow, then calls the versioned Jane Developer Platform APIs on that practitioner's behalf. Most public website projects still use Jane's booking buttons and hosted booking pages instead of a fully custom API-first handoff.
Hybrid
FitUse a hybrid setup when the clinic wants richer public-facing content and lead qualification but still wants actual scheduling to finish in Jane.
The website handles SEO content, conversion framing, and pre-booking education, then routes the patient into Jane's booking site through practitioner, location, or main booking buttons.
Data objects your stack has to preserve
Create
Appointment
Read
Practitioner, Location, Treatment, Appointment
Who usually fits a Jane App-centered website rebuild
Use this section to decide when Jane App's book online button flow is enough and when the website still needs a managed intake layer before the health wellness team takes over.
Best fit
- - Teams already running Jane App as the system of record
- - Operators who need stronger qualification before data reaches Jane App
- - Businesses that need a public site and intake flow shaped around health wellness demand
What operators complain about
- We are frustrated that there is no open API for teams that want deep custom integrations.
- We are frustrated that patient-side login and multi-clinic account handling can be confusing.
- We are frustrated that some users dislike having separate clinic-specific account patterns unless they use the newer Jane for Clients experience.
- We are frustrated that teams wanting advanced marketing instrumentation cannot use GTM or Meta Pixel inside Jane booking.
- We are frustrated that calendar syncing and external workflow flexibility are common requests from users.
- We are frustrated that the platform is strong operationally, but custom website behavior still needs to live outside Jane.
Technical trust before you connect the stack
Native path
book online button
The website should only promise the Jane App handoff paths that are publicly documented.
Auth model
OAuth2 for Technology Partners
If a custom handoff is needed, authorization into Jane App has to stay inside Jane's documented partner model.
API surface
Jane Developer Platform
Jane App still has to compete with Cliniko, SimplePractice, Practice Better while keeping the website handoff cleaner.
Auth: Jane's public developer docs describe an OAuth2 authorization flow for Technology Partners building Jane Extensions on behalf of practitioners. That is a documented partner-oriented auth model, not a generic public API key flow for arbitrary custom websites.
Data flow: The website usually sends patients into Jane's own online booking site through a button or direct booking link. Jane then handles availability, booking rules, and appointment creation inside the platform.
Security: For most website projects, the safer posture is still to keep custom website logic outside Jane and hand the patient into Jane's managed booking flow. If a partner integration is in scope, keep OAuth credentials server-side and stay inside Jane's documented extension model. Jane also limits deep embedding, which is why GTM and Meta Pixel are not supported inside the booking experience.
Also in the evaluation set
If Jane App is on the table, these adjacent systems usually come up too. Use the CRM Scorecard to decide whether you need a horizontal CRM, a vertical operating system, or a cleaner connection between both.
Jane App by industry
How Jane App gets configured for specific operating patterns.
beauty-studio
Jane App documents book online buttons and booking pages, not an open marketing API. We keep seeing vague contact forms force the desk to replay triage. This setup captures structured, marketing-safe
See the setupfunctional-medicine
We keep running into this problem: the website gets interested people, but the team still has to spend too much time figuring out who is actually ready for the kind of care we provide. Discovery calls
See the setupmartial-arts
Jane App documents book online buttons and booking pages, not an open marketing API. We keep seeing vague contact forms force the desk to replay triage. This setup captures structured, marketing-safe
See the setupmed-spa
Jane App documents book online buttons and booking pages, not an open marketing API. We keep seeing vague contact forms force the desk to replay triage. This setup captures structured, marketing-safe
See the setupphysiotherapy
People find us online, but the website is not helping them understand if we treat their problem or making it easy to start the evaluation process. Most clinic sites leak evaluation demand between spec
See the setupyoga-studio
Jane App documents book online buttons and booking pages, not an open marketing API. We keep seeing vague contact forms force the desk to replay triage. This setup captures structured, marketing-safe
See the setupNot sure if Jane App is the right fit?
The CRM Scorecard surfaces what your team actually needs from a CRM before you commit to one.
Take the CRM Scorecard