Bayut and Property Finder to Bitrix24: Why API Sync Beats XML Feeds
XML feeds are being phased out in favour of API publishing. See what changes for UAE agencies and how to publish to Bayut and Property Finder from Bitrix24.
- Bayut has told partners it is moving listing publishing from XML feeds to its API. Check the exact date with your Bayut account manager.
- An XML feed is a file a portal pulls on its own schedule. An API is a direct conversation: your CRM sends a change and learns at once whether it was accepted.
- If your listings live in Bitrix24, the safest move is to publish from the CRM through the portals' APIs, with leads flowing back the same way.
- OIA For Real Estate does this for Property Finder, Bayut and dubizzle inside Bitrix24.
What is changing for agencies
For years most UAE agencies sent listings to Bayut and dubizzle by hosting an XML file and letting the portal collect it. It worked, but it was always indirect: you changed a price, then waited for the next pickup and hoped nothing in the file was rejected.
Portals are now moving to API-based publishing. Instead of reading a file, the portal exposes endpoints your system calls to create, update and remove a listing, check a permit number and attach advertising products. Bayut's own developer documentation describes a server-to-server REST API for exactly this, using bearer-token authentication and a rate limit of 60 requests per minute.
XML feed versus API: the practical difference
| XML feed | API publishing | |
|---|---|---|
| How a change reaches the portal | The portal collects your file on its schedule | Your system sends the change immediately |
| Feedback on errors | Found later, listing by listing, in the portal | Returned in the response, so you fix it at once |
| Removing a listing | Drops out of the file, then out of the portal | An explicit delete the portal confirms |
| Permit validation | Often discovered after upload | Can be checked before publishing |
| Leads coming back | A separate mechanism | Webhooks and a leads endpoint on the same API |
Why this matters when your CRM is Bitrix24
Bitrix24 does not publish to UAE portals by itself. Agencies either maintain a script or a feed generator on the side, or pay for a connector. Both approaches break the same way: a listing is edited in the CRM, the sync does not run, and the portal shows a stale price.
Publishing through the API from inside Bitrix24 removes the middle step. The CRM stays the single source of truth, and the portal follows it.
What to look for in a replacement
- Publishes through the portals' own APIs, not a feed you host and have to monitor.
- Covers every portal you use. Property Finder and Bayut, with dubizzle listings handled through the Bayut API.
- Brings leads back automatically, with duplicate protection so one enquiry never becomes three CRM records.
- Retries failures and shows its work, so you can see what synced and what did not.
- Lives inside Bitrix24, so your agents do not learn a second tool.
How OIA For Real Estate fits
OIA For Real Estate is a Bitrix24 app built for UAE agencies. It syncs Property Finder and Bayut listings with your CRM, captures portal leads by webhook into Bitrix24 with duplicate protection and automatic retries, keeps a 90-day lead sync log, and looks up permit numbers through Property Finder's compliance API. CRM widgets and automation robots run inside Bitrix24.
Move off XML feeds before it is urgent
Install the app from the Bitrix24 marketplace and connect your portals.
Install on Bitrix24A short migration checklist
- Ask each portal what applies to your account and when.
- List every system that currently writes to your XML feed.
- Pick one place to publish from, ideally your CRM.
- Connect your portal credentials to the new integration and sync a handful of listings first.
- Check that leads arrive in the CRM once each, then switch the rest over.
Frequently asked questions
Do I need a developer to move from XML to API publishing?
Not if you use an integration that already speaks the portal APIs. You connect your portal account and choose what to sync; there is no code to write.
Will my existing listings disappear when I switch?
They should not. Sync a small batch first and compare it with what the portal shows before moving the rest.
Does this also cover dubizzle?
dubizzle listings are published through the Bayut API, so one connection covers both.
Where do portal leads go?
Into Bitrix24 as leads, deals or contacts depending on your settings, with duplicate protection so repeat enquiries do not multiply.