Routing Groups and Calendars
Canonical resource names and backwards-compatible API paths.
Canonical resources
| Resource | Canonical API path | Supported legacy alias |
|---|---|---|
| Routing groups | /v2/routing-groups | /v2/campaigns/transfer-configs |
| Calendars | /v2/calendars | /v2/campaigns/appointment-configs |
Legacy paths execute the same operations with the same permissions, validation,
status codes, and request and response shapes. Child paths such as /:id also
remain supported. Use the canonical paths for new integrations.
Payload compatibility
The naming change does not rename payload fields. A routing group is represented
by transferConfig and referenced through transferConfigId. A booking calendar
is represented by appointmentConfig and referenced through
appointmentConfigId. Existing integrations can continue sending and reading
these fields.
A calendar controls booking availability, assignment, and appointment workflows. An external calendar is a Google Calendar or Outlook calendar connected for availability checks and synchronization. An appointment is an individual booking.
Scripts and external-calendar connections have canonical application API paths
at /v2/scripts and /v2/external-calendar-connections. These retain their
existing application-only API visibility and legacy aliases at /v2/call-forms
and /v2/calendar-connections.