Skip to content
APIANT
GuideAPI Appsv1

Availability Freshness and Reliability

When availability is recomputed, and how double-booking is prevented.

CalendarConnect is built so a booking page never offers a time that is not genuinely open in Mindbody. This page explains when availability is refreshed and how the two systems are kept in agreement.

Availability is computed at view time

Each time a visitor opens a booking page, the staff member's open times are read from Mindbody and written to Calendly before the page is shown. There is no background sync and no refresh interval to wait for. The practical effect: whatever is true in Mindbody at the second the page opens is what the visitor sees. A slot booked or blocked in Mindbody a minute ago is already gone from the next page view.

The 30-day window

Availability is published 30 days ahead. Visitors can book within that window, and the window rolls forward on each page open, so the coverage is always the next 30 days from now.

How double-booking is prevented

Three things keep Mindbody and Calendly in agreement:

  • Read at view time. Because open times are read from Mindbody every time the page opens, a slot Mindbody no longer offers cannot appear.
  • Write back on booking. When a visitor books, the appointment is written into Mindbody right away, so it leaves Mindbody's open times and will not appear on the next page open for anyone else.
  • Duplicate protection. If the same booking notification arrives more than once, CalendarConnect recognizes it and writes the appointment only once, so a single booking never becomes two Mindbody appointments.

If a page is left open

If a visitor keeps a booking page open for a long time and then books a slot that was taken in the meantime, Mindbody declines the appointment and your team is alerted to follow up, rather than a double-booking being created. Refreshing the page always loads a current read.

If something is briefly unavailable

If Mindbody or Calendly is momentarily unreachable, the affected step is retried automatically. A completed booking that cannot be written to Mindbody on the first attempt is retried and, if it still cannot be placed, is logged and your team is alerted, so no booking is ever lost silently.

Last updated July 16, 2026