Property Finder UAE Agent Scraper

Extract public Property Finder UAE agent-directory profiles into JSON, CSV, Excel, or via the Apify API. This Actor is for UAE broker research and public agent rosters. It accepts one or more Property Finder agent search URLs, treats each saved record as one public agent profile, and returns valuable fields such as agent name, agency name, public phone, office address, image URLs, directory position, source search URL, and scrape timestamp.

This is an Apify Actor usable through Apify MCP. Each returned record represents one validated public directory card from Property Finder UAE, with the source page preserved for review and downstream workflows.

Best fit and connected workflows

Use this Actor when your workflow starts from a Property Finder UAE agent-directory page and you want a structured export of the public cards shown there. It fits well with:

• UAE brokerage research based on public directory presence.
• CRM enrichment with public business contact details from agent cards.
• Repeated monitoring of a filtered Property Finder search URL over time.
• Data pipelines that deduplicate agent records by a stable agent key.

If your workflow begins with a Property Finder listings page, a property-level scraper is the better starting point. If your workflow begins with an agent directory search URL, this Actor keeps the directory context intact and paginates through that search.

Practical scenario

Maya is reviewing a Property Finder UAE agent search page filtered to one Dubai area. She pastes the search URL into searchUrls and sets maxResults to 25. The dataset returns records with agentName, agencyName, phone, officeAddress, directoryPosition, and searchUrl. Maya uses the public phone numbers and agency names to update her brokerage research sheet, then stores agentId for deduplication in her next scheduled run.

Input

Field	Type	Description
searchUrls	array of string	One or more Property Finder UAE agent-directory URLs. The Actor preserves filters already present in each URL and paginates that directory.
maxResults	integer	Maximum unique public agent profiles to save across all supplied search URLs. This is a strict cap across the whole run.
maxPagesPerSearch	integer	Maximum directory pages to request for each search URL. This bounds page requests per URL.

Focused input example

{
  "searchUrls": [
    "https://www.propertyfinder.ae/en/find-agent/search"
  ],
  "maxResults": 25,
  "maxPagesPerSearch": 3
}

Output

One validated record is saved for every public agent profile returned and written to the default dataset.

Field	Type	Description
agentId	string	Stable agent key for deduplication across runs.
agentName	string	Agent name shown on the public directory card.
agencyName	string or null	Brokerage or company shown on the card.
phone	string or null	Public telephone number shown by the directory.
officeAddress	string or null	Public office address attached to the card.
agentImageUrl	string or null	Public agent image URL.
agencyImageUrl	string or null	Public brokerage logo image URL.
directoryPosition	integer or null	Position supplied by the page's public structured data.
searchUrl	string	Source directory page for the record.
scrapedAt	string	UTC ISO-8601 timestamp for collection time.

Illustrative output record

{
  "agentId": "a8d63d7e61f8dff0",
  "agentName": "Vincent Soreng",
  "agencyName": "Phoenix Homes Real Estate Brokers LLC",
  "phone": "+971568908360",
  "officeAddress": "Dubai, UAE",
  "agentImageUrl": "https://static.shared.propertyfinder.ae/media/images/agent_image/example.jpg",
  "agencyImageUrl": null,
  "directoryPosition": 1,
  "searchUrl": "https://www.propertyfinder.ae/en/find-agent/search?page=1",
  "scrapedAt": "2026-07-15T12:00:00.000Z"
}

The Actor also writes OUTPUT and RUN_SUMMARY to the default key-value store. Those records summarize the run outcome and include diagnostics and billing counters.

How it works

The Actor collects public Property Finder UAE agent-directory cards from the supplied search URLs, keeps the filters already embedded in those URLs, and paginates the directory pages. It uses validated records and a deterministic agentId so recurring runs can deduplicate the same public identity. The live contract also includes paginated JSON-LD parsing, resume state, and PPE billing.

Pricing

This Actor uses Apify Pay per Event plus platform usage.

• apify-actor-start is charged when the Actor starts.
• agent-profile-returned is charged when one validated public Property Finder agent profile is saved to the default dataset.
• Platform compute and proxy usage are billed separately through Apify.
• The live Pricing tab on Apify shows the current pricing details for this Actor.

For a simple event-count example in words: if a run saves fifty agent profiles, the profile-event portion is fifty times the per-profile rate, plus platform usage.

Use with AI agents (MCP)

This Actor is available as an Apify Actor usable through Apify MCP. The tool scope is a focused public-web extraction workflow for Property Finder UAE agent-directory pages.

Actor identity: khadinakbar/propertyfinder-agent-scraper

A practical MCP prompt:

Scrape the public Property Finder UAE agent directory from this URL, keep the search filters already in the URL, return up to 25 unique profiles, and include the source search URL with each record. I need the public agent name, agency, phone, office address, image URLs, and stable agent key for deduplication.

Output interpretation:

• agentId is the stable record key for recurring runs.
• agentName, agencyName, phone, and officeAddress reflect what Property Finder exposes on the public card.
• searchUrl preserves provenance and helps identify the exact directory page used.
• scrapedAt marks when the record was collected in UTC.

Scope and pagination guidance:

• Use one or more Property Finder agent-directory search URLs.
• The Actor keeps the filters already present in each URL.
• maxResults sets the overall saved-profile cap.
• maxPagesPerSearch bounds directory requests per search URL.
• Start with a small maxResults value when validating a workflow, then scale up as needed.

API example

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor('khadinakbar/propertyfinder-agent-scraper').call({
  searchUrls: ['https://www.propertyfinder.ae/en/find-agent/search'],
  maxResults: 25,
  maxPagesPerSearch: 3,
});

const items = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.items);

Best results and outcome guidance

For the most useful output, start from a Property Finder UAE agent-directory URL that already contains the filters you want. Set maxResults to the number of public profiles you plan to review, and use maxPagesPerSearch to keep each directory sweep focused. For recurring research, compare agentId across runs and use phone, agencyName, and officeAddress as change points when those fields are present.

Continue the workflow

• Then use Property Finder UAE Listings Scraper to extend Property Finder UAE Agent Scraper research with a complementary discovery contract.
• Then use Property Finder Scraper — UAE & MENA Listings to extend Property Finder UAE Agent Scraper research with a complementary discovery contract.

Design note

I found that the output contract centers on a single stable identity field, agentId, alongside the source searchUrl and scrapedAt, which makes the dataset suited to repeatable collection and deduplication.

FAQ

Can this Actor work with a filtered agent search URL?

Yes. Paste the Property Finder UAE agent-directory search URL into searchUrls, and the Actor keeps the filters already present in that URL while paginating the directory.

What kind of records are returned?

Each record represents one public agent directory card from Property Finder UAE, with fields such as agentName, agencyName, phone, officeAddress, and image URLs when present.

Is this Actor useful for property listings?

This Actor is scoped to the agent directory. For listing-level extraction, use a Property Finder listings workflow.

Can I provide more than one search URL?

Yes. searchUrls accepts one or more Property Finder UAE agent-directory URLs, and the cap in maxResults applies across the whole run.

What should I use for deduplication in my pipeline?

Use agentId as the stable key. It is designed for recurring collection of the same public directory identity.

Responsible use

Use this Actor for public Property Finder UAE agent-directory data and for workflows that align with your applicable policies and obligations. Respect website terms, data-handling rules, and any local requirements that apply to public business contact information.