Platform · Bayut

Bayut Data Scraping

Q: Are these transaction prices?

No. Portal prices are asking prices and price_type is a constant marking them as such. Dubai transaction data exists separately through the Land Department and is a different source with different coverage. Treating asking prices as transactions overstates a rising market and understates a falling one.

Q: How do you handle duplicate listings?

With a cluster identifier and cluster_basis naming what the grouping was built on — permit, attributes or images. Permit-based clustering is strong; attribute and image clustering is weaker. As permits become less visible, more clusters fall back to the weaker basis, and the field makes that visible rather than hiding it.

Dubai listings carry a regulator-issued permit number. It is the most useful field on the page, and it is disappearing from public view.

Bayut data scraping collects property listings, asking prices, agency identity and attributes across Dubai and the wider UAE. What makes this market distinct is regulatory: every Dubai property advertisement must carry a Trakheesi permit number issued by the Dubai Land Department. That field is uniquely useful for listing verification — and as of 2026 it is being withdrawn from public display on the major portals, which changes what a dataset can promise.

Most portal data has no regulator-issued identifier at all. Dubai has one, which is why this page is mostly about it — including the part where it is going away.

Get a free sample See sample data

Free pilot on your own Bayut list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

bayut.jsonl LIVE FEED

{"listing_id":"by-44120","emirate":"Dubai", "community":"Example Community", "permit_number":"7118*** as published", "permit_visible":true, "brokerage_name":"brokerage-a", "price":1850000,"currency":"AED", "price_type":"asking", "duplicate_cluster_id":"cl-8812","cluster_basis":"permit"} {"listing_id":"by-99021", "permit_number":"null","permit_visible":false, "portal_verified_badge":true, "cluster_basis":"attributes_images", "note":"badge is the PORTAL judgement. it is not the regulator record"} {"permit_visible_share":0.638, "share_prior_batch":0.812, "caution":"the field is being withdrawn. we track it rather than let coverage drop silently"}

3 of 484,110 listing rows · UAEpermit visible on 63.8% and falling · tracked per batch · schema v1.1

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Bayut or its owners. Bayut and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

Bayut at a glance

How we handle Bayut specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Portal: Bayut — Dubai and the wider UAE
The distinctive field: Trakheesi permit number, issued by the Dubai Land Department
Why it matters: It ties a listing to a licensed broker and an authorised owner
The change: Permit numbers are being withdrawn from public display on major portals
What we do about it: Report the visible share, per batch. Never infer a permit
Duplicates: Permit data is part of how portals detect them. Less visible means harder
Asking price: An asking price, not a transaction price. Stated on every record
Refresh: Daily. Dubai listing turnover is high and permits expire

Platform specifics

A regulated identifier, and what happens when it stops being public

These are the reasons a Bayut dataset needs its own handling rather than a shared retail schema.

The permit number is the most useful field on a Dubai listing

Dubai requires a Land Department permit for every property advertisement. The permit ties the advertisement to a licensed brokerage, an authorised owner instruction and a specific property.

For anyone working with listing data, that is unusually valuable:

It is a regulator-issued identifier, not a portal-generated one.
It supports duplicate detection — portals themselves use permit information as part of deciding whether two listings are the same property.
It is verifiable independently through the Land Department's own channels.

No other market on our real-estate coverage has an equivalent.

And it is being withdrawn from public display

Through 2026, permit numbers have been disappearing from public view on the major Dubai portals, with the direction moving toward portal-side verification badges rather than a raw number a third party can check.

That materially changes what a dataset can offer, and we would rather say so than sell a field that is becoming unavailable.

So we report the visible share rather than promising the field

Our position on this is the same one we take on gated pricing at Whole Foods and app-only rates at Agoda.

We capture the permit number where it is publicly displayed, as published.
Where it is not, the field is null with a reason — not inferred, not reconstructed from anything else.
We report permit_visible_share per batch, so a programme built on that field knows what proportion it is actually getting, and can see it change over time.

What we will not do

Reconstruct a permit number, treat a portal verification badge as equivalent to one, or represent a badge as regulatory confirmation. A badge is the portal's assessment. A permit number is the regulator's record. They are different things and conflating them would put a platform's judgement in a field that looks official.

Where a portal displays a verification badge, we capture it as portal_verified_badge — clearly its own field, clearly not the permit.

Asking price, duplicates, and what UAE listing data is not

Asking, not transaction

Portal prices are asking prices. Dubai transaction data exists separately through the Land Department and is a different source with different coverage.

price_type is a constant asking on every record. A market analysis that treats portal asking prices as transaction prices will overstate the market in a rising phase and understate it in a falling one.

Duplicates

The same property is frequently advertised by more than one brokerage. Where permit numbers are visible, they are the strongest available signal that two listings are one property. As they become less visible, duplicate detection falls back to attribute and image matching, which is weaker.

We flag duplicate_cluster_id with cluster_basis naming what the grouping was built on — permit, attributes, or images — so the confidence is visible rather than assumed.

What we never collect

Agent names, agent phone numbers, agent photographs or any individual's details. Brokerage name is a commercial entity and is collected; the individual is not, in this market or any other.

Scope

What we collect on Bayut, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

Listings with asking price, attributes and brokerage identity
Trakheesi permit number where publicly displayed, as published
permit_visible_share reported per batch, so the trend is visible
Null with a reason where a permit is not displayed
portal_verified_badge as its own field, never equated with a permit
duplicate_cluster_id with cluster_basis naming what it was built on
price_type constant asking, on every record
Property attributes — size, beds, community, completion status
Listing first_seen and last_seen, with archive_limited flagged

❌ What we do not, and why

A permit number reconstructed or inferred
A portal badge represented as regulatory confirmation
An asking price presented as a transaction price
Agent names, phone numbers, photographs or individual details
Transaction records, which are a separate Land Department source

Core Bayut fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
listing_id / portal	The listing and where it was observed
permit_number / permit_visible / permit_visible_share	As published, whether it was, and the batch share
portal_verified_badge	The portal's own assessment. Not the permit
brokerage_name	A commercial entity. No individual agent data
price / currency / price_type	Asking price, with the type constant
emirate / community / building	Geography as the portal presents it
size_sqft / bedrooms / bathrooms	As published
completion_status	Ready or off-plan, where stated
duplicate_cluster_id / cluster_basis	Grouping, and what it was built on
first_seen / last_seen / archive_limited	Lifecycle, with the honest caveat
observed_at	Timestamp

Use cases

What teams do with Bayut data

Listing verification while the signal lasts

Permit numbers where publicly displayed, with the visible share tracked per batch so you can see the field's availability declining rather than discovering it through a silent drop in coverage.

Duplicate detection with stated confidence

Clusters built on permit where available and on attributes or images where not, with the basis named so a weaker grouping is not treated as a strong one.

Asking-price market tracking

Asking prices across communities with the type stated, which is a real signal provided nobody downstream mistakes it for transaction data.

Brokerage activity analysis

Which brokerages list what, where and at what price points — using commercial entity names only, with no individual agent data.

The 24-hour sample — run on your sources, not ours

Send us a Bayut item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.

Bayut is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Bayut data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what real estate data covers, and a Bayut-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

Bayut data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

Dubai requires a Land Department permit for every property advertisement. It ties the ad to a licensed brokerage, an authorised owner instruction and a specific property.

That makes it a regulator-issued identifier rather than a portal-generated one, and it is the strongest available signal that two listings are the same property. No other market in our real-estate coverage has an equivalent.

Decreasingly. Through 2026 permit numbers have been disappearing from public display on the major Dubai portals, with the direction moving toward portal verification badges rather than a raw number a third party can check.

We report permit_visible_share per batch so you can see the availability changing rather than discovering it through a silent drop in coverage.

We capture it, as its own field, and we do not treat it as equivalent. A badge is the portal's assessment; a permit number is the regulator's record.

Conflating them would put a platform's judgement into a field that looks official, which is exactly the kind of quiet substitution we avoid everywhere.

No. Portal prices are asking prices and price_type is a constant marking them as such. Dubai transaction data exists separately through the Land Department and is a different source with different coverage.

Treating asking prices as transactions overstates a rising market and understates a falling one.

With a cluster identifier and cluster_basis naming what the grouping was built on — permit, attributes or images. Permit-based clustering is strong; attribute and image clustering is weaker.

As permits become less visible, more clusters fall back to the weaker basis, and the field makes that visible rather than hiding it.

We quote individually on listing volume, communities in scope and refresh. Daily is usually right here — Dubai listing turnover is high and permits expire on a fixed window.

One scoping call, a free pilot within 24 hours including the current permit visible share, then a fixed monthly quote. Request a quote.

See real Bayut data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner