Custom TIARA integration development
Appfront builds integrations with TIARA, the exchange system of the NVM (the Dutch association of estate agents) through which estate agents pass their listings from their own software on to Funda, among others. For estate agencies with their own software, software vendors who want to connect their package to TIARA, and organisations that want to use listings from TIARA: enter properties once, send data in the TIARA format, get notifications and errors back per property, and pass on changes and statuses such as sold subject to contract. So listings are not entered twice and an error is not only noticed when a customer calls.
What is a TIARA integration?
TIARA is the NVM's data exchange system. Estate agents enter their listings in their own software, and TIARA passes them on to Funda and other recipients. Most well-known estate agent packages have a TIARA integration built in. If you use your own software, have your own system for new-build projects or are developing a package, you have to build that integration yourself. We build TIARA integrations for exactly that.
An integration with TIARA is more than sending data. Properties have many attributes that must match exactly what TIARA expects: property type, floor areas, energy label, media and the correct status. If something is wrong, a notification comes back, and it has to reach the right employee. Without proper handling, a property does not go online and nobody notices until a seller calls.
We build custom because the integration has to fit your own system: what data you have and in what form, which types of listings you publish, such as existing homes, new-build and commercial property, how status changes work for you and who needs to see notifications. The access and conditions that apply to TIARA are determined by the NVM; we take that into account from the start.
Enter once
Properties and media from your own system, translated into the format TIARA expects, without anyone having to enter them again.
Status that is correct
Available, sold subject to contract, sold or withdrawn: a change in your system is passed on to TIARA.
Errors in view
Notifications and rejections per listing returned to your system, to the employee who manages that listing.
How we build your TIARA integration
We start with your listings: which types of property, what data you hold, how it currently reaches the portals, and where it goes wrong.
Your system and data, the types of listing, your current way of publishing, and access to TIARA via the NVM.
The features, media and statuses from your system translated into the TIARA format, with a check before sending.
Sending listings and changes, processing notifications and errors, and returning the status per listing to your system.
Testing with real listings, a log per message, monitoring of failed messages, and then maintenance when the format changes.
What a TIARA integration actually does
The components below feature in almost every TIARA integration. Which ones you need depends on your system and your listings.
Property data
Features, floor areas, prices, energy label and description translated into the TIARA format.
Media
Photos, floor plans and videos in the right order and the right format.
Statuses
Available, under offer, sold, let or withdrawn, passed on with every change.
Pre-send checks
Missing or incorrect data flagged before sending, so a listing isn't rejected.
Notifications returned
Notifications and rejections per listing returned to your system, to the right employee.
Log
For each listing and each message: what was sent, when and with what result.
Who we build a TIARA integration for
The integration is intended for parties that exchange listings via TIARA without an off-the-shelf package with a built-in integration.
Estate agents with their own software
Their own system or website as the source. The translation and the statuses are the core.
Estate agency software vendors
A package that needs to support TIARA. Completeness and testing matter most.
New-build platforms
Projects with many building numbers. The media and the statuses per building number are what's needed.
Commercial property agents
Offices, shops and commercial premises with their own features. Getting the translation right is the core.
Technology and integrations
This page covers the TIARA integration. For the estate agent's CRM, see our page on a Realworks integration; for property software in general, our page on property software; and for the file during a transaction, our page on an app for the property file. You can read about our approach at building software.
Why Appfront for your TIARA integration?
A property that isn't online doesn't sell. That's what we build on: enter a listing once, statuses that are correct, and errors that stand out immediately.
No double entry
Listings go from your own system to TIARA. Nobody enters a property twice.
Errors spotted immediately
A rejected listing triggers a notification to the employee. It doesn't quietly stay offline.
Status always in sync
A sold property no longer shows online as available, because the change is passed on automatically.
Security and privacy in a TIARA integration
The integration processes property data and sometimes data about sellers or landlords. Only what is needed for publication goes to TIARA. Access credentials are stored encrypted and can only be used by the integration itself.
The integration runs in a European data centre, with encrypted storage, daily backups and a log of every message. Failed messages are monitored and resent.
Frequently asked questions about a TIARA integration
Questions that estate agents and software vendors ask before getting started.
TIARA is the NVM's exchange system. Estate agents send their listings from their own software via TIARA to portals such as Funda, among others. Many estate agency packages have an integration built in.
If you use or develop your own software that needs to publish listings, such as a proprietary estate agency system, a new-build platform or a package for estate agents. If you use a standard package that TIARA already supports, you don't need this.
The NVM (Dutch Association of Estate Agents) arranges access and terms. We discuss the steps, tests and agreements involved in the first step and agree them with you before we start building.
The notification comes back into your system on the listing, with the reason. The member of staff can see what is wrong and fix it. A check beforehand prevents most rejections.
Yes. A change in your system, such as sold subject to contract or withdrawn, is passed on to TIARA, so the portals show the correct status.
Yes, including projects, building numbers and the media for each type. The data you hold for each project determines what the translation looks like.
A Realworks integration connects the estate agent's CRM to, for example, their own website. A TIARA integration is about the NVM's exchange system itself. If you use Realworks, you usually already have TIARA through that package.
Enter listings once and publish them via TIARA?
Tell us which system you use, which listings you publish and how it works at the moment. We'll show you what the translation, the statuses and the notifications look like.