Why Jane.app has no public booking API — and the workaround.

The short answer: as of this writing, Jane.app offers no public booking API — there is no supported way for an external app, chatbot, or marketing tool to create appointments in a clinic's Jane calendar directly. That's why almost every "Jane chatbot" on the market only collects a name and phone number for the front desk to call back. A working alternative exists: a bridge built through GHL that reads live availability and creates real Jane appointments from inside a chat conversation.

Does Jane.app have an API at all?

Jane provides limited integration points (and an active feature-request community asking for more), but nothing that lets third parties book appointments programmatically. For a platform that dominates allied-health booking in Canada, that's a striking gap — and it shapes what every marketing tool in the clinic space can and can't do.

Why doesn't Jane offer a public booking API?

Jane hasn't published a definitive reason, but the practical explanations are consistent with how the platform behaves:

• Patient data sensitivity. Jane calendars contain health information governed by Canadian privacy law (PIPEDA, and provincial rules like BC's PIPA). Every external write-path is compliance surface area.
• Booking integrity. Jane's scheduling logic — durations, buffers, practitioner rules, insurance types — is complex. Third-party writes that get it wrong would break the product's core promise.
• Product philosophy. Jane has historically built features in-house at its own pace rather than opening a developer platform.

Whatever the mix of reasons, the effect for clinic owners is the same: your booking system is an island, and most automation vendors simply route around it by not really integrating at all.

What do "Jane-integrated" chatbots actually do?

Almost always one of two things: they link the patient out to your Jane booking page (adding steps and drop-off, especially on mobile at night), or they capture contact details as a "lead" for your front desk to chase the next day. Both lose the patient at the exact moment they were ready to book. Neither is a booking.

So how can a chatbot book real Jane appointments?

The workaround we engineered at Clinic Pilot runs through GHL as a bridge layer:

1. The bridge reads live availability from the clinic's Jane schedule — practitioners, services, durations, real open slots.
2. The assistant offers real options in-chat. "Kayla has 5:40 or 7:00 Thursday" — actual openings, not a form.
3. The booking is created in Jane the moment the patient picks, exactly as if the front desk had entered it.
4. Two-way SMS takes over: confirmation, reminder, reschedule handling, and later, rebooking and win-back nudges — replacing Jane's one-way notifications that patients can't reply to.

The result is the thing everyone assumed Jane's missing API made impossible: a website conversation at 11 pm that ends with a confirmed appointment in the clinic's real calendar. In our deployments, a meaningful share of these bookings happen outside front-desk hours — demand that previously went to whichever competitor answered first the next morning.

What should clinic owners take from this?

Three things. First, be skeptical of any tool claiming "Jane integration" — ask whether it creates the appointment or just collects a lead. Second, the no-API gap is an opportunity: because real booking automation is rare, the clinics that have it convert after-hours demand their competitors physically cannot. Third, if Jane ships a public API someday, great — the conversation layer, SMS follow-up, and attribution built on top remain the durable value.

If you want to see a real Jane booking happen inside a chat, the booking assistant page shows the flow — or get in touch and we'll show it live against a real calendar.