Dubai Off-Plan Projects
Off-plan and new-launch residential projects in Dubai and the UAE, read from the official sites of Emaar, DAMAC, Sobha, Nakheel, Meraas, Binghatti, Ellington, Danube, Azizi, Omniyat, Select Group and Aldar: launch and handover dates, status, unit types with sizes and starting prices, payment plans, brochures and location.
0 rows in the dataset
Download the dataset
Get every row this scraper has collected as one CSV or JSONL file. If the data is older than maxAgeHours, the scraper is re-run with its configured settings first. The key needs the datasets:export scope.
DOWNLOAD_ID=$(curl -s -X POST "https://api.pandorlabs.com/v1/datasets/dubai-offplan-projects/downloads" \ -H "Authorization: Bearer $PANDORLABS_KEY" \ -H "Content-Type: application/json" \ -d '{"maxAgeHours":24,"format":"csv"}' | jq -r '.id')while true; do STATUS=$(curl -s "https://api.pandorlabs.com/v1/downloads/$DOWNLOAD_ID" \ -H "Authorization: Bearer $PANDORLABS_KEY" | jq -r '.status') [ "$STATUS" != "refreshing" ] && break sleep 5donecurl -s "https://api.pandorlabs.com/v1/downloads/$DOWNLOAD_ID/file" \ -H "Authorization: Bearer $PANDORLABS_KEY" \ -o dataset.csvThe rate is 1 credit per 100 rows cached and 2 credits live, charged on the rows in the dataset when the download becomes ready. A failed refresh is not charged. The file stays downloadable for 24 hours. See pricing.
Start a run
To choose the targets yourself, send the parameters below as input. The call returns 202 with the run; the key needs the scrapers:run scope and the account a positive credit balance.
curl -X POST "https://api.pandorlabs.com/v1/scrapers/dubai-offplan-projects/runs" \ -H "Authorization: Bearer $PANDORLABS_KEY" \ -H "Content-Type: application/json" \ -d '{ "input": { "developers": [ "damac", "emaar", "azizi", "sobha", "aldar", "ellington", "danube", "nakheel", "meraas", "binghatti", "omniyat", "select-group" ], "maxProjectsPerDeveloper": 1000, "fetchDetails": true, "requestDelayMs": 400 } }'A run is billed at the live rate once it finishes: 2 credits per 100 rows it collected. A run that collects nothing costs nothing.
Parameters
Every parameter is optional. Anything you leave out uses the default shown here; an unknown name or an invalid value is rejected with a 400 that lists each problem.
Targeting
developersenum[]
Developers
Each developer is read from its own official website.
- Default
["damac","emaar","azizi","sobha","aldar","ellington","danube","nakheel","meraas","binghatti","omniyat","select-group"]- Allowed values
damacemaarazizisobhaaldarellingtondanubenakheelmeraasbinghattiomniyatselect-group
maxProjectsPerDevelopernumber
Max projects per developer
- Default
1000- Range
- 1 to 1000
Advanced
fetchDetailsboolean
Open each project page
Project pages carry unit types, prices, payment plans and brochures. Off reads listing pages only.
- Default
true
requestDelayMsnumber
Delay between requests (ms)
- Default
400- Range
- 0 to 30000
Input as JSON Schema
The same schema the API validates against. Use it as a tool input schema or to generate a typed client.
{ "type": "object", "additionalProperties": false, "properties": { "developers": { "type": "array", "items": { "type": "string", "enum": [ "damac", "emaar", "azizi", "sobha", "aldar", "ellington", "danube", "nakheel", "meraas", "binghatti", "omniyat", "select-group" ] }, "uniqueItems": true, "title": "Developers", "description": "Each developer is read from its own official website.", "default": [ "damac", "emaar", "azizi", "sobha", "aldar", "ellington", "danube", "nakheel", "meraas", "binghatti", "omniyat", "select-group" ] }, "maxProjectsPerDeveloper": { "type": "number", "minimum": 1, "maximum": 1000, "title": "Max projects per developer", "default": 1000 }, "fetchDetails": { "type": "boolean", "title": "Open each project page", "description": "Project pages carry unit types, prices, payment plans and brochures. Off reads listing pages only.", "default": true }, "requestDelayMs": { "type": "number", "minimum": 0, "maximum": 30000, "title": "Delay between requests (ms)", "default": 400 } }}Run, poll, read rows
The run is asynchronous. Poll it until it reaches a terminal status and its billing is paid, then page through its rows. Until then the rows endpoint answers 409 (still queued or running) or 402 (payment required).
RUN_ID=$(curl -s -X POST "https://api.pandorlabs.com/v1/scrapers/dubai-offplan-projects/runs" \ -H "Authorization: Bearer $PANDORLABS_KEY" \ -H "Content-Type: application/json" \ -d '{ "input": { "developers": [ "damac", "emaar", "azizi", "sobha", "aldar", "ellington", "danube", "nakheel", "meraas", "binghatti", "omniyat", "select-group" ], "maxProjectsPerDeveloper": 1000, "fetchDetails": true, "requestDelayMs": 400 } }' | jq -r '.id')while true; do RUN=$(curl -s "https://api.pandorlabs.com/v1/runs/$RUN_ID" \ -H "Authorization: Bearer $PANDORLABS_KEY") STATUS=$(echo "$RUN" | jq -r '.status') BILLING=$(echo "$RUN" | jq -r '.billing.status') case "$STATUS" in queued|running) ;; *) [ "$BILLING" != "pending" ] && break ;; esac sleep 5doneecho "$RUN" | jq '{status, rowCount, billing}'curl -s "https://api.pandorlabs.com/v1/runs/$RUN_ID/rows?page=1&limit=100" \ -H "Authorization: Bearer $PANDORLABS_KEY"See the API reference for pagination, cancelling and listing runs.
Output fields
Rows have no fixed schema; these are the fields observed in the rows collected so far. Coverage is the share of rows where the field is present.
No rows collected yet, so no fields have been observed. Run the scraper once and they will appear here.
