Every system on this list connects. We publish how.
Nineteen booking and practice-management systems, each one read against the vendor's own API reference rather than its marketing page. Eleven take a booking straight from the call. The rest connect a different way, and every one of those ways still ends with an appointment on your calendar.
Can you integrate with my software?
Yes, for every system on this page. What differs between them is the route the booking takes, not whether the connection happens. Eleven of the nineteen publish a create-appointment endpoint, so the appointment lands in your system while the caller is still on the line. The other eight connect a different way and still end up with a booked appointment.
That is a more useful answer than the one this category usually gives, because “integrates with Vagaro” can mean it writes your booking into Vagaro, or it reads your calendar and texts the caller a link, or somebody built a Zap once. Those are three different products and the word covers all of them. So we publish which one you are getting.
The four routes
- The vendor’s API. Where a create endpoint exists, we use it. The booking is in your system before the call ends and your front desk sees it appear.
- Webhooks, both directions. For systems that would rather push events than accept writes, and for keeping two calendars honest with each other in real time.
- A booking link, sent mid-call. Where the API reads availability but will not write to it, the agent quotes real open times and sends the link while the caller is still on the phone. They book before they hang up.
- A browser session, under your own credentials. Where there is no usable API at all, a headless browser drives the same screens your front desk uses. It is the route we reach for last, and it is why the answer to this question is never no.
What each vendor’s API actually allows
All nineteen read against the vendor’s own endpoint index (the OpenAPI spec, the Swagger document, or the published method list) rather than the capability page. A capability page is marketing. An endpoint index is a contract.
Read 2026-08-10 and 2026-08-12. Sources and dates per row are held in the research record behind these pages, and repeated on each vendor’s own page as it goes up. APIs change; this is what the index listed when we read it.
| System | How it connects | What the endpoint index shows |
|---|---|---|
| Open Dental | Books directly | POST /appointments creates; GET /appointments/Slots reads open time. The ASAP short-call list is published too. |
| Square Appointments | Books directly | POST /v2/bookings creates; POST /v2/bookings/availability/search reads. |
| ServiceTitan | Books directly | CRM Bookings, JPM Appointments and Jobs, Dispatch capacity and arrival windows. |
| Mindbody | Books directly | POST appointment/addappointment creates; bookableitems, availabledates and activesessiontimes read. |
| Clio | Books directly | POST /calendar_entries.json creates. Contacts, matters and communications also accept writes. Runs a Canadian data region. |
| GoHighLevel | Books directly | POST /calendars/events/appointments creates; Get Free Slots reads. |
| Google Calendar | Books directly | Events: insert creates; Freebusy: query reads across several calendars at once. |
| Microsoft Outlook | Books directly | Graph Create Event creates; Get free/busy schedule and Find meeting times read. |
| Calendly | Books directly | The Scheduling API books end to end: POST /invitees, with GET /event_type_available_times for open slots. Paid plans. |
| Housecall Pro | Books directly | Create a Job is a published operation, alongside customers, estimates, invoices, schedule and webhooks. |
| Acuity Scheduling | Books directly | POST /appointments creates. No availability endpoint appears in the public index, so open time comes from the calendar side. |
| Vagaro | Reads, then links | Search Appointment Availability and Retrieve Appointments read. There is no create endpoint, so the caller gets a live booking link on the call. |
| Boulevard | Books via partner access | The Client API books through a cart flow: create, add item, read bookable times, reserve, check out. Enterprise tier only. |
| Jane | Books via partner access | Appointments, patients, staff and treatments are published endpoints. Access is by approved partner with practitioner consent. |
| Fresha | Books via partner access | No public API reference. Integration runs through Fresha's partner programme, so this one starts with a conversation. |
| Jobber | GraphQL, schema behind login | One GraphQL endpoint covering Client, Job, Request, Visit, Quote and Property, plus webhooks. Private integrations need no app review under five accounts. |
| Stripe | Supporting rail | POST /v1/payment_links takes a deposit on the call; payment_link events report back. |
| Slack | Supporting rail | chat.postMessage puts the call summary in the channel your team already watches. |
| Zapier | Supporting rail | Catch Hook triggers on the REST hook protocol, into a directory of more than 9,000 apps. |
Two rows moved on 2026-08-12. Clio was previously unverified because its reference would not render; its downloadable OpenAPI spec settles it, and the same file sources the Canadian data region a law firm actually cares about. Calendly used to be a redirect to a hosted page, and now books end to end through its Scheduling API.
The hardest one on the list, and what we do about it
Vagaro is the one system here with no create-appointment endpoint. Its API searches appointment availability and retrieves existing appointments, and that is the ceiling. So a Vagaro salon gets route three: the agent reads genuinely open times, says them out loud, and sends the caller a booking link before the call ends. The appointment still gets made. It gets made by the caller, on their phone, thirty seconds later.
This matters because you will find pages claiming direct Vagaro write-back. They are describing something the API does not expose. We know because we published that error ourselves first: an early research pass recorded Vagaro as “books appointments” on the strength of a search summary, and the most confident source in it turned out to be a marketing blog run by a competing AI receptionist vendor, a party with an interest in the answer being yes.
The correction cost us nothing and it is the reason every row above carries a source and a date. If an integration on this page is ever wrong, it will be wrong in a way you can check in about a minute.
The software we get asked about
Nineteen systems across eight categories, with the route each one takes. Every one has its own page setting out what its API permits, what we would build against it, and what we would refuse to build.
Calendars
- Google CalendarBooks directly
- Microsoft OutlookBooks directly
- CalendlyBooks directly
Health & clinics
- JaneBooks via partner access
Dental
- Open DentalBooks directly
Salon, spa & retail
- Square AppointmentsBooks directly
- MindbodyBooks directly
- VagaroReads, then links
- BoulevardBooks via partner access
- FreshaBooks via partner access
Field service
- ServiceTitanBooks directly
- GoHighLevelBooks directly
- Housecall ProBooks directly
- JobberGraphQL, schema behind login
Legal
- ClioBooks directly
Horizontal booking
- Acuity SchedulingBooks directly
Not listed? That is normal, and it is not a problem. Anything with an API connects the same way the eleven above do, and anything without one connects through route four. Bring it up on the first call and you will get a straight answer about which.
Questions we get about integrations
Almost certainly. Of the nineteen systems we are asked about most, eleven publish a create-appointment endpoint we write straight into, three book through the vendor's partner programme, one reads availability and takes a booking link instead, and the rest connect through webhooks or Zapier. Where none of that exists, we bridge it with a browser session signed in under your own credentials.
Not by writing to Vagaro's API, because Vagaro's endpoint index has no create-appointment endpoint, only availability search and appointment retrieval. Any vendor claiming a direct Vagaro write-back is describing something their API does not expose. What works instead: the agent reads live availability, tells the caller what is genuinely open, and sends the booking link while they are still on the phone.
It still connects. A headless browser session signs in with your own credentials and drives the same screens your front desk uses, so the booking lands in the same place it always has. It is the slowest of the four routes and the one we reach for last, but it is why the answer to this question is never no.
We read the vendor's own endpoint index (the OpenAPI spec, the Swagger document, or the published method list) rather than the capability page. Every row on this page carries the source and the date it was read. APIs change, and a claim without a date is not checkable.
A vendor’s capability page is marketing and its endpoint index is a contract - and when the two disagree, the contract is the one your customer finds out about.
Ask us about the one you actually run
Bring your software to the first call and you will get the route it takes, the endpoint that backs it, and the date we read it. The free pilot is about fourteen days to a working line, no call limit.
Start free pilotLast updated .