Custom TIARA integration development
Appfront builds integrations with TIARA, the NVM's data exchange system through which estate agents pass their listings from their own software on to Funda and others. For estate agency offices 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, receive notifications and errors per property, and pass on changes and statuses such as sold subject to contract. So that a listing isn't entered twice and an error doesn't only surface 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 doesn't match, a notification comes back, and it has to reach the right member of staff. Without proper handling, a home doesn't go online and nobody notices until a seller phones.
We build custom software because the integration has to match your own system: what data you hold and in what format, which types of listings you publish, such as existing homes, new-build and commercial property, how status changes flow through your business, and who needs to see notifications. The NVM sets the access requirements and conditions for TIARA, and we take those into account from the start.
Enter once
Listings and media from your own system, translated into the format TIARA expects, without anyone having to enter them again.
Accurate status
Available, sold subject to contract, sold or withdrawn: a change in your system is passed on to TIARA.
Errors made visible
Notifications and rejections for each listing returned to your system, to the member of staff who manages the property.
How we build your TIARA integration
We start with your listings: which types of property you handle, what data you have, how publishing to the portals works today, and where things go wrong.
Your system and data, the types of listings, your current publishing process, and access to TIARA via the NVM.
Attributes, media and statuses from your system translated into the TIARA format, with checks before sending.
Sending listings and changes, handling notifications and errors, and returning status for each listing to your system.
Testing with real listings, a log for each message, monitoring of failed messages, and then maintenance when the format changes.
What a TIARA integration actually does
The components below appear in almost every TIARA integration. Which ones you need depends on your system and your listings.
Listing data
Attributes, floor areas, prices, energy label and description translated into the TIARA format.
Media
Photos, floor plans and videos in the correct order and format.
Statuses
Available, sold subject to contract, 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.
Feedback returned
Notifications and rejections for each listing returned to your system, to the right member of staff.
Audit log
For each listing and each message, what was sent, when, and with what result.
Who we build TIARA integrations for
The integration is designed for organisations that exchange listings via TIARA without a standard package with a built-in integration.
Estate agents with their own software
Your own system or website as the source. Translation and statuses are the core.
Estate agency software suppliers
A package that must support TIARA. Completeness and testing matter most.
New-build platforms
Projects with many plots. Media and statuses per plot are what's needed.
Commercial property agents
Offices, shops and business premises with their own attributes. Accurate translation 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 choose Appfront for your TIARA integration?
A home that isn't listed online won't sell. That's what we build on: entering your listing just once, statuses that are accurate, and errors that are flagged straight away.
No duplicate entry
Listings go from your own system to TIARA. Nobody has to enter a property twice.
Errors spotted straight away
A rejected listing sends a notification to the staff member. It doesn't go offline unnoticed.
Status always up to date
A sold property no longer appears as available online, because the change is passed on automatically.
Security and privacy for a TIARA integration
The integration processes property data and sometimes data about sellers or landlords. Only what is needed for publication is sent 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 estate agents and software providers ask before getting started.
TIARA is the NVM's exchange system. Estate agents send their listings from their own software through TIARA to, among others, Funda. 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 already supports TIARA, you don't need one.
Access and terms are arranged by the NVM. We discuss the steps, tests and agreements that apply in the first stage and agree them with you before we start building.
The notification comes back to the listing in your system, along with the reason. The staff member can see what has gone wrong and fix it. An upfront check prevents most rejections.
Yes. A change in your system, such as sold subject to contract or withdrawn, is sent to TIARA so the portals show the correct status.
Yes, with projects, plot numbers and media per type. The data you hold for each project determines how the mapping is set up.
A Realworks integration connects the estate agent's CRM with, for example, their own website. A TIARA integration concerns the NVM's exchange system itself. If you use Realworks, you usually already have TIARA through that package.
Enter listings once and publish via TIARA?
Tell us which system you use, which listings you publish and how things work at present. We'll show you what the mapping, statuses and notifications look like.