> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developer.fortresstech.io/api-reference/units/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developer.fortresstech.io/_mcp/server.

# Units Overview

> Overview of the Units API endpoints and functionality

The Units API provides endpoints for managing and interacting with individual rental units within properties.

## Key Concepts

### Unit Status

Units can be in various states throughout their lifecycle:

* `VACANT_READY`
* `VACANT_NOT_READY`
* `OCCUPIED_ON_NTV`
* `OCCUPIED_NO_NOTICE`
* `DOWN`
* `PROPERTY_MODEL`
* `PROPERTY_OFFICE`
* `NON_PRODUCTIVE`

### Unit Address

Each unit exposes its physical address, both as individual components and as a
single pre-formatted string:

* `streetAddress1` — Primary street address line (street number and name)
* `streetAddress2` — Secondary line (apartment, suite, or building number)
* `city` — City in which the unit is located
* `state` — State or province
* `zipCode` — Postal / ZIP code
* `fullAddress` — Human-readable address composed from the components above,
  joined with commas. Blank components are omitted (e.g. a missing
  `streetAddress2` is skipped), and the field is `null` when the unit has no
  address information at all.

### Unit Availability

Available by Request

The `/properties/{propertyId}/availableUnits` endpoint lists the units that are
currently available for a property, including quoting rent, availability
dates, amenities, and floor plan details. The response is wrapped in an
envelope with two top-level fields:

* `meta` — summary information about the result set, including
  `applyNowEnabled`, `propertyType`, the total `count` of available units, and
  the property's current `special` (null when there is no current special).
* `data` — the array of available units.

This endpoint always returns the complete set of currently available units
for the requested property. Filtering, sorting, field selection, and
pagination are not supported.

> **Note**
>
> This endpoint is part of our evolving API ecosystem.
> To explore availability for your integration, please contact our team.

## Available Endpoints

| Endpoint                                                                               | Summary                             | Method |
| -------------------------------------------------------------------------------------- | ----------------------------------- | :----: |
| [`/properties/{propertyId}/units`](/api-reference/units/list-units)                    | List all units for a property       |   GET  |
| [`/properties/{propertyId}/units/{unitId}`](/api-reference/units/read-unit)            | Read Unit                           |   GET  |
| [`/properties/{propertyId}/availableUnits`](/api-reference/units/list-available-units) | List available units for a property |   GET  |

> Overview of the Units API endpoints and functionality


## API Docs

- Units [List Available Units](https://developer.fortresstech.io/api-reference/units/list-available-units.md)
- Units [List Units](https://developer.fortresstech.io/api-reference/units/list-units.md)
- Units [Read Unit](https://developer.fortresstech.io/api-reference/units/read-unit.md)

## OpenAPI Specification

The raw OpenAPI 3.1 specification for this API is available at:
- [OpenAPI JSON](https://developer.fortresstech.io/openapi.json)
- [OpenAPI YAML](https://developer.fortresstech.io/openapi.yaml)