Dubai Property Scraper — Property Finder UAE Listings

Turn a public Property Finder UAE search page into a clean listings dataset for Dubai market research. Each returned record combines the listing URL, AED price, bedrooms, area, location, brokerage, verification signal, media links, and collection-time provenance so analysts, brokerages, and proptech teams can compare inventory with a stable schema.

Best fit and focused standalone workflow

Choose this actor for a defined Property Finder UAE search that you want to monitor, compare, or export. It is designed as a focused standalone workflow: create the filters on Property Finder, provide the resulting search URL, and receive one structured record per public listing card. Pair it with your own spreadsheet, BI dashboard, or valuation workflow after export when you want to compare price, area, community, and listing status across a saved market segment.

Workflow scenario

A Dubai market analyst starts by filtering Property Finder for apartments for sale in Dubai Islands. They provide that search URL with a 100-listing cap, then export the dataset to compare AED price per area by community and brokerage. Next, they schedule the same input on a regular cadence and feed the records into a dashboard that highlights changes in visible inventory, asking prices, and verification signals.

Input

{
    "searchUrls": ["https://www.propertyfinder.ae/en/buy/dubai/properties-for-sale.html?page=1"],
    "maxResults": 25,
    "maxPages": 1
}

searchUrls accepts Property Finder UAE search pages. maxResults is the strict cap for returned, billable listing records. maxPages controls pagination for each supplied search URL; begin with one page, validate the dataset shape, then scale the cap for the market segment you need.

Data returned

Group	Fields	How to use them
Identity	listingId, listingUrl, title, listingType, propertyType	Join records across exports and open the public listing page.
Price and size	price, currency, pricePeriod, bedrooms, bathrooms, area, pricePerArea	Compare asking prices and unit economics.
Location	locationName, city, community, latitude, longitude	Segment a market by geography.
Market signals	agencyName, isVerified, isAvailable, furnishing, completionStatus, reraPermitNumber	Filter and interpret the public listing context.
Provenance	sourceUrl, sourceFetchedAt, amenities, imageUrls	Trace each record to its source search and collection time.

Output example

{
    "listingId": "116387285",
    "listingUrl": "https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-116387285.html",
    "title": "Exclusive | Spacious | Contemporary",
    "listingType": "Residential for Sale",
    "propertyType": "Apartment",
    "price": 2700000,
    "currency": "AED",
    "bedrooms": 2,
    "bathrooms": 3,
    "area": 1318,
    "areaUnit": "sqft",
    "city": "Dubai",
    "community": "Dubai Islands",
    "agencyName": "McCone Properties",
    "isVerified": true,
    "sourceUrl": "https://www.propertyfinder.ae/en/buy/dubai/properties-for-sale.html?page=1"
}

Every run also provides an OUTPUT record and a RUN_SUMMARY record in the default key-value store. They describe the outcome, item counts, pagination progress, cost-event counts, and source diagnostics alongside the dataset.

Pricing

This actor uses Pay per event plus platform usage. One validated listing written to the dataset is priced at $0.004 and the actor-start event is $0.00005. A 25-listing cap therefore has up to $0.100 in listing-event charges plus the start event; platform usage covers the run's compute and proxy resources. See the live Pricing tab for the current event pricing and platform-usage details before scheduling a larger collection.

API call

curl "https://api.apify.com/v2/acts/khadinakbar~propertyfinder-listings-scraper/runs?token=YOUR_APIFY_TOKEN" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "searchUrls": ["https://www.propertyfinder.ae/en/buy/dubai/properties-for-sale.html?page=1"],
    "maxResults": 25,
    "maxPages": 1
  }'

Once collection completes, read the default dataset for listing records and the OUTPUT record for the terminal outcome. The sourceUrl and sourceFetchedAt fields provide provenance for every item.

AI agent prompt

Call khadinakbar/propertyfinder-listings-scraper for Dubai apartment listings using this Property Finder UAE search URL. Return up to 50 records, group results by community, include AED price per area, and report the dataset readback, terminal outcome, collection time, source URL, pagination cap, and event cost scope.

For MCP and AI-agent workflows, keep maxResults aligned with the decision you need to make. Read a representative dataset page first, then use listingId and sourceUrl as the provenance keys when passing results into an analysis or dashboard step.

Best results

Provide a specific saved Property Finder UAE search URL for the district, property type, price band, and bedroom range you want to study. Start with a small cap to confirm the market segment, then schedule the same input for repeatable snapshots. Use the stable listingId plus sourceFetchedAt to separate fresh records from an earlier collection.

Builder's note

I designed this actor around Property Finder's server-delivered listing payload rather than fragile page-card selectors. My goal was to preserve a compact, analysis-ready contract while retaining source URL and collection-time provenance, so a market workflow can validate where each row came from before comparing it with earlier exports.

Responsible use

Use public data in accordance with applicable laws, Property Finder site terms, and your organization's data policy. Keep collection purposes specific, authorized, and aligned with the expectations of the relevant market participants.