Property Finder API: getting leads into your CRM

What the Property Finder API is

Property Finder is a UAE property portal where agencies list properties and receive buyer and tenant enquiries. An API is a way for one piece of software to talk to another without a person in the middle. In this case it lets your CRM, the system where you keep clients and deals, receive Property Finder enquiries and manage listings automatically.

Property Finder's agent workspace is PF Expert, a platform for listings, leads and performance analytics (see the PF Expert guide for brokerage owners). Two related things exist, and people mix them up:

• Property Finder Developer Network (PFDN). A page aimed at CRM providers, lead management platforms and custom software developers. It says partners can manage listings and handle leads through Property Finder's APIs, and it advertises documentation and sandbox environments. It has a call to become a partner and an Integration Guide, but the public page does not list endpoints or prices.
• Enterprise API (version 2.0). Described in Property Finder's help centre as the option for agencies that use an outside CRM. From the descriptions I could see, keys are generated in PF Expert under Developer Resources, only a Decision Maker can generate them, and only three keys can be active at once. The help article itself blocked my automated fetch, so confirm these details in your own account.

What you can and cannot expect

From what Property Finder and its partners publish:

• Listings can be managed from an outside system. PropSpace, a Dubai property CRM, announced a real-time API connection with Property Finder back in 2019, so listing sync through a CRM is long established.
• Leads can be received by a CRM. PropBridge, a connector for Bitrix24 (a business CRM and task platform) built by VortexWeb, lists Property Finder as connected through the Enterprise API with two-step token authentication, and tells users to ask their Property Finder account manager to enable API access.
• There is a sandbox (a test copy of the system) that has no access to your live data.

And the gaps I found, stated as of 2 November 2026:

• The documentation I could read said lead testing in the sandbox was not supported yet and was planned for the first quarter of 2026. That date has passed, so ask whether it is live.
• The same material said credit data was not yet available through the Enterprise API. If you wanted to pull credit balances into a report, you may have to keep doing that by hand. How credits work is in Property Finder price explained.
• I found no official page for a lead webhook, which would push a lead to you the second it arrives. Check with Property Finder whether leads are pushed or whether your system has to ask for them regularly. The difference matters for response speed.
• Property Finder has not been added to Zapier, a tool that links apps without code, according to a Zapier community thread. A Zapier employee suggested a generic webhook step might work. That was a suggestion, not a confirmed method.

I could not confirm any fee for API access. Ask your account manager in writing.

Three ways to get leads into a CRM

1. Use a CRM that already holds the connection. Several Dubai property CRMs, such as PropSpace, advertise Property Finder integration. This is the lowest effort because the vendor maintains it. The trade is that you live inside that CRM's way of working.
2. Use a ready-made connector for the CRM you have. PropBridge for Bitrix24 is one example. It lists a free tier of 10 leads and paid tiers priced in AED on its Bitrix24 marketplace page; check that page for current prices. You still need API access from Property Finder first.
3. Have a developer build it. If your CRM is custom or you want leads to go to a CRM, a WhatsApp message to the agent and a dashboard all at once, a developer reads the API documentation (shared once you are approved) and builds the link.

Software and AI: from portal lead to first WhatsApp reply

The task worth automating is the first five minutes after a lead arrives. Done by hand, an agent sees an alert, copies the name and number, opens the CRM, creates a contact, tags the listing and then writes to the client. Software can do all but the last step.

• What the software does. It receives the lead, checks whether that phone number already exists in the CRM, creates or updates the contact, attaches the listing reference and Property Finder source tag, assigns an agent by your rule (area, language, rota) and notifies that agent, for example on WhatsApp. WhatsApp messages sent automatically to clients need the official WhatsApp Business route; see my article on the WhatsApp Business API.
• What AI can add. It can draft the first reply from the listing details and the client's message, in English or Arabic, for the agent to approve. It can also summarise a long enquiry. It can get facts wrong, so the agent reads before sending.
• What stays human. Calling the client, judging whether they are serious, and anything about price or availability.

I build this kind of portal-to-CRM-to-WhatsApp connector for brokerages. See AI integration services for how those projects work. It is a modest build when the portal has given you API access, and a much longer wait when it has not.

Do it yourself with Claude

Before paying anyone, you can ask Claude, an AI assistant, to help you scope it. Paste in the Property Finder documentation you were given (never paste API keys) and ask: "Here is the Property Finder API documentation I received. List the lead and listing actions it supports, what each needs from me, and what is missing if I want leads to arrive in my CRM within a minute. Write the questions I should ask Property Finder." Hand the answer to a developer and it saves an hour of discovery.

Questions to ask Property Finder before you start

Send these in one email to your account manager and keep the reply, because verbal answers fade and staff change.

1. Is Enterprise API access enabled for our agency, and is there any fee?
2. Are leads pushed to us when they arrive, or does our system need to check for them? How often may it check?
3. Does the lead record include the listing reference, the channel (call, WhatsApp, email) and the time it was received?
4. Can we test leads in the sandbox yet, or only listings?
5. Who at our agency is the Decision Maker who will generate and hold the keys, and what happens to the integration when that person leaves?
6. What is the process if the connection fails and we miss leads: can missed leads be fetched afterwards?

The last question is the one most owners forget. Any connection will fail one day, usually on a weekend. A good build keeps a log of every lead it received and raises an alert if nothing arrives for a surprisingly long time, because silence is the symptom you will otherwise miss.

Update: push or pull, and what the third-party apps show

Since I wrote the gaps above, I looked at two third-party connectors that suggest lead delivery by webhook (a message Property Finder sends to your system the moment something happens) does exist. The Bitrix24 app "Property Finder Integrator" lists event types for new lead received, lead status updated and lead expired, plus listing and agent events. A LeadSquared (a sales CRM) help article for its Property Finder WhatsApp connector says the CRM generates a webhook address, and your Property Finder account manager or tech team then connects it on their side. Both are vendor descriptions, not Property Finder's own spec, and the LeadSquared route is tied to a paid Property Finder WhatsApp subscription. So the practical point is that the connection is enabled by Property Finder staff, not self-served, and you should ask for it in writing.

The Bitrix24 app also says it can track credit balance and history on its higher plan, which conflicts with the older note that credit data was not available. I can't resolve that from outside your account, so ask which is true today. That app lists $75 a month and $199 a month plans on its marketplace page, with a 7-day free trial. Check the page for current terms, and remember Property Finder still has to enable API access for your agency first.

Setup choices that cause trouble later

• Pick one matching field. Phone number is the usual choice to decide whether an enquiry updates an existing client or creates a new one. Without it you get duplicates, and two agents chase the same person.
• Map agents by email. The Bitrix24 app matches portal agents to CRM users by email address. If an agent uses different emails on the portal and in the CRM, leads go unassigned. Check this before launch.
• Decide who owns the keys. Keys sit with one Decision Maker. Record who that is and what happens when they leave, or the connection dies on their last day.
• Handle changed listings. A lead that arrives for a listing you have already unpublished still needs a reply. Make sure the CRM keeps the listing reference after the listing goes offline.

Owner view versus agent view

An agent wants the lead on their phone fast, with the listing and client message attached. An owner wants every lead logged once, with source and reply time recorded, so cost per closed deal can be worked out later. Design the connection for both: the agent gets the alert, the owner gets the record. Test it by sending yourself a real enquiry on a listing and timing it from tap to alert.

How I'd approach this

Start with the business question: how many portal leads does your brokerage lose to slow handling? If it is a few a month, a ready-made connector or a CRM with the link built in is the sensible choice. If you run many agents and several portals, a custom connector pays for itself in consistency and reporting. In every case, the first step is the same: ask your Property Finder account manager for API access, in writing, with the cost and the lead delivery method (push or pull) stated. Then decide.