Dubai Property Scraper — UAE Real Estate Listings

Scrape Dubai property listings from PropertyFinder.ae — UAE's leading real estate portal with over 267,000 active listings (148k for sale, 119k for rent). Extract rich structured data including price, GPS coordinates, agent contacts, RERA permit numbers, furnishing status, and more.

What this actor does

• Scrapes for-sale and for-rent property listings across Dubai
• Extracts 22+ structured fields per listing from JSON-LD embedded data (no fragile HTML parsing)
• Returns GPS coordinates (lat/lon) for every listing with location data
• Includes agent name, email, and phone number from contact options
• Captures RERA permit numbers for compliance verification
• Supports pagination to retrieve thousands of listings per run
• Works with custom search URLs for precise filtering by area, price range, or property type

Output fields

Field	Description
listing_id	PropertyFinder unique listing ID
title	Listing headline
price	Price in AED (or per-year for rentals)
currency	Always "AED"
price_per_sqft	Calculated price per square foot
purpose	"for-sale" or "for-rent"
property_type	Apartment, Villa, Townhouse, etc.
bedrooms	Number of bedrooms
bathrooms	Number of bathrooms
area_sqft	Property area in square feet
location	Full location path (tower, community, district, city)
city	City name (e.g. Dubai)
community	Community or district name
sub_community	Sub-community or compound
tower	Building or tower name
latitude	GPS latitude
longitude	GPS longitude
agent_name	Listing agent's full name
agent_email	Agent email address
agency	Real estate agency name
phone	Contact phone number
permit_number	RERA permit / DLD permit number
furnishing	Furnished / Unfurnished / Partly Furnished
completion_status	Completed / Off-Plan / Under Construction
description	Full property description text
amenities	List of amenity names
listing_url	Direct URL to the listing
image_url	Primary listing image URL
images	All image URLs
posted_date	Date listing was posted
scraped_at	ISO timestamp of the scraping run
parse_confidence	Data quality score 0.0–1.0

Input parameters

Required

None — the actor has sensible defaults (Dubai for-sale, 100 listings).

Optional

purpose — "for-sale" (default) or "for-rent"

propertyType — Filter by type: apartment, villa, townhouse, penthouse, duplex, studio, office, shop, warehouse, land, hotel-apartment, full-floor. Default: all types.

maxItems — Maximum number of listings to return. Default: 100. Maximum: 50,000.

searchUrl — A custom PropertyFinder search URL. If provided, overrides purpose and propertyType. Example:

https://www.propertyfinder.ae/en/search?c=1&t=2&l=dubai&pf=5000000&pt=10000000

This lets you filter by price range, specific neighborhoods, bedroom count, and any other criteria the PropertyFinder UI supports.

proxyConfiguration — Proxy settings. The actor works without a proxy from Apify infrastructure. RESIDENTIAL proxy is available as a fallback if needed.

Use cases

• Real estate market research — track price trends by area, property type, and purpose
• Lead generation — extract agent and agency contact information at scale
• Property investment analysis — compare prices, price-per-sqft, and availability across Dubai neighborhoods
• RERA compliance checks — collect permit numbers for regulatory verification
• Mapping and GIS — use GPS coordinates for spatial analysis and visualization
• Competitive intelligence — monitor new listings, price changes, and developer inventory

Technical notes

Transport: PropertyFinder serves full SSR HTML with an embedded __NEXT_DATA__ JSON blob containing all listing data. This actor extracts data directly from that JSON — making it structurally robust against layout changes and HTML refactors.

No API key required. The actor does not require any PropertyFinder or third-party API credentials.

Proxy: Works reliably from Apify datacenter IPs without any proxy. RESIDENTIAL proxy is available as a fallback input option for high-volume runs.

Performance: PropertyFinder returns 20–30 listings per page. The actor paginates automatically. At default settings (100 items), expect ~3–5 pages fetched in 15–30 seconds.

Pricing

Pay-per-result: $0.99 per 1,000 listings scraped.

A 1,000-listing run costs $0.99. Compute costs run on your Apify account (typically $0.05–0.15 for a 1,000-item run).

Sample output

{
  "listing_id": "99959555",
  "title": "Fully Upgraded with Sea and Skyline View",
  "price": 32000000,
  "currency": "AED",
  "price_per_sqft": 12167,
  "purpose": "for-sale",
  "property_type": "Apartment",
  "bedrooms": 3,
  "bathrooms": 4,
  "area_sqft": 2630,
  "location": "Bulgari Resort & Residences 6, Bulgari Resort & Residences, Jumeirah Bay Island, Jumeirah, Dubai",
  "city": "Dubai",
  "community": "Jumeirah",
  "sub_community": "Jumeirah Bay Island",
  "tower": null,
  "latitude": 25.20964813232422,
  "longitude": 55.23322296142578,
  "agent_name": "Kianoush Darban",
  "agent_email": "kia@drivenproperties.com",
  "agency": "Driven Properties",
  "phone": "+971524960123",
  "permit_number": "7121372015",
  "furnishing": "Furnished",
  "completion_status": "Completed",
  "listing_url": "https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-jumeirah-...",
  "image_url": "https://static.shared.propertyfinder.ae/media/images/listing/.../668x452.jpg",
  "posted_date": "2026-06-08",
  "scraped_at": "2026-06-08T12:00:00Z",
  "parse_confidence": 1.0
}

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Onthemarket Properties Scraper
• Realtor Scraper
• Redfin Scraper
• Rightmove Listings
• Zillow Scraper
• Zoopla Properties Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.