Documentation for import feed 2.0.0

In the following document we describe the XML structure that can be used to synchronize property listings from external sources in Indomio.portals.

This document has been structured to break down the information by topics to make it more streamlined and easy to consult.

Important Icons

We have introduced some conventions for the benefit of summary.

IconMeaningPosition on page
ListingOn the left side
AuctionOn the left side
Property up for auctionOn the left side
MandatoryNext to the XPath
DeprecatedOn the left side of a note
Direct link to section of the pageNext to the title
In-depth linkOn the right side of the paragraph
Link to section of the pageOn the right side of the paragraph
Back to main pageOn the right side of the paragraph
Downloadable resourceOn the right side of the paragraph
External pageOn the right side of the paragraph

XML format

Indomio allows agencies' listings to be imported automatically, subject to commercial agreement, from management systems or franchises.

How to submit information is discussed in more detail on a dedicated page.

The following sections describe the information with which you can integrate listings, we recommend validating the resulting feed with the XSD schema available to you for development. Validation is applied on every incoming listing, if it fails this step the listing is discarded. It is therefore advisable to validate the feed after each change.

Each piece of information, complete with compatible values, is contained in the XSD schema. This documentation can therefore be considered a readable translation of the schema itself.

Standard formats

Whenever it has been necessary to use a specific unit of magnitude, we have used universal and well-known standards, possibly applying ISO specifications or W3C guidelines on XML format.

With this in mind, to confidently identify the position each element should occupy within the feed we use the notation known as XPath:

//property/building/@IDType

In general

XML node and attribute names should be written as they are given, respecting upper and lower case letters. Over time we have tried to group information into logical groups, for example geographic attributes are organized within a //location container.

XML header

Each XML call or feed must have indicated the version of the standard itself (1.0), and by the document encoding UTF-8.

<?xml version="1.0" encoding="UTF-8"?>

Numbers

Whole numbers or decimals are expressed without thousand separators. According to the XML standard the dot . should be used as a decimal separator.The sign is needed only for negative numbers

-41.8968348

Flag

Several nodes and attributes can only take the values True or False (fields of type boolean). For them, the allowed values are

true
false

it is important that they all occur in lower case, it is not necessary to use CDATA and it is not recommended to insert spaces or carriage returns before or after these values, ideally:

<price currency="EUR" reserved="false">1000000</price>
...
<workshop>false</workshop>

The treatment of boolean fields conforms to the W3C-defined XML standard.

w3c

Date and time

Date and time (fields of type dateTime) are expressed according to ISO 8601 format:

2013-01-30T12:01:07

In other words: specify year in 4 digits, hyphen, 2-digit month, hyphen, 2-digit day, capital T, 2 digits for hour (00-23), colon, 2 digits for minutes (00-59), colon, 2 digits for seconds (00-59).

Note the T character as separator between date and time. It is not necessary to specify the Timezone. As a quick reference we refer you to the Wikipedia page.

Currency

Although Indomio provides only Euro as a permitted currency, you are always required to specify the currency according to the ISO 4217 standard, consisting of three capital characters.

EUR

Specific fields

Going into the specific details of a property you will find information peculiar to certain property categories. In other words you will find fields that make sense only for certain types of properties and not for others. These nodes are marked with the following icons:

CategoryExpectedUnscheduled
Residential
Buildings / buildings
Garages / parking spaces
Lands
Offices / coworking
Warehouses
Sheds
Stores / commercial premises
Construction sites / new construction

Batch streams (obsolete)

Follow these instruction but add a /feed/properties XML node container. All XPath notations are valid in both modes.

Entering or updating Auction

Below are the specifications of the various xml nodes to be sent to set up the various features of an auction. Where not explicitly stated the absence of an element or attribute in a feed is interpreted as a desire to remove the relevant information.

//auction

Container node of auction type elements to be published or updated

AttributeDescriptionStatus
@operationType of operation required
@IDid listing on Indomio
@source-typeReason for auction
@typeProcedure type.

possible values for @operation:

The write value updates the auction information. If the auction is not found a new listing will be created. The archive value updates the auction information and archives it.

Possible values for @source-type:

possible values for @type:

For Real Time REST calls this node has root function, so each REST call can contain one and only one auction:

<auction ID="12345" operation="write">
  ...
</auction>

In Batch mode it is necessary to send the entire set of auctions, so we will have a variable number of auction nodes structured like this:

<feed>
    <auctions>
        <auction ID="12345" operation="write">
            ....      
        </auction>
        <auction ID="54321" operation="write">
            ....      
        </auction>
        ...
    </auctions>
</feed>

//auction/unique-id

Auction identifier in management, is used to identify the auction. When paired with the agency email, under the responsibility of the sender, it must be unique.

//auction/reference-code

Agency reference code (max 255 characters), is a free text field at the discretion of the client. It is not necessary to guarantee its uniqueness.

//auction/published-on

date of first publication of the auction

//auction/date-updated

date the auction was last updated, must always be updated after each change to the listing.

//auction/agent

agency requesting publication of the listing

//auction/descriptions/description

description of the auction

AttributeDescriptionStatus
@languagedescription language

//auction/descriptions/description/title

title of the listing (max 255 characters)

//auction/descriptions/description/content

description text

//auction/starting-price

starting price of the auction

AttributeDescriptionStatus
@currencycurrency (pass 'EUR')
@reservedspecifies whether price is confidential, if true price will be hidden

//auction/minimum-bid

Minimum bid

AttributeDescriptionStatus
@currencycurrency (pass 'EUR')
@reservedspecifies whether price is confidential, if true price will be hidden

//auction/minimum-bid-challenge

Minimum bid

AttributeDescriptionStatus
@currencycurrency (pass 'EUR')
@reservedspecifies whether price is confidential, if true price will be hidden

//auction/success-price

Minimum bid

AttributeDescriptionStatus
@currencycurrency (pass 'EUR')
@reservedspecifies whether price is confidential, if true price will be hidden

//auction/court

Court of reference for the auction

AttributeDescriptionStatus
@namecourt name
@typetype of court. Possible values are 'court' and 'other'

Extremes of court proceedings

AttributeDescriptionStatus
@yearyear of the proceeding
@numbernumber of the proceeding

//auction/actors

Container of information about the actors in the judicial proceeding

//auction/actors/actor

Actor of the judicial auction

AttributeDescriptionStatus
@typetype of plaintiff
@IDplaintiff id

possible values for @type:

//auction/actors/actor/name

First name of claimant

//auction/actors/actor/lastname

Last name of the plaintiff

//auction/actors/actor/tax-code

Tax identification number of the claimant

//auction/actors/actor/phone

Plaintiff's landline phone

//auction/actors/actor/mobile

Cell phone number of the actor

//auction/actors/actor/email

Actor's email

//auction/actors/actor/fax

Actor's fax

//auction/actors/actor/selling-operations

Indicates whether the actor is enabled for the sale transaction (flag true or false)

//auction/actors/actor/estate-journey

Indicates whether the plaintiff is qualified to visit the property (flag true or false)

//auction/notes

Notes regarding the judicial auction

//auction/lot-number

Auction lot number

//auction/selling-place

Container of geography, for the address of the place of sale.

//auction/depot-conditions

Security deposit information

//auction/depot-out-of-date

Submission deadline

//auction/depot-bills

Expense account deposit, in Euros (EUR). May contain decimal values.

//auction/real-value

Property value from appraisal, in Euros (EUR). May contain decimal values.

//auction/ransom

Value of security deposit, in Euros (EUR). May contain decimal values.

//auction/ransom-bill

Bail expenses, in Euros (EUR). May contain decimal values.

//auction/practice

description

//auction/show-place

Auction submission location

//auction/reference-info

Auction contact person information.

//auction/events

Container node of auction-related events. This is the calendar with the dates on which the auctions are scheduled.

//auction/events/event

Single auction-related event

AttributeDescriptionStatus
@typeType of event
@statusEvent Status.
@modemode of the event

possible values for @type:

possible values for @status:

possible values for @mode:

//auction/events/event/date

Date of event

//auction/events/event/starting-price

Base price

AttributeDescriptionStatus
@currencycurrency (pass 'EUR')
@reservedspecifies whether price is confidential, if true price will be hidden

//auction/documents

Container of auction documents.

//auction/raw-360s

Node containers of the listing's spherical images.

//auction/publish/portal

container of the extra-visibility information (the agency must be enabled to submit). In the absence of the publish node, the visibility of the listing remains unaffected.

AttributeDescriptionStatus
@idthe id of the portal for which you want to set the extra-visibilities
@statusspecifies whether to place the listing in real estate (true) or only in Gestionale (false)

possible values for @id:

Example xml:

<publish>
    <portal id="immobiliare.it" status="true">
      <visibilities>
        <visibility op="active">premium</visibility>
        <visibility op="active">top</visibility>
        <visibility op="remove">showcase</visibility>
      </visibilities>
    </portal>
  </publish>

//auction/publish/portal/visibilities

container of portal-specific extra-visibilities

//auction/publish/portal/visibilities/visibility

specifies a single extra-visibility that you want to add or remove

AttributeDescriptionStatus
@opspecifies the type of operation required for a specific extra-visibility (default: active)

possible values for @op:

possible values for the node:

//auction/estates

Node container of auction properties

//auction/register

Auction log information (lookup). Possible values:

Legal category of real estate. Possible values:

Type of contribution. Possible values:

Container of auction-related links

Description of link

AttributeDescriptionStatus
@urlurl related to the link to be shown

2025 Indomio.com