Create a calendar integration
Create a calendar integration. The connection is verified before saving (Cal.com: API key + event type; Calendly: OAuth connection_id + public event_type_id; Acuity: OAuth connection_id + numeric appointment_type_id and optional calendar_id; google/outlook: the calendar connection must exist; native: the booking event type must exist) — invalid credentials are rejected with 400 and never stored. Calendly resource URIs, Acuity account identifiers, and all OAuth tokens stay internal. Requires an admin-level credential; plan gate: calendar_integrations.
Required scope: integrations:write (keys without scope restrictions have full access).
Authorizations
API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access.
Body
64calcom, calendly, acuity, google_calendar, outlook_calendar, native, etermin Provider-specific configuration (see the Integration schema). For Acuity send an OAuth connection_id, numeric appointment_type_id, optional calendar_id, and optional allowed_ops; appointment metadata and timezone are loaded canonically from Acuity.
Response
The created integration (secrets masked).
A calendar integration. config is provider-specific; secret values are always masked as •••.