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

{
  "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 - 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 pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402 - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server - no account, no API key.
• 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.