> ## Documentation Index > Fetch the complete documentation index at: https://developer.zeeg.me/llms.txt > Use this file to discover all available pages before exploring further. # Get Reschedule Availability > List the slots a specific booking can be moved to. Call this before rescheduling, and reschedule to one of the slots it returns. ## OpenAPI ````yaml GET /scheduled-events/{uuid}/reschedule-availability openapi: 3.0.0 info: title: Zeeg Public API description: >- Zeeg public API documentation. ## Authentication All endpoints require a Bearer token. You can generate an API token from [your Zeeg dashboard](https://app.zeeg.me/account/settings/api-access). Each token is scoped to specific permissions (e.g. `events:read`, `webhooks:write`). Make sure your token has the required scopes for the endpoints you want to use. ## Recommended Headers We recommend including the `Accept: application/json` header in all API requests to ensure you receive JSON responses. version: 2.0.0 x-logo: url: https://app.zeeg.me/img/logo-dark.2ca83593.svg backgroundColor: '#f7f7f9' altText: zeeg contact: name: Zeeg Support email: support@zeeg.me url: https://zeeg.me/en/contact license: name: Proprietary url: https://zeeg.me/en/legal/terms termsOfService: https://zeeg.me/en/legal/terms servers: - url: https://api.zeeg.me/v2 description: Production security: - bearer: [] tags: - name: Scheduled Events description: Management of events scheduled via Zeeg - name: Scheduling Pages description: Scheduling pages information and management - name: Availability Schedule description: Read and change availability for users - name: Webhooks description: Webhooks management - name: Notes description: Notes for scheduled events - name: Workspaces & Teams description: Workspace users and team member management - name: AI Agent description: AI Agent integration endpoints - name: Payloads description: Webhook payload schemas - name: CRM - Objects description: >- Discover the schema of CRM objects (standard and custom) including all attribute definitions - name: CRM - Companies description: Create, read, update, and delete CRM company records - name: CRM - People description: Create, read, update, and delete CRM person records - name: Routing Forms - Forms description: Read routing forms with their questions and their routes - name: Routing Forms - Submissions description: Read and delete the submissions that invitees send through a routing form paths: /scheduled-events/{uuid}/reschedule-availability: parameters: - schema: type: string format: uuid example: zg-O69bac566950c6 name: uuid in: path required: true description: UUID of a specific scheduled event (zg-XXX format) get: tags: - Scheduled Events summary: Get reschedule availability for a scheduled event description: >- Returns the available time slots for rescheduling a specific booking. This endpoint exists on v2 only — v1 has no reschedule-availability endpoint. It runs the same slot computation `PUT /scheduled-events/{uuid}/reschedule` writes against, so the slots this endpoint returns are exactly the slots that reschedule endpoint accepts. Call this endpoint first to discover valid slots, then call the reschedule endpoint with one of them. Unlike `GET /availability/{ownerSlug}/event-types/{eventTypeSlug}`, this endpoint does not require the premium `timetable` scope. It reads a property of a booking the caller already owns rather than a scheduling page's public availability, so `events:read` or `events:write` is enough. The booking's own current slot is handled correctly here: because the computation treats this specific booking as the one being moved, its slot is excluded from the busy time that would otherwise make it look taken. `timeZone` defaults to the booking's existing invitee time zone when omitted. operationId: get-api-scheduled-event-reschedule-availability parameters: - schema: type: string format: date example: '2026-04-01' in: query name: startDate required: true description: Start date in YYYY-MM-DD format. - schema: type: string format: date example: '2026-04-14' in: query name: endDate required: true description: >- End date in YYYY-MM-DD format. Must be on or after `startDate`, and at most 90 days after it. A longer range returns 422. - schema: type: string example: Europe/Berlin in: query name: timeZone description: >- IANA time zone identifier. Defaults to the booking's existing invitee time zone when omitted. - schema: type: number example: 30 in: query name: duration description: >- Meeting duration in minutes. The event type ignores an unsupported value and uses its own configured duration instead. responses: '200': description: > OK - Empty slot arrays indicate dates with no availability. - The `isNotAvailable` flag indicates if the booking has no reschedule availability at all during the requested time range. content: application/json: schema: type: object properties: ownerSlug: type: string nullable: true eventTypeSlug: type: string schedulingUrl: type: string format: uri nullable: true duration: type: integer firstAvailableDate: type: string format: date lastAvailableDate: type: string format: date timeZone: type: string timeZoneOffset: type: string isNotAvailable: type: boolean availability: type: array items: type: object properties: date: type: string format: date slots: type: array description: Array of time strings, e.g. "09:00". items: type: string currentTime: type: string format: date-time examples: Reschedule availability for a one-on-one booking: value: ownerSlug: null eventTypeSlug: 30min-discovery-call schedulingUrl: null duration: 30 firstAvailableDate: '2026-04-01' lastAvailableDate: '2026-04-14' timeZone: Europe/Berlin timeZoneOffset: '+02:00' isNotAvailable: false availability: - date: '2026-04-01' slots: - '09:00' - '09:30' - '10:00' - '14:00' - '14:30' - date: '2026-04-02' slots: [] currentTime: '2026-03-20T12:00:00+00:00' '400': description: Bad Request content: application/json: schema: type: object properties: success: type: boolean message: type: string status: type: integer examples: Already cancelled: value: success: false message: Event has already been cancelled! status: 400 Already rescheduled: value: success: false message: The event has been already rescheduled. status: 400 Booking in the past: value: success: false message: The event is in the past. status: 400 '401': description: Unauthorized content: application/json: schema: type: object properties: error: type: object properties: type: type: string message: type: string error_id: type: string examples: Missing or invalid token: value: error: type: unauthenticated message: A valid API token is required to access this resource. error_id: 3d3a9f2b-6c1d-4b8a-9e2f-7a5c1e0d4b6a '403': description: Forbidden content: application/json: schema: oneOf: - type: object description: >- The caller cannot view this booking (fails the ownership/team/organization gate). properties: success: type: boolean message: type: string status: type: integer - type: object description: >- The token is missing both `events:read` and `events:write`. properties: error: type: object properties: type: type: string message: type: string error_id: type: string required_scopes: type: array items: type: string examples: Cannot view booking: value: success: false message: You don't have permission to view this event. status: 403 Missing scope: value: error: type: insufficient_scope message: >- Your token is missing the required scope(s). Include at least one of: events:read, events:write. error_id: ab97b5cd-5732-45b9-b42d-a9e46106dc1d required_scopes: - events:read - events:write '404': description: Not Found content: application/json: schema: type: object properties: error: type: object properties: type: type: string message: type: string error_id: type: string examples: Event not found: value: error: type: not_found message: Entry for Event not found. error_id: a15b5b16-02c6-423b-be78-48627f4b80fe '422': description: Unprocessable Entity content: application/json: schema: type: object properties: message: type: string errors: type: object additionalProperties: type: array items: type: string examples: Missing required fields: value: message: The start date field is required. (and 1 more error) errors: startDate: - The start date field is required. endDate: - The end date field is required. security: - bearer: [] components: securitySchemes: bearer: type: http scheme: bearer description: '' ````