We build for a 100% native booking flow
We try to make the booking experience identical to Square's own. In practice, we run into a handful of real limitations in Square's public API — and here we've laid them out honestly.
Native push notification for merchants
The limitation
Square reserves this push notification for bookings made through its own first-party apps (Square Appointments, Square POS). No third-party integration — ours included — has API access to trigger it. This affects merchant notifications only; your customers still get their normal native Square confirmations and reminders exactly as usual.
Source: Square Developer docs — Bookings API webhooks ↗What we do
Every new booking sends you an instant email today. SMS notifications for merchants are in active development.
Manual “Pending” approval step
The limitation
Booking a service that carries a cancellation or no-show fee requires seller-level API access, and at that access level Square's API always creates the appointment as Accepted — there is no way to request a Pending state first, for us or for any other integration at that tier.
Source: Square Developer docs — Bookings API webhooks ↗What we do
Your cancellation policy and no-show fee still apply in full, so you're not losing protection against unwanted bookings — it's enforced right after the booking lands instead of before.
Prepayment visibility on the POS terminal
The limitation
Square's public API has no way to link a payment collected at booking to the specific appointment record — that's a gap in Square's own API surface, not a bug in our payment flow. So a prepaid amount won't automatically appear at checkout on the POS terminal.
Source: Square Developer Forums — linking a payment to an appointment ↗What we do
We write the amount paid and the remaining balance directly onto the booking's note inside Square, visible to your staff before they charge the rest.
Waitlist entries in the Square dashboard
The limitation
Square's own Appointments Waitlist — the one in your Square dashboard — has no public API. There is no way for any third-party integration, ours included, to write an entry into it directly.
Source: Square Developer Forums — waitlist API availability ↗What we do
When a customer joins the waitlist on your booking page, we record it as a note on their Square customer profile and send you an instant email right away, so it doesn't just sit unnoticed in a customer's profile.
Outside of these three points, the booking flow is functionally identical to Square's own — email us if you run into anything else.