Bayut and Dubizzle API: connecting leads to your CRM

What Bayut officially offers

Bayut is a large UAE property portal, and Dubizzle is the classifieds site from the same group, which also carries property listings. Bayut's agent app, Profolio, manages listings across both, handles leads and shows market data (see the Bayut Profolio guide). An API is a way for one piece of software to exchange data with another without a person copying it across. Bayut's help centre describes two connections for agencies that run their own CRM, which is the software where you keep clients and deals:

• The Leads API. Bayut says it lets your CRM receive call logs, email leads, phone views, SMS clicks, WhatsApp views and WhatsApp leads. It says the API is available to Profolio users, who request it by contacting support@bayut.com. It also says there is no restriction on how many times your CRM can pull the data. That wording points to a design where your system asks for new leads regularly.
• The XML listing feed. For sending listings the other way, Bayut says feeds must be shared as publicly accessible web addresses, and Bayut's system reads them to pick up updates. This is how a CRM publishes your inventory without agents re-typing it.

Bayut's help pages blocked my automated fetch, so those descriptions come from the page excerpts that search returned. Treat the exact wording as something to confirm with Bayut support when you request access.

What I could not find

• No official Bayut documentation of a lead webhook, meaning a message pushed to you the moment a lead arrives. A third-party connector, PropBridge (a paid add-on for the Bitrix24 business CRM), says it uses a pull API, where your system asks for leads, plus a WhatsApp push webhook for Bayut and Dubizzle. That is the vendor's claim about its own product. Ask Bayut directly if push delivery exists for your account.
• No public price for the Leads API. Ask in writing.
• No public endpoint reference. I expect it is shared when access is granted, as with most portal feeds, but I could not confirm that.

One more warning. Searching for "Bayut API" turns up listings on developer marketplaces for tools that read Bayut's public pages. Those collect public listing data. They cannot publish your listings or deliver your private leads, and they may sit awkwardly with Bayut's terms of use. For your own leads and listings, use the official routes.

Routing leads to the right agent quickly

Getting the data out is half of it. The money is in what happens next. A lead for a two-bedroom in a particular community should reach the agent who holds that listing, or the agent on rota for that area, within a minute. A workable rule set looks like this:

1. If the lead names a listing reference, send it to the listing's agent.
2. If the listing agent is off shift or on leave, send it to the backup you named.
3. If the lead is a general call with no listing, send it to the duty agent on rota.
4. If nobody acknowledges within a set number of minutes, alert the team lead.

Bayut's SmartLeads in Profolio already links email leads and many phone calls to listings, and sorts leads into email, SMS, phone, WhatsApp and chat channels. Your CRM rules sit on top of that, and the combined picture across Property Finder and Bayut is what your owner report needs. To compare the two portals, see Property Finder vs Bayut for brokerages.

Connecting options

• A CRM that already connects. Several property CRMs list Bayut integration. Ask the vendor how leads arrive (pull or push) and what it costs.
• A connector for your existing CRM. PropBridge, for Bitrix24 (a business CRM and task platform), lists Property Finder, Bayut and Dubizzle on its marketplace page, with a free tier of 10 leads and paid tiers in AED. It tells users to get API access from each portal's account manager first. Other connectors exist for other CRMs; check each one's marketplace page for current terms. Bitrix24 users can read how the Bitrix24 API connects to a brokerage setup first.
• A custom connection. Built by a developer against the access Bayut gives you.

Software and AI: from enquiry to the right desk

Here is what software can do on this exact task, and where it stops.

• Software pulls and deduplicates. It polls the Leads API at a short interval, creates the contact in your CRM, and matches the phone number against existing clients so the same buyer who also enquired on Property Finder is one person, not two.
• Software assigns and nudges. It applies the rota rules above, sends the agent a message, and escalates when no one answers. I build this kind of portal-to-CRM connection and the dashboard that reports on it; business process automation explains how those projects run.
• AI sorts the messy part. A WhatsApp lead might say "interested in the 1BR in Jumeirah Village Circle, can I see it Saturday?" AI can pull out the area, bedrooms and requested viewing time and draft a reply for the agent to approve. It cannot be trusted to confirm a price or availability by itself.
• Humans still decide. Which buyers deserve a call-back first, and what to promise.

Do it yourself with Claude

You can test the idea without any connection. Export a week of leads from Profolio (SmartLeads can export to Excel), remove names and numbers, and paste the rows into Claude, an AI assistant, with this request: "For each lead, tell me the area, property type, bedrooms and urgency from the message, and flag any lead where the message is unclear. Then suggest which agent on this list should take it: [your agents and their areas]." You will see quickly whether the rules you want are workable before you build anything.

Questions to ask Bayut before you start

Send these in one email from the Profolio account, and keep the reply.

1. Is the Leads API enabled for our agency, and does it cost anything?
2. Do leads reach us by our system asking regularly, or can they be pushed to us the moment they arrive?
3. Which lead types are included: calls, email, SMS clicks, WhatsApp views and WhatsApp leads?
4. Does each lead carry the listing reference so we can assign it to the right agent?
5. Do Dubizzle leads arrive through the same connection?
6. For listings, what are the rules for our XML feed, and how fast do changes appear on the portal?

Whatever you decide, keep a log of every lead your connection receives and compare it each month with the lead counts Bayut shows in Profolio. If the two numbers drift apart, you are losing leads somewhere between the portal and your agents, and you want to know before a client tells you.

How often should your system ask for leads

If Bayut leads are pulled rather than pushed, the pull interval becomes a hidden delay. LeadSquared (a sales CRM) documents a Bayut connector that pulls leads on a 15 minute default, which you can shorten. Simple arithmetic: with a 15 minute interval, a lead can wait anywhere from zero to 15 minutes before your CRM even knows about it, about 7 minutes on average, and that is before the agent reads the alert. Set the interval as short as Bayut allows (their help centre says there is no limit on how often your CRM pulls, but confirm), and watch your phones as a backup for calls, which the agent hears directly anyway.

Duplicates, retries and sync rules

The CRM connector pages I read share a few settings that decide whether your data stays clean:

• A matching field. Pick one (phone number is common) and optionally a second. If a buyer enquired twice, one record is updated, not two created. Without it, the same person appears as separate leads and gets chased by different agents.
• Create, update or both. LeadSquared offers create-and-update, create-only and update-only. Create-and-update is the usual choice, but create-only is safer if agents edit client records by hand and you don't want a sync overwriting them.
• Failures need a retry route. A lead that fails because a field did not fit your CRM's format is not captured. Someone must see the failure and fix the mapping, then retry. Ask who gets notified.
• Country codes. A number without a country code can be attached to the wrong market. Set a default (for Dubai, the UAE code) and check a sample of records.

Which route fits whom

Your situation	Sensible route
Small team, happy to work inside Profolio	Use Profolio and its SmartLeads inbox, export to Excel monthly, no API needed yet
Already on a CRM with a Bayut connector (HelloLeads, LeadSquared and others advertise one)	Turn that connector on, after asking Bayut support for API access
Bitrix24 user	A marketplace connector such as PropBridge, with portal access requested first
Several agents, several portals, custom reporting	A custom link that merges Bayut, Dubizzle and Property Finder leads into one record

One caution from a vendor page I read: it claimed that phone and WhatsApp views dropped out of Profolio's default lead counts from July 2026. I could not confirm that from Bayut, so when you compare your logged leads against Profolio, check how Profolio counts each lead type first, or you will chase a gap that is only a counting difference.

How I'd approach this

Email support@bayut.com from the Profolio account and ask four questions in writing: is the Leads API enabled for us, is delivery pull or push, what does it cost, and where is the documentation. While you wait, write down your routing rules on a single page, because they are the part no vendor can invent for you. Then decide between a CRM that already connects or a custom link, depending on how many agents and portals you run. If your CRM is going to be Bitrix24 or something similar, a ready-made connector is usually the fastest start.