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.

Example:

"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: Standard or Recurring Booking, or Seated Booking. If you're rescheduling a seated booking as org admin of booking host, pass booking input for Standard or Recurring Booking 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"

rescheduleWithSameHost
boolean

Only for round robin event types that let the person rescheduling choose the host. True keeps the original host, false lets round robin pick from the whole team. Ignored for every other event type.

Example:

true

allowConflicts
boolean

When true, availability conflict checks are bypassed for an authenticated user who has access through the existing event owner, host, assigned user, team admin or organization admin checks. Team- and organization-scoped keys are restricted to events in their stored team or organization. Otherwise this parameter is silently ignored. Only supported on the 2026-02-25 and 2026-05-01 API versions.

Example:

true

allowBookingOutOfBounds
boolean

When true, booking time out-of-bounds checks are bypassed, allowing bookings outside the normally permitted scheduling window, for an authenticated user who has access through the existing event owner, host, assigned user, team admin or organization admin checks. Team- and organization-scoped keys are restricted to events in their stored team or organization. Otherwise this parameter is silently ignored. Only supported on the 2026-02-25 and 2026-05-01 API versions.

Example:

true

skipBookingLimits
boolean

When true, booking limit checks (event type, team, and per-host count and duration limits) are bypassed for an authenticated user who has access through the existing event owner, host, assigned user, team admin or organization admin checks. Team- and organization-scoped keys are restricted to events in their stored team or organization. Otherwise this parameter is silently ignored. Only supported on the 2026-02-25 and 2026-05-01 API versions.

Example:

true

Response

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

"success"

data
Booking · object
required

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