Skip to content
Go to app
Signpost for Astro Get the theme →

Time zones and availability

How the API represents time, and how to show slots in your user's time zone without off-by-one-hour bugs.

Intermediate · 6 min read · Updated Aug 28, 2026

Scheduling bugs are almost always time zone bugs. The API follows one simple rule to avoid them.

Every timestamp the API accepts or returns is an ISO 8601 string in UTC, for example 2026-11-02T09:00:00Z. Convert to local time only when you display it.

const start = new Date(slot.start)
start.toLocaleString("en-GB", {
timeZone: "Europe/Rome",
dateStyle: "medium",
timeStyle: "short",
}) // "2 Nov 2026, 10:00"

The GET /v1/availability/slots endpoint combines:

  • the host’s schedule, in the schedule’s own time zone
  • busy times from every connected calendar
  • the event type’s buffers, minimum notice and daily limits

The response is already filtered, so every slot you receive can be booked.

Because schedules are stored in a named time zone such as America/New_York, a host who works 9:00 to 17:00 keeps those local hours when the clocks change. The UTC times of the slots shift by an hour, and that’s expected.

Use the invitee’s browser time zone by default, and let them change it:

const zone = Intl.DateTimeFormat().resolvedOptions().timeZone // "Europe/Rome"