Skip to main content
POST
Create a calendar integration

Authorizations

Authorization
string
header
required

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

application/json
name
string
required
Maximum string length: 64
provider
enum<string>
required
Available options:
calcom,
calendly,
acuity,
google_calendar,
outlook_calendar,
native,
etermin
config
object
required

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.

is_active
boolean
default:true

Response

The created integration (secrets masked).

data
object
required

A calendar integration. config is provider-specific; secret values are always masked as •••.