# Routing Groups and Calendars (/docs/api-reference/product-resources)



Canonical resources [#canonical-resources]

| Resource       | API path             |
| -------------- | -------------------- |
| Routing groups | `/v2/routing-groups` |
| Calendars      | `/v2/calendars`      |

Use these paths for all integrations, including child operations such as `/:id`.
The older `/v2/campaigns/transfer-configs` and
`/v2/campaigns/appointment-configs` paths have been retired.

Payload compatibility [#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`.
