---
title: "List units for a property"
method: GET
path: "/v2/properties/{property_id}/units"
tags: ["Units v2"]
---

# List units for a property

`GET /v2/properties/{property_id}/units`

Returns a paginated list of units for a specific property.

Use this endpoint to retrieve all units within a property, with support for
cursor-based pagination to handle large result sets efficiently.

**Access Control**: You must have access to the specified property to view its units.

## Path parameters

- `property_id` string, required — The property ID

## Query parameters

- `limit` integer — Number of units to return (max 500)
- `cursor` string — Pagination cursor from previous response. Use the next_cursor value from the previous response to get the next page.

## Response `200`

Successful Response

- UnitsResponse — List of units with pagination metadata.
  - `units` UnitV2WithEntity[], required — Array of unit objects
    - `id` string, required — Unique identifier for the unit
    - `property_id` string, required — ID of the property this unit belongs to
    - `unit_number` string, required — Unit number for display and mail delivery
    - `building_id` string — ID of the building this unit belongs to (matches `buildings[].id` on GET /v2/properties/{property_id}); null when not scoped to a building
    - `entity_id` string — Active GL Catalog entity containing this unit, when available
    - `address` Address, required — Physical address for a property. Structured address components support accurate geocoding and utility provider matching for billing integrations.
      - `street_address` string, required — Street number and name
      - `unit_number` string — Unit/suite/apartment number if applicable
      - `city` string, required — City name
      - `state` string, required — State or province code
      - `postal_code` string, required — ZIP or postal code
      - `country` string — ISO 3166-1 alpha-2 country code
    - `bedrooms` integer, required — Number of bedrooms
    - `bathrooms` number, required — Number of bathrooms
    - `square_feet` integer — Unit square footage
    - `floor` integer — Floor number (ground floor = 1)
    - `building_name` string — Building name or identifier
    - `floor_plan` string — Name of the floor plan
    - `floor_plan_id` string — ID of the associated floor plan
    - `unit_leasing_status` 'available' | 'application_hold' | 'leased' | 'on_notice' | 'not_available' | 'notice_application_hold' | 'notice_leased' — An enumeration.
    - `unit_status` 'ready' | 'renovating' | 'make_ready' | 'occupied' | 'model' | 'offline' — An enumeration.
    - `available_date` string, date — Date unit becomes available
    - `market_rent` number — Market rent amount (not meant for display on websites)
    - `asking_rent` number — Current lowest marketed offer on the unit
    - `created_at` string, date-time, required — When this unit was created
    - `updated_at` string, date-time, required — When this unit was last modified
  - `pagination` CursorMeta, required — Cursor metadata for cursor-based pagination. Use the cursor token to fetch the next page of results. If null, there are no more pages.
    - `next_cursor` string — Opaque cursor token for fetching the next page
    - `has_more` boolean, required — Indicates if more pages are available

## Other responses

- `400` — Bad request - invalid parameters
- `401` — Unauthorized - invalid or missing API key
- `403` — Forbidden - insufficient permissions
- `404` — Not found - resource doesn't exist
- `422` — Unprocessable entity - validation error
- `500` — Internal server error

---

[API](https://skmtc.net/eliseai/apis/elise-api.md) · [All operations](https://skmtc.net/eliseai/apis/elise-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/eliseai/elise-api/revisions/8abbd6b80f99/schema)