Time zones
How company, location, and request timezones affect availability and daily caps.
Purpose
OnSched stores appointment times in UTC and interprets calendar days in an IANA timezone. Pick the timezone that matches the location your customer visits.
Which timezone is used
| Context | Timezone |
|---|---|
New location, timezone omitted | America/New_York |
Location daily cap (customerDailyBookingLimit) | Location timezone; UTC only if the stored value is blank |
| Service-wide daily quotas | Company timezone for company-scoped services; location timezone for location-scoped services |
GET /v3/availability timezone query | Response clock only. Date-only startDate/endDate are read in that zone (UTC if omitted) |
| Weekly hours | Location wall-clock (then company), even when a stored row has a frozen iana |
11pm example
A location in America/New_York with customerDailyBookingLimit: 1. A customer who already has a 10:00 AM booking cannot hold another start at 11:00 PM the same Eastern calendar day. That 11:00 PM start is still “today” in New York, even though the UTC date has rolled.
Request parameter
Pass timezone=America/New_York (or another IANA name) on availability when you want availableTimes in local clock. Omitting it returns UTC.
List valid identifiers with GET /v3/timezone — Platform API utilities.
See also
Updated 1 day ago
Did this page help you?