PropertyFinder Listing Lookup

Look up any property listing on PropertyFinder.ae, the UAE's leading property marketplace, by URL — price, bedrooms, bathrooms, size, property type, completion status, location, and agent contact. The listing's full detail set is embedded server-side in a __NEXT_DATA__ JSON payload, so this reads structured data directly rather than scraping rendered HTML.

Features

• URL → full listing record. Title, reference number, property type, and purpose (buy/rent), straight from the page's own data.
• Price & specs. Price, currency, price period, bedrooms, bathrooms, size (sq ft), furnished status, and completion status.
• Location & agent. Full location name, coordinates, and the listing agent's name and phone number.
• Pay only for hits. Listings that don't resolve — removed, or invalid URLs — cost nothing; see Pricing.
• Built for bulk. Feed in a list of listing URLs; concurrency is configurable to stay conservative against the target.

How to use PropertyFinder Listing Lookup — UAE Property Data by URL

1. In the Apify Console. Open the actor page and click Start — the items field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~propertyfinder-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"items":["https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-dubai-hills-estate-elvira-at-dubai-hills-estate-elvira-2-132512758.html"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "items": [
    "https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-marina-132512758.html"
  ],
  "maxConcurrency": 5
}

items is a list of PropertyFinder.ae listing URLs (the /en/plp/... permalink). A bare path without the domain is also accepted. One dataset row is returned per item; rows with "found": false are never charged. proxyConfiguration defaults to Residential proxies. maxConcurrency controls how many requests run in parallel — keep it conservative, since this target has no browser fallback.

Output

One row per listing URL, for example:

{
  "query": "https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-marina-132512758.html",
  "found": true,
  "data": {
    "listingId": 132512758,
    "reference": "PF-DM-4521",
    "title": "Luxurious 2BR Apartment with Marina View",
    "propertyType": "Apartment",
    "purpose": "for-sale",
    "price": 1850000,
    "currency": "AED",
    "pricePeriod": null,
    "bedrooms": 2,
    "bathrooms": 3,
    "sizeSqft": 1450,
    "furnished": "Unfurnished",
    "completionStatus": "Ready",
    "location": "Dubai Marina, Dubai",
    "latitude": 25.0805,
    "longitude": 55.1403,
    "agentName": "Sarah Ahmed",
    "agentPhone": "+971501234567",
    "listedDate": "2026-08-01",
    "url": "https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-marina-132512758.html"
  },
  "scrapedAt": "2026-08-20T10:00:00.000Z"
}

Listings that no longer exist — removed or an invalid URL — still get a row ("found": false), so you always get one row per input, but you're never charged for that.

Use cases

• Price monitoring — track asking prices on a watchlist of listings over time.
• Listing enrichment — attach full property spec and agent contact to a list of listing URLs pulled from search results or a lead list.
• Market analysis — build a dataset of property type/size/price combinations for valuation or comparison work across neighborhoods.
• Agent & listing verification — confirm agent contact details and listing status before reaching out about a property.
• Listing health checks — confirm which URLs in a saved list are still live before running a larger workflow against them.

Pricing

$4 per 1,000 results, plus a $0.005 start fee. Misses (found:false) are never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~propertyfinder-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"items":["https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-dubai-hills-estate-elvira-at-dubai-hills-estate-elvira-2-132512758.html"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~propertyfinder-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"items":["https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-dubai-hills-estate-elvira-at-dubai-hills-estate-elvira-2-132512758.html"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~propertyfinder-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"items":["{{value}}"]}, mapping the row's value into the items array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "PropertyFinder Listing Lookup | Apify" — the agent will find and run this actor.

FAQ

Do I need to log in to PropertyFinder to look up a listing? No. This actor reads the listing's own embedded page data over an HTTP request — no account or API key involved.

What happens if a listing has been removed? You get a dataset row with "found": false — a fabricated or removed listing URL returns a clean HTTP 404 from PropertyFinder, and that row is never charged.

Why does this default to Residential proxies? PropertyFinder.ae has been observed returning HTTP 403 through the shared datacenter proxy pool even when a plain request from a residential IP succeeds, so Residential is the safer default.

What URL format does it accept? The full listing page URL, e.g. https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-marina-132512758.html. A bare path (starting with /en/plp/...) also works — it gets expanded to the full URL automatically.

Can I search by keyword or area instead of a specific listing URL? No — this actor looks up individual listings by their permalink URL. It doesn't crawl search result pages or accept bare listing IDs, since the URL slug isn't derivable from the numeric ID alone.

Does the price field include currency conversion? No — price and currency are returned exactly as PropertyFinder lists them (almost always AED), with no conversion applied.