# Get unit showing availability

Retrieve showing availability for a specific unit, including available and preferred showing windows

Endpoint: GET /showings/availability
Version: 1.1.1
Security: BearerAuth

## Query parameters:

  - `unitId` (number, required)
    ID of the unit to get availability for
    Example: 12345

## Response 200 fields (application/json):

  - `availability` (object)

  - `availability.unitId` (number, required)
    ID of the unit
    Example: 12345

  - `availability.preferredShowingWindows` (array, required)
    Preferred showing windows (e.g., with stacking opportunities)

  - `availability.preferredShowingWindows.start` (string, required)
    Start time of the showing window
    Example: "2024-03-15T10:00:00Z"

  - `availability.preferredShowingWindows.end` (string, required)
    End time of the showing window
    Example: "2024-03-15T10:30:00Z"

  - `availability.preferredShowingWindows.invitedUserIdsArray` (array)
    Array of user IDs invited for this showing window (for accompanied showings)
    Example: ["1259ef6e-61ee-42cb-b6bd-7fe547569d7c"]

  - `availability.preferredShowingWindows.showingMethodsAvailable` (array)
    Available showing methods for this time slot
    Enum: "Accompanied", "Remote Guided", "Remote Guided with Gated Access", "Self Guided"

  - `availability.availableShowingWindows` (array, required)
    Available showing windows

  - `availability.showingMethod` (string, required)
    The showing method configured for this unit
    Enum: "Accompanied", "Remote Guided", "Remote Guided with Gated Access", "Self Guided"

  - `availability.timezoneName` (string, required)
    Timezone name for the unit
    Example: "America/Chicago"

  - `availability.timezoneAbbreviation` (string, required)
    Timezone abbreviation
    Example: "CST"

  - `availability.unitStatus` (string,null)
    Current status of the unit
    Enum: "Available", "Leased", "On Hold", "Archived", "Withdrawn", "Withdrawal Requested", "Incomplete", "Under Review", "Expired", "Price Analysis"

## Response 400 fields (application/json):

  - `error` (string, required)
    Error message
    Example: "Invalid request parameters"

  - `details` (array)
    Detailed error information
    Example: [{"keyword":"required","dataPath":"","schemaPath":"#/required","params":{"missingProperty":"account_id"},"message":"should have required property 'account_id'"}]

## Response 401 fields (application/json):

  - `error` (string, required)
    Error message
    Example: "Invalid request parameters"

  - `details` (array)
    Detailed error information
    Example: [{"keyword":"required","dataPath":"","schemaPath":"#/required","params":{"missingProperty":"account_id"},"message":"should have required property 'account_id'"}]

## Response 500 fields (application/json):

  - `error` (string, required)
    Error message
    Example: "Invalid request parameters"

  - `details` (array)
    Detailed error information
    Example: [{"keyword":"required","dataPath":"","schemaPath":"#/required","params":{"missingProperty":"account_id"},"message":"should have required property 'account_id'"}]