Skip to main content
POST
Reschedule a booking

Headers

cal-api-version
string
default:2026-02-25
required

Must be set to 2026-02-25.

Authorization
string

value must be Bearer <token> where <token> is api key prefixed with cal_, managed user access token, or OAuth access token

x-cal-secret-key
string

For platform customers - OAuth client secret key

x-cal-client-id
string

For platform customers - OAuth client ID

Path Parameters

bookingUid
string
required

Body

application/json

Accepts different types of reschedule booking input: Reschedule Booking (Option 1) or Reschedule Seated Booking (Option 2). If you're rescheduling a seated booking as org admin of booking host, pass booking input for Reschedule Booking (Option 1) along with your access token in the request header.

start
string<date-time>
required

Start time in ISO 8601 format for the new booking

Example:

"2024-08-13T10:00:00Z"

rescheduledBy
string

Email of the person who is rescheduling the booking - only needed when rescheduling a booking that requires a confirmation. If event type owner email is provided then rescheduled booking will be automatically confirmed. If attendee email or no email is passed then the event type owner will have to confirm the rescheduled booking.

reschedulingReason
string

Reason for rescheduling the booking

Example:

"User requested reschedule"

emailVerificationCode
string

Email verification code required when event type has email verification enabled.

Example:

"123456"

allowConflicts
boolean

When true and the authenticated user is a host of the event type, availability conflict checks are bypassed. If the user is not a host or is unauthenticated, this parameter is silently ignored.

Example:

true

allowBookingOutOfBounds
boolean

When true and the authenticated user is a host of the event type, booking time out-of-bounds checks are bypassed allowing bookings outside the normally permitted scheduling window. If the user is not a host or is unauthenticated, this parameter is silently ignored. Only supported on the 2026-02-25 API version.

Example:

true

Response

201 - application/json
status
enum<string>
required
Available options:
success,
error
Example:

"success"

data
object
required

Booking data, which can be either a BookingOutput object or a RecurringBookingOutput object