Google Calendar FREE events block GoDaddy bookings despite correct Free/Busy API response

Hello Google Workspace Developers,

I’m investigating a Google Calendar synchronization issue affecting my automotive repair business.

Our Google Calendar is connected to GoDaddy Online Appointments through Cronofy. Events explicitly marked FREE in Google Calendar are incorrectly blocking customer booking availability in GoDaddy.

GoDaddy support has repeatedly directed us to Google, but we conducted a controlled test that raises questions about where the integration is failing.

Controlled test — October 19, 2026

  • Calendar: Primary Google Calendar

  • Test event: Wednesday, October 21, 2026, 1:00–2:00 PM (America/Toronto)

  • Event transparency: transparent (FREE)

  • Other conflicting events: None during the test hour

We confirmed through Google’s Events API that the test event had transparency: "transparent".

While the event was present, we queried Google’s Free/Busy API for the primary calendar from 12:00–3:00 PM.

The response reported only this separate busy interval:

{
  "busy": [
    {
      "start": "2026-10-21T14:30:00-04:00",
      "end": "2026-10-21T15:00:00-04:00"
    }
  ]
}

Google’s API therefore reported no busy interval between 1:00 and 2:00 PM.

However, after synchronization, GoDaddy Online Appointments removed both the 1:00 PM and 1:30 PM booking slots.

When the test event was deleted and synchronization completed, those booking slots returned.

We reproduced this behavior with two separate FREE test events.

Questions for Google

  1. Is it correct that events with transparency: "transparent" should not appear as busy intervals in the Google Calendar Free/Busy API?

  2. Does the API response above indicate that Google’s Free/Busy service is behaving as expected?

  3. Are there any Google Calendar API behaviors, event metadata, or synchronization considerations that could cause a third-party integration such as Cronofy to interpret transparent events as blocking availability?

  4. Is there any additional Google-side diagnostic information we should collect before escalating this to GoDaddy/Cronofy?

We’re seeking technical clarification so we can identify the responsible integration layer and provide accurate evidence to GoDaddy.

Thank you for your assistance.

Hi, Your test is solid and it points away from Google. In the Calendar API, transparency “transparent” means the event doesn’t block time, and the Free/Busy API leaves those events out, which is exactly what your response shows (only the 2:30-3:00 busy block). So Google is giving the right answer.

That means the slots are being removed further down the chain, by Cronofy or GoDaddy. A common cause is the integration reading the events themselves instead of the free/busy result, and treating any event as busy. Send your test (event JSON showing “transparent” plus the Free/Busy response) to GoDaddy and ask them to escalate it to Cronofy. Cronofy will know which data they read.

Two ways around it in the meantime:

  1. Make a second calendar (e.g. “Not busy”) in Google Calendar and put the FREE events on that one. Then in GoDaddy’s calendar settings, make sure only your main calendar is ticked for checking conflicts. If it checks every calendar on your account, the second one will still block slots.

  2. Or skip the middlemen: Google Calendar has its own booking page built in (Appointment schedules). It checks your calendar directly, so there’s no Cronofy sync in between. Worth a look if GoDaddy can’t sort it out.

If you need to stay on GoDaddy and don’t want to move events around by hand, a small Apps Script could copy only your busy events onto a separate calendar for GoDaddy to read. Happy to share one if that would help.