Property Finder Gulf — Qatar, Saudi, Egypt, Bahrain
Pricing
from $3.50 / 1,000 results
Property Finder Gulf — Qatar, Saudi, Egypt, Bahrain
Scrape Property Finder in Qatar, Saudi Arabia, Egypt and Bahrain: price in local currency, size in sq ft and m², bedrooms, coordinates, verification status and listed date, plus the agent with email and the brokerage with phone, email and office address.
Pricing
from $3.50 / 1,000 results
Rating
0.0
(0)
Developer
Logiover
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
1
Monthly active users
8 days ago
Last modified
Categories
Security
Limited permissionsShare
Export listings from Property Finder across Qatar, Saudi Arabia, Egypt and Bahrain — price, size, coordinates, verification status and the full agent and brokerage contact record — to JSON, CSV or Excel. Keyless, no login.
What does Property Finder Scraper do?
Property Finder runs the same platform in every market it operates in, and embeds its whole search payload in the page. This Actor reads that directly across four Gulf and North African markets from one dropdown. No browser, no rendering, low cost per row.
The United Arab Emirates is deliberately not in the list: it has its own dedicated Actor. Two Store listings competing for the same market split the traffic instead of adding anything.
What makes this export unusually valuable is the contact record on every listing. Each row carries the listing agent's name, email and spoken languages, and the brokerage's name, email, phone number and registered office address. In markets where thousands of brokerages compete for the same stock, that turns a property export into a brokerage database — which is exactly what proptech vendors, mortgage brokers, developers and portal competitors want.
Three details are handled deliberately rather than copied blindly:
- The results array is mixed. Alongside ordinary properties it carries developer-project blocks, project carousels and recommendation widgets. Those are not properties, so they are filtered out and the row count stays honest.
- Studios are not a number.
bedroomsarrives as a string and studios come through as the word "studio". Both a numeric column and the original label are exported, so you can filter numerically without losing studios. - Sizes are in square feet. The site's own sq ft value is kept and a square-metre column is derived, because everyone outside the Gulf compares in m².
Who is it for?
- Brokerages benchmarking competitor stock and agent activity in Doha, Riyadh, Cairo and Manama.
- Proptech, CRM and mortgage vendors prospecting Gulf brokerages with verified contact details.
- Developers tracking secondary-market pricing against their own launches.
- Investors filtering by price per sq ft, completion status and location.
- Analysts measuring supply, verification rates and time-on-market.
Use cases
- Build a Qatari or Saudi brokerage contact list with phone, email and office address.
- Rank agents by listing count and average asking price.
- Compare price per sq ft across Doha or Riyadh districts using exact coordinates.
- Separate off-plan from completed stock using the completion status.
- Track newly listed properties daily in each market by sorting newest first.
Why use this Actor?
- Agent and brokerage contact data — email, phone and office address on every row.
- Both size units — the site's sq ft plus a derived m² column.
- Exact coordinates, no geocoding step.
- Verification and developer flags, so you can filter to verified stock only.
- Real listed date, not a relative label.
- Keyless and browserless — no login, no headless Chrome.
What data can you extract?
Every row carries the property ID and reference, title and URL, property and transaction type, price with currency and a hidden-price flag, numeric bedrooms plus the original label, bathrooms, size in sq ft and m², furnished state, completion status, location name, full location path, location type, latitude and longitude, agent name, email, languages and super-agent flag, brokerage name, email, phone and address, the listing's contact phone and WhatsApp number, verified, developer, new-construction and premium flags, amenity codes, image count and the listed date.
How to use it
- Choose the country market — Qatar, Saudi Arabia, Egypt or Bahrain.
- Choose the transaction — residential sale or rent, or commercial.
- Pick a property type, or Any.
- Optionally paste a location ID from a Property Finder search URL's
lparameter. - Set a price band and minimum bedrooms if you need them.
- Set Maximum results and run, then export JSON, CSV or Excel.
Input example
{"market": "qa","transaction": "buy","propertyTypeId": "1","minPrice": 1000000,"maxPrice": 3000000,"minBedrooms": 2,"sortBy": "nd","maxResults": 1000}
Additional input fields
These optional fields are also available in the input form and API:
| Field | Type | Default | Description |
|---|---|---|---|
locationId | string | "" | Optional Property Finder location code from the search URL's l parameter. Leave empty to search the whole country. |
proxyConfiguration | proxy | {"useApifyProxy": true} | Property Finder embeds its search payload in the page; the default datacenter proxy is enough. |
Notes and limits
- Prices are asking prices in each market's own currency — Qatari riyal, Saudi riyal, Egyptian pound or Bahraini dinar — and the currency is exported per row. For rentals the figure is the annual rent, which is how these markets quote it.
- Contact details are the business contact information the brokerage publishes on its own adverts — not personal data taken from anywhere else. You remain responsible for how you use it under each market's own law and, where applicable, GDPR when sending marketing.
- Amenities are exported as Property Finder's own two-letter codes; the codes are stable, the display names are not.
- Brokerage phone and office address are absent on a small share of listings because the brokerage has not filled them in.
- This Actor exports the search payload, not full property pages — open the property URL for the complete description and gallery.
FAQ
Do I need a Property Finder account? No. Search results are public and the Actor needs nothing from you.
Why is the UAE missing? It has its own Actor. Listing the same market twice in the Store would split search traffic between two pages rather than growing it.
Where do I get the location ID?
Search on the country site for your area and copy the l parameter from the URL. Leaving it empty searches the whole country.
Does it cover rentals and commercial? Yes — all four combinations of residential/commercial and sale/rent.
Why are there two size columns? The site quotes square feet; the square-metre column is derived so the data is comparable internationally.
How am I charged? Pay per result — you pay for the properties delivered.
*Maintained: last verified 2026-11-01 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).
Output example
One row from a real run of this Actor:
{"propertyId": "62523918","reference": "AS-004121-5600","title": "READY 2 BEDROOMS | THE PEARL INVESTMENT","propertyUrl": "https://www.propertyfinder.qa/en/plp/buy/apartment-for-sale-doha-the-pearl-island-qanat-qu…","propertyType": "Apartment","transactionType": "sale","priceAmount": 1850000,"currency": "QAR","isPriceHidden": false,"bedrooms": 2,"bedroomsLabel": "2","bathrooms": 3,"sizeSqft": 1249,"sizeSqm": 116,"furnished": "YES","completionStatus": "completed","locationName": "Carnaval","locationFullName": "Carnaval, Qanat Quartier, The Pearl Island, Doha","locationType": "TOWER","latitude": 25.377395629882812,"longitude": 51.544288635253906,"agentName": "Louay Soufi","agentEmail": null,"agentLanguages": "English, Arabic, French"}
Output fields
| Field | Type | Filled in sample |
|---|---|---|
propertyId | string | 100% |
reference | string | 100% |
title | string | 100% |
propertyUrl | string | 100% |
propertyType | string | 100% |
transactionType | string | 100% |
priceAmount | number | 100% |
currency | string | 100% |
isPriceHidden | boolean | 100% |
bedrooms | number | 93% |
bedroomsLabel | string | 100% |
bathrooms | number | 100% |
sizeSqft | number | 100% |
sizeSqm | number | 100% |
furnished | string | 100% |
completionStatus | string | 100% |
locationName | string | 100% |
locationFullName | string | 100% |
locationType | string | 100% |
latitude | number | 100% |
longitude | number | 100% |
agentName | string | 100% |
agentEmail | string | 0% |
agentLanguages | string | 100% |
isSuperAgent | boolean | 100% |
brokerName | string | 100% |
brokerEmail | string | 100% |
brokerPhone | string | 100% |
brokerAddress | string | 100% |
contactPhone | string | 100% |
contactWhatsapp | string | 100% |
isVerified | boolean | 100% |
isFromDeveloper | boolean | 100% |
isNewConstruction | boolean | 100% |
isPremium | boolean | 100% |
amenityCodes | string | 100% |
imageCount | number | 100% |
listedDate | string | 100% |
country | string | 100% |
source | string | 100% |
Related scrapers
Other Actors from the same collection:
Scheduling and integrations
Run this Actor on a schedule — hourly, daily or weekly — and have every run append to the same dataset, which is how you turn a one-off export into a time series. Results can be pushed straight into Google Sheets, Slack, Zapier, Make, Airtable or any Webhook.
How much Property Gulf data can you extract in one run?
A single run returned 975 listings in 195 seconds on the example input. That is roughly 300 listings a minute. Widen the search — more queries, more pages, a broader location — and the same run goes deeper.
There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Property Gulf itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.
Property Gulf scraping — frequently asked questions
Do I need a Property Gulf API key, account or login?
No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.
How do I export Property Gulf data to CSV, Excel, JSON or Google Sheets?
Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.
Can I schedule this Property Gulf scraper to run daily or hourly?
Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the listings you care about really do change that fast.
How many listings can I get, and what does it cost?
See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.
Is scraping Property Gulf legal?
This Actor collects only information that Property Gulf publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.
What happens if Property Gulf blocks the run or changes its layout?
A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".
Can I use this with an AI agent, LangChain or an MCP client?
Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.
Legal and compliance
This Actor collects publicly available information from Property Gulf only. It does not log in, does not circumvent access controls, and collects no private data. You are responsible for using the output lawfully, including under GDPR and comparable regimes where the rows contain personal data, and for respecting Property Gulf's terms where they apply to you.
This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Property; Property and all other trademarks mentioned here are the property of their respective owners.
📝 Changelog
2026-11-01
- Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
- README refreshed: independence disclaimer added; documented 2 additional input fields.
2026-10-15
- Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
- A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
- A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
- Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
- Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.
2026-09-23
- Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
- Output verified on a live run: 41 columns returned, 97.4% of cells populated.
- Run reliability reviewed: 96.6% of public runs succeeded in the last 30 days.
- Input schema, output schema and pricing configuration reviewed.
- Noted that 1 column(s) came back empty in this sample (
agentEmail); these are under review.
2026-09-01
- Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
- Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
- No change to input, output fields or scraping logic.
2026-08-11
- Maintenance release: refreshed the build and dependencies.
- Re-verified live execution, non-empty structured output and dataset field/type integrity.
- Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.