Skip to main content
PATCH
Update 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_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, billing:write, 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 within the workspace's available capabilities.

Path Parameters

id
string<uuid>
required

Event type ID

Body

application/json
name
any
slug
any
duration_min
any
timezone
any
availability
any
public_holidays
any
description
any
buffer_before_min
any
buffer_after_min
any
min_notice_min
any
max_days_ahead
any
slot_increment_min
any
reminder_hours
any
is_active
any
booking_fields
any
phone_required
any
email_required
any
sender_email_address_id
any
confirmation_email_subject
any
confirmation_email_body
any
email_templates
any
email_locale
any
guest_emails_enabled
any
hour_cycle
any

Response

The updated 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}.