# PropertyFinder Listing Lookup — UAE Property Data by URL (`accountable_eel/propertyfinder-listing-lookup`) Actor

Look up any PropertyFinder.ae listing by URL: price, bedrooms, bathrooms, size, property type, completion status, location, and agent contact, read from the listing's own structured page data. Pay only for listings that resolve.

- **URL**: https://apify.com/accountable\_eel/propertyfinder-listing-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Real estate, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.04 / 1,000 successful lookups

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/actors/running/actors-in-store.md#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 Listing Lookup

Look up any property listing on [PropertyFinder.ae](https://www.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](#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:
   ```bash
   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

```json
{
  "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:

```json
{
  "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.

```bash
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.

# Actor input Schema

## `items` (type: `array`):

One item per line — see the item shape and examples below. Only the items we actually find are charged — never per run, and never for a miss.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

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

Apify Proxy config. Defaults to Residential — this target returns HTTP 403 through the shared datacenter proxy pool even though a plain request from a residential IP succeeds.

## Actor input object example

```json
{
  "items": [
    "https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-dubai-hills-estate-elvira-at-dubai-hills-estate-elvira-2-132512758.html"
  ],
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

No description

# 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 = {
    "items": [
        "https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-dubai-hills-estate-elvira-at-dubai-hills-estate-elvira-2-132512758.html"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/propertyfinder-listing-lookup").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 = { "items": ["https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-dubai-hills-estate-elvira-at-dubai-hills-estate-elvira-2-132512758.html"] }

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/propertyfinder-listing-lookup").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 '{
  "items": [
    "https://www.propertyfinder.ae/en/plp/buy/apartment-for-sale-dubai-dubai-hills-estate-elvira-at-dubai-hills-estate-elvira-2-132512758.html"
  ]
}' |
apify call accountable_eel/propertyfinder-listing-lookup --silent --output-dataset

```

## MCP server setup

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

```

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/ubDD2Ht17Kog14Rd0/builds/2J1GE0PHJujwBnfU0/openapi.json