> ## Documentation Index
> Fetch the complete documentation index at: https://cal.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Reassign a booking

> Reassigns the host of a round robin or managed event type booking. The provided authorization header refers to the owner of the booking.

      Without `userUuid` in the body, an available round robin host is picked automatically.

      With `userUuid`, the booking is reassigned to that user. For a **round robin** booking, the user must be one of the booking's hosts and the booking keeps its `uid`. For a **managed event** booking, the user must be one of the users the managed event is assigned to — list them, along with their availability for the booking's slot, with `GET /v2/bookings/{bookingUid}/reassignment-candidates`. Reassignment moves the booking onto the new host's own child event type, so the original booking is cancelled and **the returned booking has a new `uid`** which you must store in place of the old one. Recurring managed bookings cannot be reassigned yet.

       <Note>Please make sure to pass in the cal-api-version header value as mentioned in the Headers section. Not passing the correct value will default to an older version of this endpoint.</Note>

If accessed using an OAuth access token, the `BOOKING_WRITE` scope is required.
      



## OpenAPI

````yaml /api-reference/v2/openapi.json post /v2/bookings/{bookingUid}/reassign
openapi: 3.0.0
info:
  title: Cal.com API v2
  description: ''
  version: 1.0.0
  contact: {}
servers: []
security: []
tags: []
paths:
  /v2/bookings/{bookingUid}/reassign:
    post:
      tags:
        - Bookings
      summary: Reassign a booking
      description: >-
        Reassigns the host of a round robin or managed event type booking. The
        provided authorization header refers to the owner of the booking.

              Without `userUuid` in the body, an available round robin host is picked automatically.

              With `userUuid`, the booking is reassigned to that user. For a **round robin** booking, the user must be one of the booking's hosts and the booking keeps its `uid`. For a **managed event** booking, the user must be one of the users the managed event is assigned to — list them, along with their availability for the booking's slot, with `GET /v2/bookings/{bookingUid}/reassignment-candidates`. Reassignment moves the booking onto the new host's own child event type, so the original booking is cancelled and **the returned booking has a new `uid`** which you must store in place of the old one. Recurring managed bookings cannot be reassigned yet.

               <Note>Please make sure to pass in the cal-api-version header value as mentioned in the Headers section. Not passing the correct value will default to an older version of this endpoint.</Note>

        If accessed using an OAuth access token, the `BOOKING_WRITE` scope is
        required.
              
      operationId: BookingsController_2026_02_25_reassignBooking
      parameters:
        - name: cal-api-version
          in: header
          description: Must be set to 2026-02-25.
          required: true
          schema:
            type: string
            example: '2026-02-25'
            default: '2026-02-25'
        - name: bookingUid
          required: true
          in: path
          schema:
            type: string
        - name: Authorization
          in: header
          description: >-
            value must be `Bearer <token>` where `<token>` is api key prefixed
            with cal_, managed user access token, or OAuth access token
          required: true
          schema:
            type: string
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ReassignBookingInput_2026_02_25'
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReassignBookingOutput_2026_02_25'
components:
  schemas:
    ReassignBookingInput_2026_02_25:
      type: object
      properties:
        userUuid:
          type: string
          format: uuid
          description: >-
            UUID of the user to reassign the booking to. Omit it to let Cal.com
            pick an available round robin host. For a managed event booking,
            list the eligible users with `GET
            /v2/bookings/{bookingUid}/reassignment-candidates` and pass a
            candidate's `uuid`.
          example: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
        reason:
          type: string
          description: >-
            Reason for reassigning the booking. Only recorded when `userUuid` is
            set.
          example: Host has to take another call
    ReassignBookingOutput_2026_02_25:
      type: object
      properties:
        status:
          enum:
            - success
            - error
          type: string
          example: success
        data:
          $ref: '#/components/schemas/ReassignedBookingOutput_2026_02_25'
      required:
        - status
        - data
    ReassignedBookingOutput_2026_02_25:
      type: object
      properties:
        bookingUid:
          type: string
          example: booking_uid_123
          description: >-
            The reassigned booking's uid. For a managed event booking this is a
            new uid, because the booking is recreated on the new host's event
            type.
        reassignedTo:
          $ref: '#/components/schemas/ReassignedToOutput_2026_02_25'
      required:
        - bookingUid
        - reassignedTo
    ReassignedToOutput_2026_02_25:
      type: object
      properties:
        id:
          type: number
          example: 123
        uuid:
          type: string
          format: uuid
          example: 3f2504e0-4f89-41d3-9a0c-0305e82c3301
        name:
          type: string
          example: John Doe
        email:
          type: string
          example: john.doe@example.com
        displayEmail:
          type: string
          example: john.doe@example.com
          description: Clean email for display purposes
      required:
        - id
        - uuid
        - name
        - email
        - displayEmail

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.