Connecting the Realworks API: what your agency arranges itself

Before a software vendor may connect to Realworks, your agency must itself subscribe to the API in the Realworks Marketplace and release the contacts the integration may see. After that, the API determines what is possible: there are eight APIs, two of them are export-only, and there is no API for the instruction or the commission.

KeyVue connects to Realworks this way: see what comes along and what your agency does.

Why the agency has to act first

With a Realworks integration, the agency decides which data is shared, not the vendor. A developer can only connect once the agency has subscribed to the API and granted access.

That fits with who Realworks is. The software has been 100% owned by the NVM (the largest Dutch association of estate agents) since 2015, and its own CRM page cites 2,550 offices and 19,000 daily users. In our own survey of 23 August 2026, just over a quarter of estate agency websites show Realworks. So the software holds the client records of a large part of the sector, and access to them rests with the agency that manages the data.

So plan internal time at the start. That time falls to you, not to the vendor. If you don't schedule it, you risk the integration sitting idle for weeks.

Step 1: subscribe to the API in the Marketplace

The first step is for someone with admin rights in Realworks to subscribe to the right API in the Realworks Marketplace. Without that step, no vendor may connect, however ready its software is.

Ask the vendor in writing beforehand which of the eight APIs it needs. Don't subscribe to more than necessary: every extra API gives an extra party access to part of your data.

Record internally who subscribes to the API and who can cancel it later. At an agency with several branches, that is not always the person who chose the software.

Step 2: release contacts

The second step is releasing contacts. Contacts only become visible to an integration once they have been released one by one. So a subscribed API does not yet mean the vendor sees your entire contact database.

That is good for privacy and awkward for planning. Agree:

• which contacts you release, for example all sellers and home seekers, or only some of them;
• who does it, per branch or centrally;
• how you handle contacts added later.

After the first synchronisation, check whether the number of contacts in the integration matches what you expected. A large difference usually points to the release, not to a fault in the software.

What the eight APIs exchange

Realworks has eight APIs, each for its own part of the records. The table shows, per API, what it contains according to Realworks' own API pages (September 2026). Where the direction was not clear from those pages, that is noted.

Importing leads via Wonen or Business is a standard facility. So a vendor being able to put leads into Realworks is no differentiator; the question is what else it does with them.

The newsletter opt-in in the Relatie API has been especially relevant since 1 September 2025. Realworks then discontinued its own newsletter module, and an external platform needs that opt-in to know who you may email. The options are set out in the Realworks newsletter has been discontinued.

What is export-only

Taken and Facturen can only be exported. An integration can read that data from Realworks, but cannot write anything back through these APIs.

If a vendor promises to create tasks or invoices in Realworks, ask how. The answer may hold via another route, but not via these two APIs.

What has no API

Realworks has no API for the instruction or the commission. So an integration cannot read which sales instruction was signed or what it earned.

That has a direct consequence for reporting. The question of which lead source produced an instruction cannot be answered by reading Realworks alone. The instruction has to be linked to the lead and the source somewhere else. How to set up that tracking is covered in which lead source wins instructions, and what to do with it each quarter in the quarterly report for a multi-branch agency.

Questions for a vendor before you connect

Ask a vendor these questions before you subscribe to anything in the Marketplace. The answers determine what your agency needs to arrange and what you can expect from the integration.

If you want to compare vendors side by side, the overview of types of lead software helps. If you are merging two agencies after an acquisition, also read the first hundred days of an integration.

KeyVue synchronises contacts and properties from Realworks and reports conversion by source, branch and agent, including the commission on referrals. Ask in a demo which APIs that requires and how the instruction is linked to the lead.

Frequently asked questions