UAE Property Broker Contacts — MX-Checked Emails + Phones

Get real UAE property broker contacts from PropertyFinder: name, agency, email, phone and profile URL — with every email checked against the domain's mail records (MX) and tagged valid / invalid.

This actor reads public, logged-out PropertyFinder list pages (no login, no proxy) and extracts the broker contacts that agencies publish alongside their listings. Great for real-estate outreach, lead lists, CRM imports and market research in Dubai, Abu Dhabi and the wider UAE.

What you get

Each dataset row contains:

Field	Description
brokerName	Broker name as shown on PropertyFinder
agency	Agency / company name
email	Broker email address
emailStatus	valid / invalid — based on an MX lookup of the email domain
phone	Phone number (+971 format) when available
profileUrl	Link to the broker's PropertyFinder profile
activeListings	Number of active listings, when available
city	City searched
sourceUrl	The list page the contact was found on
lastSeen	Date the contact was collected

How it works

1. Builds PropertyFinder list-page URLs from your input (city, purpose, property type).
2. Fetches each page (server-rendered HTML, logged out — no proxies needed).
3. Extracts broker cards: name, agency, email, phone, profile URL.
4. Runs an MX check on every email domain and tags it valid / invalid.
5. Deduplicates by email, drops known junk senders (e.g. site support addresses), and saves the results.

A short delay is kept between requests to stay polite to the source site.

Input

Field	Type	Default	Description
City (required)	string	dubai	Emirate/city, e.g. dubai, abudhabi, sharjah
Purpose	select	rent	rent or buy
Property type	string	properties	e.g. apartments, villas, offices
Max pages	integer	5	How many list pages to crawl (1 page ≈ 17–19 broker emails before dedupe)
Verify emails (MX check)	boolean	true	Tag each email valid / invalid
Only rows with email	boolean	true	Drop brokers with no email found

Example input

{
    "city": "dubai",
    "purpose": "rent",
    "propertyType": "properties",
    "maxPages": 5,
    "verifyEmails": true,
    "onlyWithEmail": true
}

Example output

{
    "brokerName": "Ahmed Al Mansouri",
    "agency": "Downtown Realty",
    "email": "ahmed@downtown-realty.ae",
    "emailStatus": "valid",
    "phone": "+971501234567",
    "profileUrl": "https://www.propertyfinder.ae/en/broker/ahmed-al-mansouri",
    "activeListings": 42,
    "city": "dubai",
    "sourceUrl": "https://www.propertyfinder.ae/en/rent/dubai/properties-for-rent.html",
    "lastSeen": "2026-09-20"
}

Pricing

Pay per event: $0.005 per MX-checked broker contact (a row with an email). You are only charged for rows that contain an email — pages with no results cost you nothing.

Tips

• Use onlyWithEmail: true (default) so you only pay for contactable leads.
• Filter results by emailStatus: "valid" to remove typos and dead domains before outreach.
• Run once per city/purpose combination to build a broad list; re-run weekly to refresh.
• Sample run for testing: maxPages: 1 gives you ~17–19 contacts for under $0.10.

FAQ

Does an email marked valid mean it will reach the inbox? No. The check only asks the email's domain whether it publishes mail-server (MX) records. It does not test whether a specific mailbox exists, and it does not detect catch-all domains or predict bounces.

Where does the data come from? Public, logged-out PropertyFinder list pages (rent or buy, by city and property type). No login, no proxy, no private data.

What are the possible emailStatus values? valid (the domain has MX records) or invalid (no MX records, or the DNS lookup failed). It is empty when you turn off "Verify emails".

Are name and email always correctly paired? Not always. Where PropertyFinder's page data carries the email on the broker record, they are paired exactly. When it does not, the actor attaches the emails it finds on the page to the broker records in page order, and any leftover emails become rows with an empty brokerName. Spot-check a sample before a large outreach.

Am I charged for rows marked invalid? Yes. The charge is one event per delivered row that contains an email, whatever its MX status. Rows without an email are not charged.

Can I search for one agency or one broker? No. You choose city, purpose (rent or buy) and property type, and the actor reads the list pages for that combination.

Errors and limits

• Input handling: purpose is buy or else rent. propertyType is lower-cased and stripped to letters and hyphens (empty falls back to properties). maxPages is limited to 1-200 per city (invalid values become 5). City names such as "Abu Dhabi" and abudhabi are turned into the abu-dhabi URL form.
• Unknown city or type (HTTP 404): that city is skipped with a log warning and the run carries on with the next city. Check the log if a city returned nothing.
• Blocked or failing pages (any other HTTP error, a timeout, rate limiting): the actor stops the whole run at that page, with no retry, and finishes with the rows already saved; any remaining cities are not crawled. Re-run later, or with fewer pages. Each request has a 25 s timeout and there is a 1.5 s pause between pages.
• Empty results are not an error. A run can end as succeeded with an empty dataset (for example when pages load but contain no brokers with an email while "Only rows with email" is on). If pages load but the structured broker data is missing on every page, the log warns that PropertyFinder's page structure may have changed.
• Partial results: rows are saved one by one as they are found, so a stopped run keeps everything delivered so far. If one row cannot be saved it is skipped with a log warning and not charged.
• Charging on failure: a row is charged only after it has been saved to the dataset. If you set a maximum charge per run, the actor stops cleanly when it is reached. Pages that fail, skipped cities and rows without an email are not charged. The Apify actor-start event applies to every run.
• Duplicates: brokers are deduplicated by email (or by name, agency and phone when there is no email), across all cities in the run.
• activeListings: currently always null; the actor does not read that number. sampleListings holds up to 4 listing links from the page.
• Notion output: if the optional Notion step fails, the dataset is still delivered and the reason is logged.

Disclaimer

This actor collects only publicly visible contact information from logged-out public pages, with rate limiting. Please respect applicable privacy laws (e.g. UAE PDPL) when using the data for outreach.

Send results to Notion (new, Sep 2026)

Authorize Notion once in Apify Console → Settings → API & Integrations → MCP connectors (choose Notion, sign in). Then pick that connector in Notion connector and paste the link of any Notion page in Notion page to create the table in. The first run creates a table inside that page and fills it with the broker contacts (up to 500 rows per run; the full set is always in the dataset). To keep adding to the same table on later runs, paste the table ID from the log into Existing Notion table ID. This Actor never sees your Notion login: Apify's connector proxy holds it. If the Notion step fails, your dataset results are still delivered and the reason is logged.

Use it from an AI agent (MCP)

Add this Actor to any MCP client (Claude, Cursor, VS Code) with one URL:

https://mcp.apify.com?tools=leadharbor/uae-property-broker-contacts

Or call it through the Apify API with an input like this:

{
  "cities": [
    "dubai"
  ],
  "purpose": "rent",
  "maxPages": 2
}

Returns one row per UAE property broker: name, agency, MX-checked email, phone and profile URL. Results land in the run's default dataset (JSON, CSV or Excel). No login or API key is needed for the sites it reads, and pay-per-event pricing works with Apify's x402 agent payments.

API usage

Run it from your own code with an Apify API token. The input below is this actor's prefilled example.

curl (runs the actor and returns the dataset items):

curl -X POST "https://api.apify.com/v2/acts/leadharbor~uae-property-broker-contacts/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "cities": [
    "dubai"
  ],
  "propertyType": "properties",
  "maxPages": 2
}'

Python (pip install apify-client):

from apify_client import ApifyClient

client = ApifyClient("<APIFY_TOKEN>")

run = client.actor("leadharbor/uae-property-broker-contacts").call(run_input={
    "cities": [
        "dubai"
    ],
    "propertyType": "properties",
    "maxPages": 2
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Changelog

28 Sep 2026 — Optional Notion output; MCP agent section; old city input no longer prefilled. Plus 5 public example tasks with their own pages.

More from leadharbor

• Google Maps MX-Checked Email Scraper
• YouTube Video Scraper
• Airbnb Listings Scraper
• E-commerce Price & Restock Monitor
• App Store Review Monitor
• Local Review Booster
• Website Contact Extractor
• Bulk Email Verifier
• USA Business Email Finder
• UK Business Email Finder
• UAE Business Email Finder
• LinkedIn Jobs Scraper

---

Using this actor? A quick review helps other buyers find it: uae-property-broker-contacts

Related actors

• Disposable Email & Domain Checker — Flags throwaway and free-provider email domains using 5 merged public lists. $0.30 per 1,000 checks.
• Domain Trust Check — 0-100 trust score for a domain from domain age, SSL, SPF/DKIM/DMARC and disposable-domain lists. $2.50 per 1,000 domains.
• Bulk Email Verifier — Verifies email addresses: syntax, MX, disposable and role flags, and a 0-100 score. $0.50 per 1,000.
• UAE Business Email Finder — MX-checked business emails for UAE companies.
• Website Technology Detector — Detects the CMS, frameworks, analytics and 100+ other technologies a website uses from its homepage. $9 per 1,000 sites.