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

# List unavailable slots

> Explain why a scheduling link has no open slots. For each date of a month, or of one day, the response lists the open time ranges and the blocked ones with the reason for each, such as a holiday, a date override, an existing booking or a connected calendar event.

With a user session, only a host of the scheduling link or a workspace admin can call this.


<Info>Replace `{your-subdomain}` with your workspace’s subdomain. <br /> Learn how to find your subdomain in [Workspace subdomain](/api/workspace-subdomain).</Info>


## OpenAPI

````yaml bundled/slots.yaml GET /meetings/{meeting_sid}/unavailable-slots
openapi: 3.0.3
info:
  title: NeetoCal Slots APIs
  version: 2.0.0
servers:
  - description: NeetoCal APIs
    url: https://{your-subdomain}.neetocal.com/api/external/v2
    variables:
      your-subdomain:
        default: spinkart
        description: >-
          Replace **spinkart** with your [workspace's
          subdomain](/api/workspace-subdomain).
security: []
tags:
  - name: Slots
    description: APIs to manage slots availability of a scheduling link.
paths:
  /meetings/{meeting_sid}/unavailable-slots:
    get:
      tags:
        - Slots
      summary: List unavailable slots
      description: >
        Explain why a scheduling link has no open slots. For each date of a
        month, or of one day, the response lists the open time ranges and the
        blocked ones with the reason for each, such as a holiday, a date
        override, an existing booking or a connected calendar event.


        With a user session, only a host of the scheduling link or a workspace
        admin can call this.
      parameters:
        - $ref: '#/components/parameters/api_key_header'
        - in: path
          name: meeting_sid
          description: >
            The unique identifier (SID) of the scheduling link. You can get this
            from the response of the [List scheduling
            links](/api/scheduling-links/list) endpoint.
          required: true
          schema:
            type: string
            example: vj5pgkh
        - in: query
          name: time_zone
          description: Time zone, in IANA format, in which times are given.
          required: true
          schema:
            type: string
            example: America/New_York
        - in: query
          name: year
          description: Year to check, between 2000 and 2100.
          required: true
          schema:
            type: integer
            example: 2026
        - in: query
          name: month
          description: Month to check, from 1 to 12.
          required: true
          schema:
            type: integer
            example: 10
        - in: query
          name: day
          description: >-
            Day of the month, from 1 to 31. If omitted, every date in the month
            is returned.
          required: false
          schema:
            type: integer
            example: 19
        - in: query
          name: host_email
          description: >
            To check a particular host only, for scheduling links with more than
            one host. The email must belong to one of the scheduling link's
            hosts, otherwise the request is rejected with a 422 error.
          required: false
          schema:
            type: string
            example: oliver@example.com
        - in: query
          name: duration
          description: >-
            Slot length in minutes. Must be one of the durations the scheduling
            link offers. Defaults to its default duration.
          required: false
          schema:
            type: integer
            example: 60
      responses:
        '200':
          description: OK - Request succeeded
          content:
            application/json:
              schema:
                type: object
                properties:
                  dates:
                    type: array
                    items:
                      $ref: '#/components/schemas/unavailable_slots_date'
              example:
                dates:
                  - date: '2026-10-19'
                    available_time_ranges: ''
                    day_reasons:
                      - reason: holiday
                        holiday_name: Company offsite
                        booking_sid: null
                        client_name: null
                        meeting_name: null
                        calendar_event_title: null
                        calendar_name: null
                        booking_limit_level: null
                    blocked: []
                  - date: '2026-10-20'
                    available_time_ranges: 10:30-17:00
                    day_reasons: []
                    blocked:
                      - from: '09:00'
                        to: '10:30'
                        host_email: oliver@example.com
                        reason: booking
                        holiday_name: null
                        booking_sid: 8sqtzrs
                        client_name: Emma Smith
                        meeting_name: Product demo
                        calendar_event_title: null
                        calendar_name: null
                        booking_limit_level: null
        '403':
          description: >-
            Forbidden - With a user session, the caller is neither a host of the
            scheduling link nor a workspace admin.
        '404':
          description: Not Found - The scheduling link does not exist.
        '422':
          description: >-
            Unprocessable Entity - A parameter is missing or invalid, or
            `host_email` is not a host of the scheduling link.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
components:
  parameters:
    api_key_header:
      in: header
      name: X-Api-Key
      description: >-
        Use the X-Api-Key header to provide your workspace API key. Refer to
        [Authentication](/api/authentication) for more information.
      required: true
      schema:
        type: string
  schemas:
    unavailable_slots_date:
      type: object
      properties:
        date:
          type: string
          format: date
          example: '2026-10-19'
        available_time_ranges:
          type: string
          description: >-
            Open time ranges of the date as `HH:MM-HH:MM`, joined by a comma and
            a space. Empty when nothing is open.
          example: 10:30-17:00
        day_reasons:
          type: array
          description: Reasons that block the whole day, such as a holiday.
          items:
            $ref: '#/components/schemas/unavailable_slots_reason'
        blocked:
          type: array
          description: >-
            Blocked time ranges, in time order. Neighbouring ranges with the
            same host and reason are merged.
          items:
            allOf:
              - $ref: '#/components/schemas/unavailable_slots_reason'
              - type: object
                properties:
                  from:
                    type: string
                    description: Start of the blocked range, `HH:MM`.
                    example: '09:00'
                  to:
                    type: string
                    description: End of the blocked range, `HH:MM`.
                    example: '10:30'
                  host_email:
                    type: string
                    nullable: true
                    description: >-
                      Host the range is blocked for. `null` when it is blocked
                      for every host.
                    example: oliver@example.com
    unavailable_slots_reason:
      type: object
      description: >-
        Why a time cannot be booked. Keys that do not apply to the reason are
        `null`.
      properties:
        reason:
          type: string
          description: Why the time is blocked.
          enum:
            - past_time
            - outside_booking_window
            - host_availability
            - outside_range
            - holiday
            - host_availability_override
            - lead_time
            - booking_limit_reached
            - booking_limit_reached_day
            - booking_limit_reached_week
            - booking_limit_reached_month
            - duration_exceeds_availability
            - duration_exceeds_member_availability
            - booking
            - booking_before_buffer
            - booking_after_buffer
            - calendar_event_before_buffer
            - calendar_event_after_buffer
            - slot_before_buffer
            - slot_after_buffer
            - google_calendar_event
            - outlook_event
            - icloud_event
            - icloud_event_travel_time
            - booking_limit_per_slot_reached
            - overlapping_group_slot_booking
            - unknown
          example: holiday
        holiday_name:
          type: string
          nullable: true
          description: Name of the holiday, for `holiday`.
        booking_sid:
          type: string
          nullable: true
          description: SID of the booking that takes the time, for booking reasons.
        client_name:
          type: string
          nullable: true
          description: Client of that booking.
        meeting_name:
          type: string
          nullable: true
          description: Scheduling link of that booking.
        calendar_event_title:
          type: string
          nullable: true
          description: Title of the calendar event, for calendar reasons.
        calendar_name:
          type: string
          nullable: true
          description: Calendar the event belongs to.
        booking_limit_level:
          type: string
          nullable: true
          description: >-
            Level of the booking limit that was reached, for booking limit
            reasons.

````

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