Additional
PropertiesAdditional niches properties of products allow studying user preferences and calculating recommendations more accurately. This section describes allowing filling the product feed with niche features of real estate.
Case Sensitivity
| Warning |
|---|
All parameter names are case-sensitive and should follow the spelling used in this documentation. |
Realty
The "realty" element must be inside the "offer" element.
| Code Block |
|---|
|
<offer ...>
...
<realty>
...
</realty>
</offer> |
Price
The "price" element must be inside the "offer" element and have a the value per unit area (1m², 1ft², etc)of the area cost per 1m².
| Code Block |
|---|
|
<offer ...>
...
<price>10.52</price>
</offer> |
Space
Optional parameter <space>. Placed within the <offer> subsection, inside the <realty> section.
Consider the following table of possible values:
ValueThe "space" element must be inside the "realty" element and includes a minimum, maximum and final value of the object's area:
| Element | Metric Units | Description |
|---|
| min | Square Meter | Minimum size |
| max | Square Meter | Maximum size |
| final | Square Meter | Exact size |
| Info |
|---|
title | NOTE| Warning |
|---|
Metric units are always square metermeters, even if the object is a 30 hectares-wide ground area. |
Consider the following example of use:
| Code Block |
|---|
| language | xml |
|---|
| titletheme | XML example |
|---|
| ...
|
<offer ...>
...
<realty>
<space>
<!-- Here can be set minimum and maximum object group size or precise size of a particular object -->
<min>30</min>
<max>100</max>
<final>37</final>
</space>
</realty>
</offer>
... |
Object Floor
Optional parameter <floor>. Placed within the <offer> subsection, inside the <realty> section.
Consider the following table of available subparameters:
| Parameter | Description |
|---|
<current>
Floor
The "floor" element must be inside the "realty" element and includes the current floor of the object and the maximum floors:
| Element | Description |
|---|
| current | Object floor |
<total>| total | Total number of floors in the building |
| Code Block |
|---|
| language | xml |
|---|
| titletheme | XML example |
|---|
| ...
|
<offer ...>
...
<realty>
<floor>
<!-- Object floor -->
<current>3</current>
<!-- Total number of floor in the building
-->
<total>12</total>
</floor>
</realty>
</offer>
... |
Transaction
type Mandatory parameter <action>. Placed within the <offer> subsection, inside the <realty> section.
Consider the following table of possible Type
The "action" element must be inside the "realty" element and can have one of the following values:
| Value | Description |
|---|
| rent | For lease |
| sale | For sale |
| Infowarning |
|---|
If the same realty object is both on sale and lease leases simultaneously, XML-file the product feed should contain two separate objects, each having its own unique ID , and each specifying in the <offer> section in a separate "offer" element with the required type of action (sale, rent). |
Consider the following example of use:
| Code Block |
|---|
| language | xml |
|---|
| titletheme | XML example |
|---|
| ...
|
<offer ...>
...
<realty>
...
<action>sale</action>
</realty>
</offer>
... |
Type of Property
Mandatory parameter <type>. Placed within the <offer> subsection, inside the <realty> section.
Consider the following table of possible
Property Type
The "type" element must be inside the "realty" element and can have one of the following values:
| Value | Description |
|---|
| flat | Flat |
| office | Office |
| warehouse | Warehouse |
| land | Ground area |
Consider the following example of use:
| Code Block |
|---|
| language | xml |
|---|
| titletheme | XML example |
|---|
| ...
|
<offer ...>
...
<realty>
<type>flat</type>
</realty>
</offer>
... |