ILS IntegrationUnit Availability

ILS Unit Availability Response Model

Structure

This model represents the XML response for unit availability, following the MITS 4.1 standard, as used by Fortress for ILS integrations. Below is an annotated XML skeleton showing the structure and required elements.

1<PhysicalProperty>
2    <Property IDType="PropertyID" IDValue="..." OrganizationName="...">
3        <PropertyID>
4            <Identification IDType="PropertyID" IDValue="..."/>
5        </PropertyID>
6        <Information>
7            <Address>
8                <AddressLine1>...</AddressLine1>
9                <City>...</City>
10                <State>...</State>
11                <PostalCode>...</PostalCode>
12            </Address>
13            <Phone>...</Phone>
14            <Email>...</Email>
15        </Information>
16        <File>...</File> <!-- Optional -->
17        <Floorplan IDType="FloorplanID" IDValue="...">
18            <Name>...</Name>
19            <Bedrooms>...</Bedrooms>
20            <Bathrooms>...</Bathrooms>
21            <SquareFeet>...</SquareFeet>
22        </Floorplan>
23        <ILS_Unit IDType="UnitID" IDValue="...">
24            <Rent>...</Rent>
25            <Status>...</Status>
26            <FloorplanID>...</FloorplanID>
27            <Bedrooms>...</Bedrooms>
28            <Bathrooms>...</Bathrooms>
29            <SquareFeet>...</SquareFeet>
30            <AvailableDate>...</AvailableDate>
31            <UnitNumber>...</UnitNumber>
32        </ILS_Unit>
33        <!-- More Floorplan and ILS_Unit elements as needed -->
34    </Property>
35    <!-- More Property elements as needed -->
36</PhysicalProperty>

The response is designed for consumption by Internet Listing Services (ILS) and matches the MITS 4.1 schema. This page documents the XML representation of the response used by the integration. When other formats (such as JSON via a format parameter) are requested, they represent the same underlying data model. For more details and the full standard, visit the MITS Project website.

Key Elements

  • PhysicalProperty: Root element containing one or more properties.
  • Property: Each property includes address, contact info, floorplans, and units.
  • Floorplan: Describes a floorplan available at the property.
  • ILS_Unit: Represents an individual unit, with rent, status, floorplan, and availability details.

XML Example Response

1<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
2<PhysicalProperty>
3    <Property IDType="PropertyID" IDValue="81108fc2-3426-4403-a8da-4fa924d7ac31" OrganizationName="Example Organization Name">
4        <PropertyID>
5            <Identification IDType="PropertyID" IDValue="81108fc2-3426-4403-a8da-4fa924d7ac31"/>
6        </PropertyID>
7        <Information>
8            <Address>
9                <AddressLine1>123 Main St</AddressLine1>
10                <City>Sample City</City>
11                <State>CA</State>
12                <PostalCode>90001</PostalCode>
13            </Address>
14            <Phone>555-123-4567</Phone>
15            <Email>leasing@example.com</Email>
16        </Information>
17        <Floorplan IDType="FloorplanID" IDValue="FP-2BR">
18            <Name>2 Bedroom</Name>
19            <Bedrooms>2</Bedrooms>
20            <Bathrooms>2</Bathrooms>
21            <SquareFeet>950</SquareFeet>
22        </Floorplan>
23        <Floorplan IDType="FloorplanID" IDValue="FP-3BR">
24            <Name>3 Bedroom</Name>
25            <Bedrooms>3</Bedrooms>
26            <Bathrooms>2</Bathrooms>
27            <SquareFeet>1100</SquareFeet>
28        </Floorplan>
29        <ILS_Unit IDType="UnitID" IDValue="105">
30            <Rent>1200</Rent>
31            <Status>Available</Status>
32            <FloorplanID>FP-2BR</FloorplanID>
33            <Bedrooms>2</Bedrooms>
34            <Bathrooms>2</Bathrooms>
35            <SquareFeet>950</SquareFeet>
36            <AvailableDate>2026-02-20</AvailableDate>
37            <UnitNumber>105</UnitNumber>
38        </ILS_Unit>
39        <ILS_Unit IDType="UnitID" IDValue="106">
40            <Rent>1350</Rent>
41            <Status>Available</Status>
42            <FloorplanID>FP-3BR</FloorplanID>
43            <Bedrooms>3</Bedrooms>
44            <Bathrooms>2</Bathrooms>
45            <SquareFeet>1100</SquareFeet>
46            <AvailableDate>2026-03-01</AvailableDate>
47            <UnitNumber>106</UnitNumber>
48        </ILS_Unit>
49    </Property>
50    <Property IDType="PropertyID" IDValue="2222fc2c-1234-5678-9abc-4fa924d7ac31" OrganizationName="Another Management Co">
51        <PropertyID>
52            <Identification IDType="PropertyID" IDValue="2222fc2c-1234-5678-9abc-4fa924d7ac31"/>
53        </PropertyID>
54        <Information>
55            <Address>
56                <AddressLine1>456 Oak Ave</AddressLine1>
57                <City>Other City</City>
58                <State>TX</State>
59                <PostalCode>75001</PostalCode>
60            </Address>
61            <Phone>555-987-6543</Phone>
62            <Email>info@anotherco.com</Email>
63        </Information>
64        <Floorplan IDType="FloorplanID" IDValue="FP-1BR">
65            <Name>1 Bedroom</Name>
66            <Bedrooms>1</Bedrooms>
67            <Bathrooms>1</Bathrooms>
68            <SquareFeet>700</SquareFeet>
69        </Floorplan>
70        <ILS_Unit IDType="UnitID" IDValue="201">
71            <Rent>950</Rent>
72            <Status>Available</Status>
73            <FloorplanID>FP-1BR</FloorplanID>
74            <Bedrooms>1</Bedrooms>
75            <Bathrooms>1</Bathrooms>
76            <SquareFeet>700</SquareFeet>
77            <AvailableDate>2026-02-25</AvailableDate>
78            <UnitNumber>201</UnitNumber>
79        </ILS_Unit>
80    </Property>
81</PhysicalProperty>

Notes:

  • All string fields have maximum lengths as defined in the schema (e.g., AddressLine1: 100 chars, City: 60 chars).
  • Optional fields may be omitted if not applicable.
  • For a full list of possible values and field constraints, see the MITS Core Data 4.1 schema.