Skip to main content
POST
Reschedule a booking

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

Booking ID

Body

application/json
start
string<date-time>
required

New start time in ISO 8601 UTC. The duration stays the one of the event type.

allow_outside_availability
boolean
default:false

Allow a staff booking within the next two years outside the event type's usual availability. Observed public holiday closures and confirmed bookings of the same event type still block the requested time.

Response

The rescheduled booking.

data
object
required