Skip to main content
POST
Create a booking event type

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: 128
slug
string
required
Pattern: ^[a-z0-9-]{3,64}$
duration_min
integer
required
Required range: 5 <= x <= 480
timezone
string
required
Example:

"Europe/Berlin"

availability
object
required
Example:
description
string
Maximum string length: 2000
buffer_before_min
integer
default:0
buffer_after_min
integer
default:0
min_notice_min
integer
default:60
max_days_ahead
integer
default:30
slot_increment_min
integer | null
reminder_hours
integer | null
is_active
boolean
default:true

Response

The created event type.

data
object
required

An event type of the native booking engine. Each active event type has a public, embeddable booking page at /book/{workspace}/{slug}.