Fresha publishes no public API reference, so we will not tell you what its API does.
Every other page in this section quotes the vendor's own endpoint index. This one cannot, because Fresha does not publish one: integration runs through a partner programme rather than public documentation. That does not stop a phone agent working for a Fresha salon, and it does change what any vendor is in a position to promise you, including us.
What is Fresha, and who runs on it?
Fresha is booking and business management software for salons, barbershops and spas, with a large consumer-facing marketplace attached. It is one of the most widely adopted systems in the independent beauty sector, particularly outside North America, and it has grown fast among smaller and newer businesses.
Fresha salons tend to be busy, appointment-dense and lightly staffed at the front. A large share of bookings arrive through Fresha's own marketplace and through the salon's booking link, which means the phone carries the calls that self-service could not absorb.
Those are, as ever, the awkward and valuable ones: a client who needs to move an appointment, someone asking whether a treatment suits them, a first-timer who does not know which service to choose. They arrive at the times a salon is least able to pick up.
What gap does Fresha leave?
The same one every booking platform leaves, plus one of its own. It books efficiently and it does not answer calls, and because Fresha's documentation is not public, salon owners evaluating phone vendors have no way to check the integration claims they are being told.
That second gap is the one this page is actually about. When a vendor's capability is checkable, you can verify it in a minute. When it is not, you are relying entirely on the vendor's own account of what they have built, which is the worst position to be in when you are signing a contract.
It is also the situation in which vague language flourishes. 'Works with Fresha' can mean a live two-way booking integration or it can mean somebody once connected a Zap, and with no public reference to check against, both claims read identically on a website.
None of this is a criticism of Fresha. Plenty of good platforms gate their APIs behind a partner programme, and it is a reasonable way to control quality. It just moves the burden of proof onto whoever is selling you the integration.
What does Fresha's API actually allow?
We do not know, and we are not going to guess. Fresha has no publicly readable API reference: its developer portal does not resolve publicly and integration is handled through a partner programme. That is a genuine unknown rather than a capability we are being coy about.
Not publicly documented; we are not claiming a depth here
Every other page in this section transcribes the vendor's own endpoint index: Open Dental's specification, Square's Bookings API reference, Mindbody's OpenAPI document, Clio's downloadable spec. For Fresha there is nothing equivalent to read. developers.fresha.com does not resolve publicly, and Fresha operates a partner account programme instead, which means the API surface is disclosed to approved partners rather than published. We could tell you what we suspect it supports (most booking platforms of this size expose availability and appointment creation) but a suspicion is exactly the kind of thing that becomes a sentence on a sales call and then a problem, and it is how this site got Vagaro wrong once already.
We would rather publish nothing here than publish a guess. Prospects read these pages aloud on sales calls, and a capability we cannot evidence is the one mistake on this site that costs more than the page earns. Ask us on the first call and you will get a straight answer about Fresha.
What that means for your build
What we can say precisely is how the build works without a confirmed write. The agent handles the call, answers what it should, quotes your hours and services from your own configuration, and sends the caller your Fresha booking link by text while they are still on the phone. The client books themselves through your booking page, into your calendar. That route requires no API at all, which is why it can be promised honestly. If your salon has partner-level Fresha access, tell us during setup and the ceiling conversation becomes a real one rather than a theoretical one.
What it will not do
- Be described honestly by any vendor as a confirmed two-way Fresha integration on public evidence. If you are told otherwise, ask which endpoint; the question is fair and the answer is informative.
- Advise on treatment suitability. That routes to a person in every salon and every clinic, on every page of this site.
- Quote a price for a service where the price depends on hair length, density or condition.
- Waive your cancellation policy. It states the policy you have.
What does a call to a busy Fresha salon sound like?
A rebooking, usually, and a question nobody has time to answer at the desk. The agent's job here is to be genuinely useful without pretending to a calendar write it cannot evidence.
An example call: composite, not a recording
An existing client calls on a Thursday to move an appointment, at the hour the salon is fullest.
- Caller
Hi, I've got a balayage booked for Saturday but something's come up - can I move it?
- Agent
Of course. Balayage is a long appointment so it's worth getting the right slot rather than the soonest - are you flexible on the weekday, or does it need to be a weekend?
Working from the salon's own service configuration for duration. Getting this wrong is what produces a rushed colour and an unhappy client. - Caller
A weekday's fine if it's after 4.
- Agent
That helps. I'm sending you the booking link now - it'll show you every late-afternoon slot with enough time for a full balayage, so you can pick the one that works. Shall I stay on while it comes through?
The link route, stated plainly. The caller sees genuine availability through the salon's own booking page. - Caller
Got it - Wednesday at 4:30 works.
- Agent
Lovely. One thing worth flagging - if you've used a box colour since your last visit, let them know in the notes, because it changes how the lightener behaves.
The kind of question a good front desk asks and a message-taking service never does. It is what stops a colour going wrong on the day.
An appointment moved without the front desk stopping, and a colour history flag captured that would otherwise have surfaced when the client was already in the chair.
Fresha does not publish an API reference, so no vendor can prove a Fresha booking integration from public evidence - which makes the right question for any of them not whether they integrate, but which endpoint they write to.
If you are comparing phone vendors on Fresha, ask each one what they read and what they write. The ones who answer in specifics are the ones who have actually built something.
Start free pilotQuestions Fresha salons ask
No public evidence supports it, so treat any vendor claiming one with care. Fresha has no publicly readable API reference: developers.fresha.com does not resolve publicly and integration runs through a partner programme, checked August 12, 2026. Any vendor telling you they have a confirmed two-way Fresha integration is asking you to take their word for it, which may be perfectly true and is not something you can check. Ask which endpoint. It is a fair question and the answer tells you a lot.
Through the booking link, which needs no API and works today. The agent answers the call, handles the question, quotes your services and hours from your own configuration, and texts the caller your Fresha booking page while they are still on the phone, then stays on the line while they open it. The client books themselves, into your calendar, through your own page. It adds about thirty seconds to a call and it is the same route we use for Vagaro, where the write endpoint is confirmed not to exist.
Because the alternative is the thing that makes this whole category hard to buy from. We recorded Vagaro as booking appointments once, from a search summary whose most confident source turned out to be a competing vendor's marketing blog, and Vagaro's endpoint index has no create endpoint at all. That correction is why every capability on this site now carries a source and a date, and why a page with nothing to cite says so rather than filling the space.
Potentially quite a lot, and it makes the conversation a concrete one. If your salon has partner-level access we can look at what your account actually exposes rather than reasoning from the outside, and the ceiling discussion stops being theoretical. Bring it up during setup rather than after; it is the single fact that would move this page from unverified to specific for your build.
Hear it move a balayage without touching the desk
The free pilot is about fourteen days to a working line with no call limit. Call it as a client trying to rebook, and see how much it gets right without an API to lean on.
Start free pilotLast updated .