# Get unit leasing performance

Retrieve leasing performance metrics for a specific unit within a date range.

This endpoint provides comprehensive leasing activity data including:
- Days on market
- Property health assessment
- Lead volume and conversion metrics
- Showing activity (scheduled, completed, upcoming)
- Application metrics
- Communication activity (texts, calls)
- Detailed showing feedback from completed showings

Endpoint: GET /reporting/leasing-performance/units/{unitId}
Version: 1.1.1
Security: BearerAuth

## Path parameters:

  - `unitId` (integer, required)
    ID of the unit to get leasing performance for
    Example: 12345

## Query parameters:

  - `start` (string, required)
    Start date/time for the reporting period (ISO 8601 format)
    Example: "2024-01-01T00:00:00Z"

  - `end` (string, required)
    End date/time for the reporting period (ISO 8601 format)
    Example: "2024-01-31T23:59:59Z"

## Response 200 fields (application/json):

  - `unit_id` (integer, required)
    ID of the unit
    Example: 12345

  - `days_on_market` (integer,null, required)
    Number of days the unit has been on the market
    Example: 45

  - `property_health` (string, required)
    Overall health assessment of the property listing
    Enum: "Off-Market", "Healthy", "At-risk", "On Hold", "Waitlist", "Commercial", "Unknown"

  - `benchmark_leads_since_last_price_change` (integer, required)
    Expected number of leads based on bedroom count and time since last price change
    Example: 12

  - `new_prospects` (integer, required)
    Number of new prospects in the reporting period
    Example: 15

  - `showings_scheduled` (integer, required)
    Number of showings scheduled in the reporting period
    Example: 8

  - `showings_completed` (integer, required)
    Number of showings completed in the reporting period
    Example: 6

  - `applications_requested` (integer, required)
    Number of applications requested in the reporting period
    Example: 3

  - `applications_submitted` (integer, required)
    Number of applications submitted in the reporting period
    Example: 2

  - `active_prospects` (integer, required)
    Number of active (non-terminal status) prospects in the reporting period
    Example: 5

  - `upcoming_showings` (integer, required)
    Number of upcoming scheduled showings
    Example: 2

  - `outbound_texts` (integer, required)
    Number of outbound text messages sent in the reporting period
    Example: 25

  - `total_calls` (integer, required)
    Total number of calls in the reporting period
    Example: 10

  - `showing_feedback` (array, required)
    Feedback from completed showings in the reporting period

  - `showing_feedback.prospect_id` (integer, required)
    ID of the prospect who attended the showing
    Example: 789

  - `showing_feedback.prospect_name` (string, required)
    Name of the prospect
    Example: "John Doe"

  - `showing_feedback.created_at` (string, required)
    When the showing was completed
    Example: "2024-01-15T14:30:00Z"

  - `showing_feedback.feedback` (string,null, required)
    Feedback notes from the showing
    Example: "Prospect liked the kitchen but concerned about parking availability"

## 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 429 fields (application/json):

  - `error` (string)
    Example: "Too Many Requests"

  - `message` (string)
    Example: "Rate limit exceeded. Please try again later."

  - `retryAfter` (integer)
    Seconds until rate limit resets
    Example: 45