Platform API utilities
Short guide to supporting endpoints: timezones, geography, holidays, email templates, support tickets, and health checks.
These routes sit alongside the main booking CRUD surface. Use the API reference for full request and response schemas.
Timezones (GET /v3/timezone)
GET /v3/timezone)Returns valid IANA timezone identifiers for dropdowns and validation when you cannot rely on a hardcoded list.
Geography (GET /v3/geography)
GET /v3/geography)Optional query parameters country and state return nested geography data for address UIs. Requires a valid Bearer token (same as other authenticated routes).
Holidays (GET / POST /v3/holidays)
GET / POST /v3/holidays)Manage company-level holiday definitions that availability and scheduling can respect. Use the interactive reference for body fields and list filters.
Email templates (GET / POST /v3/emailTemplates)
GET / POST /v3/emailTemplates)Read and update email template content for notification flows configured in your account.
Domains and OAuth client IDs
/v3/domainsand/v3/domain— Manage custom domains for your company when your account supports them. See the API reference and Authentication for how domains relate to your integration./v3/clientId— Create and list OAuth2 client credentials (also summarized in the Companies overview).
Support tickets (/v3/tickets)
/v3/tickets)Create, list, update, and message support tickets via the API when your integration or operations workflow needs programmatic access. Endpoints include collection and per-ticket routes for messages and notes.
Health (GET /v3/health)
GET /v3/health)Liveness check for monitoring. No business data; suitable for load balancers and uptime probes.
Related documentation
- Authentication — How to obtain tokens for authenticated routes
- Notifications — How messaging fits the product
- Get started — Core booking flows
Updated 4 days ago
