Extend Barberly with your own booking integrations

Any shop running on Barberly. Your locations, team, services, working hours and booking rules have to be set up in Barberly first - the API reads that configuration, it does not create any of it. Then issue a key under Apps, Booking API, Create key.

No. Every request goes through the same availability engine as your own app and website, and it sees the client view of the calendar, never the staff one. Working hours, lead times, service durations, which barber does what, manual approval and the requirement for a registered customer all apply unchanged. The API invents no rules of its own and can bypass none.

No. It is a client-facing booking tool, the same as your mobile app or your booking website. It does not open up the business side of your account - no reports, no team management, no settings.

No. The Booking API is for bookings only: creating, rescheduling, reading and cancelling appointments. The walk-in queue and the appointment waitlist are handled by the kiosk and the Barberly business app.

No. Anything in a browser bundle can be read by anyone who loads the page, so a key with real scopes belongs on a server. Keep it in your own backend and proxy the requests, attaching the X-Api-Key header there. The demo repository shows the setup.

Yes. The API exposes locations, team members, services with add-ons and real availability, so you can design your own booking flow in your own brand and keep Barberly as the engine behind it. If you only need booking on an existing site, the ready-made booking widgets are usually faster to set up.