# PropertyFinder Scraper - UAE Listings & Agent Leads (`scrapesage/propertyfinder-scraper`) Actor

Scrape PropertyFinder.ae property listings: price, size, bedrooms and bathrooms, location with coordinates, amenities, and the listing agent and broker contact (name, email, phone). Paste a search URL, get structured rows. No browser, cents per listing.

- **URL**: https://apify.com/scrapesage/propertyfinder-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Real estate, Lead generation, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.65 / 1,000 listing scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## PropertyFinder Scraper - UAE Listings & Agent Leads

Scrape property listings from **PropertyFinder.ae** (UAE's largest property portal). For each listing you
get the **price**, **size**, **bedrooms/bathrooms**, **location with GPS coordinates**, amenities, and the
listing **agent and broker contact** - name, **email** and **phone**. Build any search on the site (buy or
rent, city, property type, price, beds), paste the result-page URL, and get clean structured rows.

### What you get per listing

| Group | Fields |
|---|---|
| Listing | `title`, `url`, `purpose` (sale/rent), `propertyType`, `reference`, `listedDate` |
| Price | `price`, `currency`, `pricePeriod`, `pricePerArea`, `pricePerAreaUnit` |
| Property | `bedrooms`, `bathrooms`, `sizeValue`, `sizeUnit`, `furnished`, `completionStatus`, `amenities` |
| Location | `locationName`, `city`, `latitude`, `longitude` |
| **Leads** | `agentName`, `agentEmail`, `agentPhone`, `brokerName` |
| Media | `imageUrl`, `imagesCount`, `isVerified` |

### Input

```json
{
  "searchUrls": ["https://www.propertyfinder.ae/en/buy/dubai/apartments-for-sale.html"],
  "maxItems": 500
}
```

- **Search URLs** - build a search on PropertyFinder.ae (filter by buy/rent, city, type, price, beds) and
  paste the result-page URL. One per line. Both the readable `/buy/dubai/apartments-for-sale.html` form and
  the `?c=1&l=1&t=1...` form work.
- **Import from a file** - paste a whole list, or link a public `.txt`/`.csv`, a Google Sheet/Drive link,
  or an Apify key-value-store record.
- **Max results** / **Max pages per search URL** - bound the run.
- **Output fields** - tick only the columns you want (e.g. just the agent contact fields for a lead list).

Leave the URL list empty and the run returns a small free sample so you can see the shape first.

### Reliability

Scraped over plain HTTP - the search page ships the full result set as JSON inside the page, so there is no
browser and no rendering. **PropertyFinder blocks datacenter IPs, so residential proxy is required and is
the default** - leave the proxy setting as-is. A run that returns nothing bills **$0** and says so.

### Honest limits

- **Search-result data only.** Everything on the results page (price, size, location, agent contact) is
  captured; the actor does not open each listing's detail page, so there is no full amenities checklist
  beyond what the card carries or a full description beyond the card summary.
- **Agent contact is what the portal publishes.** `agentEmail`/`agentPhone` come from the listing's public
  contact options; where a listing hides a channel, that field is null.
- **UAE portal.** This targets PropertyFinder.ae (United Arab Emirates).

### Pricing

**$0.003 per listing** on the FREE tier (tiered pricing lowers it with volume). You are only charged for
listings actually saved; a blocked or empty run costs nothing.

### Output views

- **Listings** - title, purpose, type, price, beds/baths, size, location, agent name + phone, and the URL.

### Use with AI assistants (MCP)

Available through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) - an agent can
pull current UAE listings with agent contacts for a given search and hand them to a CRM or outreach flow.

### Agent-ready: autonomous payments (x402 & Skyfire)

This actor is **agent-ready** - AI agents can discover it, run it, and **pay for it autonomously**, with no Apify account and no human in the loop. It uses [pay-per-event](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) - no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/skyfire)** - agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

# Actor input Schema

## `searchUrls` (type: `array`):

PropertyFinder.ae search-result URLs. Build the search you want on the site (buy/rent, city, property type, price, beds), then paste the result-page URL here - one per line. <b>Leave empty and the run returns a small free sample.</b>

## `urlsFromFile` (type: `string`):

Bulk-load search URLs. Either <b>paste the whole list</b> (one per line), or give <b>a single link</b> to a public <code>.txt</code>/<code>.csv</code>, a Google Sheet/Drive link, or an Apify key-value-store record. A file that cannot be read says so and charges nothing.

## `maxItems` (type: `integer`):

Stop after this many listings in total (across all search URLs). You are only charged for listings actually saved.

## `maxPagesPerUrl` (type: `integer`):

How deep to page through each search. A PropertyFinder page holds about 20-25 listings.

## `outputFields` (type: `array`):

Pick the fields you want and every record is trimmed to exactly those - handy for lean CSV/Sheets exports. Open the dropdown and tick, or type to filter (<code>price</code>, <code>agentEmail</code>).

## `proxyConfiguration` (type: `object`):

PropertyFinder blocks datacenter IPs, so <b>Residential proxy is required</b> and is the default. Leave it as-is unless you have your own residential provider.

## Actor input object example

```json
{
  "searchUrls": [
    "https://www.propertyfinder.ae/en/search?c=1&l=1&t=1&fu=0&rp=y&ob=mr"
  ],
  "maxItems": 500,
  "maxPagesPerUrl": 10,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Each scraped record - property listings with agent contacts - as a JSON item in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchUrls": [
        "https://www.propertyfinder.ae/en/search?c=1&l=1&t=1&fu=0&rp=y&ob=mr"
    ],
    "urlsFromFile": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/propertyfinder-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchUrls": ["https://www.propertyfinder.ae/en/search?c=1&l=1&t=1&fu=0&rp=y&ob=mr"],
    "urlsFromFile": "",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/propertyfinder-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchUrls": [
    "https://www.propertyfinder.ae/en/search?c=1&l=1&t=1&fu=0&rp=y&ob=mr"
  ],
  "urlsFromFile": ""
}' |
apify call scrapesage/propertyfinder-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/propertyfinder-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/GXnMv5ZV1UiHt9cFX/builds/0gPoARIfRZAXChfe1/openapi.json
