Dataspryva

Use Property Finder MENA Listings & Agent Contact Extractor with Python

Reads Property Finder listings across the UAE, Saudi Arabia, Qatar, Bahrain, and Egypt, returning price, size, location hierarchy, amenities, and agent or brokerage contact details.

1. Choose the data you need

Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.

2. Prepare a source-based input

This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.

{
  "bedrooms": "any",
  "city": "dubai",
  "completionStatus": "any",
  "country": "ae",
  "furnishing": "any",
  "includeDetails": true,
  "maxItems": 2,
  "mode": "search",
  "propertyType": "apartment",
  "purpose": "buy"
}

Download input.example.json and save your reviewed copy as input.json.

FieldTypeRequiredDescription
modestringrequiredWhat to scrape. Search listings by filters, scrape specific listing URLs, or collect agent/broker profiles.
countrystringoptionalMarket to search or the country used for bare agent/broker ids.
citystringoptionalCity, province or governorate to search. Choose All cities for a country-wide search.
purposestringoptionalBuy, rent, or the commercial equivalents.
propertyTypestringoptionalResidential types: apartment, villa, townhouse, penthouse, duplex, compound, land, whole building, half floor. Commercial types: office, shop, warehouse, factory, showroom.
bedroomsstringoptionalBedroom filter for residential searches. Studio is supported for apartments and mixed-type searches.
priceMinintegeroptionalMinimum asking price in the market's local currency (AED, SAR, QAR, BHD or EGP).
priceMaxintegeroptionalMaximum asking price in the market's local currency.
furnishingstringoptionalFurnished or unfurnished. Leave on Any furnishing to include both.
completionStatusstringoptionalReady or off-plan. Applies to residential for-sale searches; ignored for rentals and commercial searches.
maxItemsintegeroptionalMaximum number of listings or profiles to return.
includeDetailsbooleanoptionalOpen each listing page to add the full photo gallery, permit validation link, licences, floor plans and agent ratings. Turn off for a faster, lighter dataset.
startUrlsarrayoptionalProperty Finder landing, search, listing or short URLs. Used with mode=listings. Sitemap and sitemap-index URLs are also accepted.
agentUrlsarrayoptionalProperty Finder agent profile URLs, or bare numeric agent IDs. Used with mode=agents.
brokerUrlsarrayoptionalProperty Finder broker/agency profile URLs, or bare numeric broker IDs. Used with mode=brokers.

3. Start an Actor run

Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.

Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.

import json
import os
import urllib.request

# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
    actor_input = json.load(stream)

token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
    "https://api.apify.com/v2/acts/6tmA1k9u56N6klleB/runs?timeout=120&maxTotalChargeUsd=0.50",
    data=json.dumps(actor_input).encode("utf-8"),
    headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
    method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
    run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.

4. Inspect the actual results

Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.

Dataset of Property Finder listings, agent profiles and brokerages with prices, location, amenities, permit data, media and public broker/listing contact details.

Questions before you run

Which inputs are required?

The published required fields are mode

What does this guide verify?

The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.

What if the run request times out?

Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.

Generated from source build xMhCXrO7B9kNH6URi and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.