For brokerages in Dubai and Abu Dhabi
Bayut API integration that publishes your listings and brings leads back
Your listings go from your own CRM to Bayut, dubizzle and Property Finder, and every portal enquiry comes back into that CRM with its lead type recorded.
From AED 13,500excl. VATSee pricing →
- Official Bayut feed and Leads API
- Duplicate-permit check before publish
- All six Bayut lead types stored
- Trakheesi, Madhmoun and ADGM fields
- Keys and data on your accounts
- ★ 4.9 on Google (76 reviews)Lucknow, India profile
- 200+ projects since 2017
- Top Rated on Upwork, 100% Job Success
Founder-led delivery
Overview
On Bayut that means its two official integration points, the XML listing feed and the Leads API. On Property Finder it means Enterprise API 2.0, through whichever route your CRM qualifies for. Everything runs on your agency's own portal accounts, and permit and duplicate checks run before Bayut reads the feed, so a bad row is caught before it spends a credit.
By Ashish Sharma, founder · Updated 12 October 2026
Quick answer
Does Bayut have an official API that a brokerage can use to post listings and receive leads?
Bayut has two official integration points for brokerages (as of 12 October 2026): an XML listing feed that syncs listings from your CRM to Bayut and/or dubizzle, and a Leads API that returns your enquiries. The feed is a public URL your CRM publishes and Bayut reads. Profolio agencies request the Leads API from support@bayut.com, and a WhatsApp-only version is available on request. Bayut emails its full XML documentation to the agency instead of publishing it. The RapidAPI 'Bayut API' products scrape Bayut's website and cannot post a listing or deliver your leads.
- The XML integration syncs to Bayut and/or dubizzle
- Bayut sets no pull limit on the Leads API
- Property Finder is a separate job: Enterprise API 2.0
- Since January 2026, a duplicate permit can cost credits Bayut won't refund
- Since July 2026, phone and WhatsApp views drop out of Profolio's default lead counts
01of 10
Which ‘Bayut API’ are you looking at?
Search 'Bayut API' and the first results are documentation sites with keys, pricing tiers and JSON samples. They look official. docs.bayutapi.com says its data comes from scraping Bayut's website, and bayutapi.dev calls itself unofficial and not affiliated with Bayut.
When a brokerage asks me to price a 'Bayut API' job, I first check which of these five they mean. A scraper and a feed are different jobs.
| What it is | Run by | Publishes your listings | Delivers your leads | Published cost |
|---|---|---|---|---|
| bayutapi.com and its docs site | Third party; says it scrapes Bayut | No | No | Free for 750 calls a month; USD 15 or USD 40 tiers |
| bayutapi.dev | Third party, unofficial | No | No | 900 free requests a month; paid tiers in USD |
| Bayut XML listing feed | Bayut, reading a URL your CRM publishes | Yes, Bayut and/or dubizzle | No | Not published |
| Bayut Leads API | Bayut, for Profolio agencies | No | Yes, six lead types | Not published |
| WhatsApp-only lead API | Bayut, on request | No | WhatsApp leads only | Not published |
Ruby CRM describes a Bayut 'Push API'. Bayut's help centre documents none, so ask any vendor offering one for Bayut's written confirmation.
A scraper gives you other agencies' public listings, never your own leads, and it is not a route Bayut documents. If read-only market data is what you want, those products are built for it. Everything below is about your own listings and enquiries.
02of 10
Your agency asks. The portal decides.
Property Finder's API for agencies is Enterprise API 2.0. Its help centre, as indexed on 12 October 2026, says shortlisted CRMs connect with a key made in PF Expert, while other software is pointed to a sandbox and the Property Finder Developer Network (PFDN). On both portals, no developer can switch access on. Your agency asks, from its own account. We aren't a Bayut or Property Finder partner, and don't need to be.
Property Finder with a shortlisted CRM
The Enterprise API 2.0 article, as indexed, names a shortlist of CRMs, PropSpace and Pixxi among them, that connect with a production key from PF Expert > Developer Resources > API Credentials. It sits behind a bot check, so we read the current wording with you before scoping.
Property Finder with custom software
PFDN's guide lists six steps: application, eligibility review, a security and compliance audit, the API Access Terms & Conditions, documentation with test credentials and sandbox endpoints, then go-live once PF Expert clients authorise access. Test credentials come only after the audit and terms steps. No fees or timeline are published, so nobody can honestly promise a date.
Which route your build uses
If your CRM is already on the shortlist, keep it for Property Finder and build only the Bayut side. You skip PFDN onboarding. Otherwise the route, and who applies, goes into the written scope before you sign.
| Portal and job | Route | Who in your agency acts | What isn't published |
|---|---|---|---|
| Bayut and dubizzle listings | XML feed at a public URL | Profolio account holder, by email to support@bayut.com | Full XML spec (sent by email) |
| Bayut leads | Leads API, pulled by your CRM | Profolio account holder | Endpoint documentation |
| Property Finder, shortlisted CRM | Enterprise API 2.0 key in PF Expert | A Decision Maker, up to 3 active keys (per PF's help centre, seen 12 Oct 2026) | Technical docs outside PF Expert |
| Property Finder, custom software | PFDN onboarding | The agency or its developer, as set in the written scope | Fees, timeline, endpoint list |
Not sure which route fits your CRM? Send its name on WhatsApp and I'll tell you.
03of 10
What Bayut reads from your feed
Bayut reads whatever your CRM publishes, so mistakes go live too. A listing corrected in the CRM flows through without anyone telling Bayut support, and so does an error. New agents in the feed are created in Profolio as 'Invited', so a typo in an email becomes a stray user. PropSpace notes that publishing fails unless each agent's CRM details exactly match their portal account.
Off-plan stock has four published tags. The last column is our mapping, not a Bayut rule.
| Bayut tag | Allowed values | Required when | CRM field we map it from |
|---|---|---|---|
| offplanDetails_saleType | New or Resale | Any off-plan listing | Deal type |
| offplanDetails_dldWaiver | 0 to 100 | Off-plan New | Developer's DLD-fee waiver (%) |
| offplanDetails_originalPrice | Original price | Off-plan Resale | Price the seller paid the developer |
| offplanDetails_amountPaid | Amount paid | Off-plan Resale | Paid to the developer so far |
Tag names are from Bayut's off-plan guideline for CRM listings, updated 16 September 2026. A unit bought off-plan and now resold carries saleType Resale with originalPrice and amountPaid filled in.
Left out on purpose: the Trakheesi and Madhmoun tag names, how often Bayut reads the URL, and whether Arabic fields exist. Those sit in the documentation Bayut emails the agency. We build Arabic right-to-left sites with a bilingual QA pass, but Arabic inside the feed depends on Bayut's spec.
Have a project in mind?
Send a few lines on WhatsApp or get a fixed AED quote.
04of 10
Permit numbers the feed must carry in Dubai, Abu Dhabi and ADGM
Every reason Bayut lists for a red status is a permit problem, and each jurisdiction issues its own. This table comes from Bayut's help centre and official notices read on 12 October 2026. Where a rule isn't published, it says so.
Red and yellow on Bayut
Red means a purpose mismatch, no DLD result, an invalid or expired permit, or a project permit on a rental. Bayut removes the listing. Yellow means the permit exists but location, price, area or type differs, or a project permit sits on a sale. A new listing failing the Instant Check goes to Rejected Listings and uses no credits.
Fix it in the CRM, not in Profolio
For CRM-fed listings, Bayut says a changed permit number goes in the CRM. Recheck is for the same number once it is valid again after renewal. So the correction screen we build sits in your CRM.
Madmoun is not Madhmoun
Dubai's Madmoun is a RERA QR code on each Trakheesi permit, required on print and audiovisual ads since 24 April 2023. Abu Dhabi's Madhmoun is an ADREC permit, mandatory for every property advert there since 7 July 2025, and ADREC warned of legal and administrative measures for violations.
The penalty figure on record
In October 2020, DLD reported progressive fines of AED 50,000 per company for advertising without a permit, manipulating permit numbers or using expired ones. No newer published schedule turned up in our research.
What carrying the permit means
Trakheesi, Madhmoun, BRN and ORN are fields our feed carries, not a compliance badge. The permit stays the brokerage's responsibility.
| Location | Permit | Issued by | Date | What to know |
|---|---|---|---|---|
| Dubai | Trakheesi ad permit | DLD, through Trakheesi | – | Licence registered on Trakheesi first; Bayut matches the permit against DLD data |
| Dubai print and audiovisual ads | Madmoun QR code | RERA (DLD), via Trakheesi | From 24 April 2023 | Not Abu Dhabi's Madhmoun |
| Abu Dhabi | Madhmoun permit | ADREC, under DMT | From 7 July 2025 | At most three approved brokers per listing |
| ADGM (Al Reem, Al Maryah) | ADGM Advertising Permit on AccessRP | ADGM Registration Authority | Announced 21 August 2025 | Integrated with Madhmoun (Aletihad) |
| Sharjah, Ajman, RAK, UAQ, Fujairah | Not verified | – | – | Checked against the portal's documentation before mapping |
05of 10
Bayut rules (2025–2026) that cost credits or change your lead counts
| Rule | Date on Bayut's help centre | Effect | What the build does |
|---|---|---|---|
| Duplicate listings | Introduced January 2026 | Since January 2026, duplicates matched on details such as the DLD permit get no TruCheck or TruPoints and may need extra credits, not refunded after a fix | De-duplicate by permit before publishing |
| TruLeads | July 2026 | Since July 2026, phone views, WhatsApp views and SMS leads are left out of default counts | Store the lead type |
| First to Bayut | Article updated June 2026 | 30 TruPoints for the first listing per permit and purpose in 90 days | Optional publish order |
| Credit reversal | Documented July 2025 | Credits revert if Bayut's team rejects a listing within 10 days of posting | Watch Rejected Properties after go-live |
Our build compares permit numbers across live listings before the feed is generated, and holds back the second listing for a person to decide.
06of 10
Six lead types, three of which Profolio now counts
Bayut's Leads API sends six lead types. Profolio's TruLeads classification (July 2026) leaves three of them out of its default counts.
Why the two reports disagree
If your CRM counts all six, its numbers won't match Profolio's, and your agents will argue about it. Every record we store carries its lead type, so a report can filter like the 'Is TruLead?' column in Profolio's lead-log export.
Polling and de-duplication
Bayut sets no pull limit, so I agree the interval with you before the build. If agents call WhatsApp leads within minutes, the CRM must pull often enough to keep up. Pulls are matched on the lead identifier in Bayut's documentation plus phone number, so a buyer who calls twice isn't two records. Unmatched leads go to one named default agent, a pattern PropSpace uses too.
Property Finder leads
Enterprise API 2.0 lists receiving leads. A Bitrix24 Marketplace app describes webhooks signed with HMAC-SHA256, but that is a vendor's description, not Property Finder's documentation. We build to the docs issued with your keys or sandbox.
Lead data is personal data
Lead names and numbers are personal data under the UAE's Federal Decree-Law No. 45 of 2021. DIFC firms fall under DIFC Data Protection Law No. 5 of 2020, ADGM firms under the ADGM Data Protection Regulations 2021. Where the lead database is hosted goes into the project agreement before you sign.
Where this job stops
At a lead saved with its type. Qualifying it on WhatsApp is a separate build, on our chatbot page.
| Leads API type | Counted as a TruLead by default | Stored in the CRM as |
|---|---|---|
| Email lead | Yes | Enquiry |
| Call log | Yes (connected, missed, not connected) | Enquiry, with outcome |
| WhatsApp lead | Yes, as a tracked message | Enquiry |
| Phone view | No | Intent signal |
| WhatsApp view | No | Intent signal |
| SMS click | No | Intent signal |
07of 10
Where a failed listing turns up in Profolio
A feed that passed at launch breaks later when a permit expires or an agent leaves. Listings that fail to sync are counted in Profolio's Notification Panel and sit under Rejected Properties with the Sync Failed filter, each with its reason. The fix goes into the CRM and flows back through the feed.
Bayut's help centre (article dated July 2025) says credits revert when Bayut's team rejects a listing within 10 days of posting, so watch those ten days after go-live. Our validator runs before Bayut reads the URL: permit present, off-plan tags complete, no permit repeated among live listings, each agent email matching a portal user. Who gets its alerts, how long we monitor and response times for failures are set in the written scope.
Our day runs 08:30–17:30 Gulf Standard Time, Monday to Saturday (10:00–19:00 in India, 1 hour 30 minutes ahead), so a broker's 9:00–18:00 day and ours share eight and a half hours, Saturdays included.
Have a project in mind?
Send a few lines on WhatsApp or get a fixed AED quote.
08of 10
Eight rows to check in your own listings export
Each check maps to a published portal or permit rule, named in the last column. Run them on a spreadsheet of your active listings before you pay anyone.
| Check | How to spot it | What happens | Rule |
|---|---|---|---|
| Two live listings with one permit number | Sort by permit | No TruCheck, possible extra credits | Bayut duplicates |
| A rental on a project permit | Purpose rent, permit type project | Red; removed | Bayut permit status |
| A permit near expiry | Sort by expiry date | Red once expired | Bayut permit status |
| Off-plan resale without original price or amount paid | Filter off-plan + resale | Required tags missing | Bayut off-plan guideline |
| Off-plan new without the DLD waiver | Filter off-plan + new | Required tag missing | Bayut off-plan guideline |
| Price, area or community unlike the permit | Compare with the permit record | Yellow | Bayut permit status |
| Agent email unlike the portal account | Compare with PF Expert and Profolio users | Publishing fails, or a stray 'Invited' user | PropSpace guide; Bayut |
| Abu Dhabi listing with no Madhmoun number | Emirate Abu Dhabi, permit blank | Advert without its permit | ADREC |
If you'd rather I check it, keep the permit, purpose, price, size, community and off-plan columns, delete owner names and phone numbers, and swap agent emails for consistent placeholders (agent1, agent2). Then send it on WhatsApp and I'll mark the rows likely to be rejected, removed or flagged under these rules.
09of 10
Keeping HubSpot or Zoho next to PropSpace or PF Expert
If your pipeline is in HubSpot or Zoho and your listings are in PropSpace, you don't have to pick one. Decide which system owns the portal connection.
Start with who edits listings day to day. If that's your PropSpace users, and PropSpace's published AED 220 per user per month (AED 500 minimum) suits you, leave PropSpace on the portals. The open question is whether PropSpace exposes contacts and deals through an API or export your HubSpot or Zoho account can use. We check that, and your plan's integration limits on the vendor's own page, before quoting.
If your own CRM or website should own the feed, it publishes the Bayut XML and takes a Property Finder route from above. Prices are then edited in one place.
If you only need portal leads in an existing CRM, connectors exist: one on the Bitrix24 Marketplace lists lead sync at AED 99–499 a month (vendor's listing, May 2026). A build makes sense when your CRM must publish listings, check permits first or keep leads in a database you own. Still choosing a CRM? See CRM software in the UAE.
10of 10
Whose account the feed runs on
Nothing to transfer at handover
The feed runs on your hosting. Your Decision Maker makes the Property Finder key. The Bayut login and the lead database are yours. At handover we pass over every login we set up and remove our own access.
When a developer leaves
Have your Decision Maker rotate the Property Finder keys. The Enterprise API 2.0 article describes a limit of 3 active keys, so a forgotten key holds a slot. Change the Bayut credentials the CRM uses too. Our hiring page lists the feed credentials to collect.
Built from Lucknow
Codingclave Development LLP was founded in 2017 by Ashish Sharma in Lucknow, India, and has no UAE office, entity or licence. We work WhatsApp first, plus email and video calls. The deliverable lives on your accounts, so our location doesn't change who controls it.
4.9 on Google (76 reviews), 200+ projects since 2017, Top Rated on Upwork, founder-led delivery. See reviews, about us, working with a team in India and our UAE hub.
Pricing in AED
Priced per CRM, since the portals charge nothing for access
Bayut and Property Finder publish no fee for feed or API access. That isn't free: your listings still spend credits.
I quote these connections myself. A connection to a system you already run is quoted after a short discovery call, a video call where we look at your export and CRM together, then fixed for that scope. What moves the price: Bayut alone or with Property Finder, which Property Finder route applies, whether your CRM has an API, agent and listing numbers, the off-plan share, and whether you want the validator and alerts.
Payment: 40% to start, 40% once a milestone we name up front is passed (say, the test batch), 20% at launch. With that last payment, all source code and IP for the feed, validator and lead database become your brokerage's. If a bug of ours stops a listing syncing or loses a lead within six months of launch, we put it right free of charge.
New builds have bands: a brokerage website plus CRM is AED 13,500–98,000, a custom CRM AED 12,500–88,000, and a WhatsApp bot that qualifies portal enquiries AED 4,900–59,000. See the CRM page and software and CRM costs in AED.
Bayut XML feed and Leads API on your existing CRM or website
Quoted after a short discovery call
Excl. VATBayut XML feed and Leads API on your existing CRM or website · Fixed in writing once the scope is agreed
Feed built to Bayut's documentation with permit, off-plan and duplicate checks, plus a lead pull storing each lead type.
Get a quote for this plan
Property Finder Enterprise API connection
Listings and leads through the route in your scope, built to the docs issued with your keys or sandbox.
HubSpot or Zoho sync beside PropSpace
Contacts and deal stages, where PropSpace exposes them. Checked before quoting.
Real estate website + CRM
Brokerage listings website plus CRM, with portal feeds scoped within the band. 4–10 weeks.
AI chatbot (website or WhatsApp)
A WhatsApp bot that qualifies portal enquiries and writes them to the CRM. 2–6 weeks.
- Fixed price in AED
- Free scoping call
- No obligation
A portal rule added after launch, like January 2026's duplicate rules, is new scope with its own fixed price. Hosting, backups, monitoring and support for the feed run AED 200–600 a month; care for a brokerage website we built is AED 600–1,800 a month. Your agency pays each dirham invoice from its bank to our AED account.
Prices are in UAE dirhams (AED) and exclude VAT. Project prices are converted from our GBP price list at GBP 1 = AED 4.90 (11 October 2026) and rounded; monthly plans are set in AED. Codingclave is an India-based supplier and is not registered for UAE VAT. VAT-registered UAE businesses usually account for VAT on imported services under the reverse-charge mechanism; confirm with your tax adviser.
Fixed AED quote
Which portal connection do you need?
Send its name and who holds the Property Finder Decision Maker role, and I'll tell you which access route applies and what the connection involves. If an anonymised listings export is ready, send that too.
Ashish Sharma
Founder, Codingclave
Ashish or the team replies on WhatsApp or email during our hours, Mon–Sat, 8:30am–5:30pm GST.
- ★ 4.9 on Google (76 reviews) · Lucknow, India profile
- 200+ projects since 2017
- Top Rated on Upwork, 100% Job Success
- Founder-led delivery
Prefer WhatsApp?
WhatsApp AshishYour export and two names
You send an anonymised export and name who holds PF Expert's Decision Maker role and who owns the Profolio account.
Access, requested by your agency
The agency emails support@bayut.com, and Property Finder access follows the route in your scope. Neither portal publishes how long this takes. Whether our build starts before or after access is granted is set in the scope.
Field map signed off
Every CRM field is mapped to a tag beside its permit, off-plan and duplicate rules. The price is fixed against that map, the timeline is written in, and the first 40% is paid.
A small live test batch
Bayut's help centre describes no test environment, so unless its emailed documentation offers one, the test is a few listings you choose. They use your credits. The batch passes when Sync Failed is empty, nothing is red, and CRM leads reconcile with Profolio's TruLeads export.
Full feed live, ten days watched
The full feed goes live, and Rejected Properties is watched through Bayut's 10-day credit-reversal window, as the scope sets out.
Final 20%, code handed over, our access removed
The last 20% falls due at launch; once it's paid, your agency owns the code and IP outright. We remove our own access, yet a defect in our build found within six months of launch is still ours to fix free.
FAQ
Questions UAE businesses ask us
Can’t see yours? Ask Ashish directly — you’ll get a straight answer, not a sales script.
Ask Ashish directly
Where do I get a Bayut API key?
Are the 'Bayut API' sites on RapidAPI official?
Is the Bayut API free, and what does a Bayut integration cost?
How do I get a Property Finder API key?
Do we need to join the Property Finder Developer Network?
How long does a Bayut or Property Finder integration take?
Why don't our CRM's lead counts match Profolio's?
What is the difference between a Trakheesi and a Madhmoun permit number?
Ashish Sharma · Founder
Which CRM do your agents publish from?
Send its name and who holds the Property Finder Decision Maker role, and I'll tell you which access route applies and what the connection involves. If an anonymised listings export is ready, send that too.
- WhatsApp us or fill in the form
- Free scoping call
- Fixed AED quote, no obligation
- ★ 4.9 on Google (76 reviews) · Lucknow, India profile
- 200+ projects since 2017
- Top Rated on Upwork, 100% Job Success
- Founder-led delivery
Keep exploring
- UAE
Codingclave for UAE businesses
- Service
Custom CRM for Dubai sales teams
- Service
Qualifying portal enquiries on WhatsApp
- Price guide
Software and CRM prices in AED
- Service
Dedicated developers with Gulf-hours overlap
- Service
Designing listing and search screens
- UAE
Ask for a fixed quote
- Guide
Choosing a real estate CRM in Dubai
- Guide
CRM software options in the UAE
Ashish Sharma
Founder, Codingclave · Updated 12 October 2026
Ashish founded Codingclave in Lucknow, India, in 2017 and still leads delivery on every project.
Sources (12)· public sources cited on this page
- Bayut Help Centre – What is the Leads API?
- Bayut Help Centre – How many times can our CRM pull the data from the leads API?
- Bayut Help Centre – Our listings are posted through our own CRM. What are the guidelines for posting an Off-plan listing?
- Bayut Help Centre – How to add the Madhmoun Permit on your listings in your CRM?
- Bayut Help Centre – Permit status article (invalid, red)
- Bayut Help Centre – Duplicate listings article (January 2026)
- Bayut Help Centre – TruLeads article (July 2026)
- Bayut Help Centre – Credit reversal for rejected listings (July 2025)
- Property Finder Developer Network – Integration guide
- Property Finder Help Centre – What is Enterprise API 2.0? (behind a bot check; seen as indexed 12 Oct 2026)
- Aletihad – Madhmoun permit system comes into force (8 July 2025)
- Government of Dubai Media Office – DLD provides Madmoun service to verify real estate ads via QR codes (18 April 2023)