Collect Properati Listings Without Running Your Own Browser Fleet
Properati property pages are built with JavaScript and protected by bot detection, so a plain HTTP fetch often returns a shell rather than the listing.
A managed scraping API moves the browser, proxy rotation, and rendering work off your side: your code sends a Properati URL and receives rendered HTML or parsed JSON back. This page explains the controls that matter for Properati, shows how the pieces fit into one listing record, and helps you choose a plan from the published credit and concurrency figures.
What the API handles for you
Three jobs sit between a Properati URL and a usable dataset: getting past bot checks, executing the page's JavaScript, and turning the rendered result into fields your pipeline can query. The API covers all three. A stealth proxy layer and a headless browser do the fetching and rendering, so your client stays a thin HTTP call. You can then ask for rendered HTML, a screenshot, Markdown, or structured extraction depending on what the next step in your workflow needs.
The practical benefit is that you do not maintain a pool of browsers or source proxy providers yourself. You also keep the option to add JavaScript scenarios that click, scroll, or type before capture when a listing page reveals details only after interaction.
Three collection patterns for Properati data
Most Properati work falls into one of three shapes, and each shapes what you extract.
- Listing extraction. You want individual property records for lead generation, competitor comparison, or positioning work. The fields that matter are the ones on the listing itself: price or rent, size, rooms, location, agent, and photos.
- Market trend analysis. You collect listings repeatedly and compare them over time to see how asking prices and rental rates move. Here consistency of field names and capture timing matters more than any single record.
- Neighborhood research. You group listings by area and combine them with demographic signals to judge where investment interest is rising. This pattern depends on reliable location fields and enough volume per neighborhood to compare.
All three start from the same request mechanics; they differ in how often you run collection and how you store the output.
Request controls mapped to Properati page problems
Use this map to pick the parameter that matches the symptom you see.
- Page returns a skeleton with no listing content. Turn on JavaScript rendering so the page executes in a real browser before capture.
- Requests are challenged or blocked. Enable the stealth proxy path so traffic is routed through residential IPs and browser behaviour looks like a normal visitor.
- Content differs by country. Set the country code so the request exits through a residential IP in that country.
- You need fields, not HTML. Supply extraction rules that map CSS selectors to field names, or describe the fields in natural language for AI extraction.
- You need a visual record. Request a full-page screenshot alongside or instead of HTML.
- You need text for a language model. Ask for the page as clean Markdown.
The controls compose: a single request can render JavaScript, use a stealth proxy, target a country, and apply extraction rules.
A worked listing record
Suppose you send one Properati sale listing through the API with JavaScript rendering on and extraction rules that name the fields you want. The response is parsed JSON rather than a page you have to scrape again. Based on the fields the API returns for Properati listings, a single record can carry:
- asking price or monthly rent
- square meters
- bedrooms and bathrooms
- neighborhood
- agent name
- days on market
- the image gallery
That record is the unit your downstream work consumes: a lead list, a price index, or a neighborhood roll-up. If you prefer natural language over selectors, describe the same fields in an AI extraction spec and the response still arrives as parsed JSON. The example is illustrative of the field set, not a claim about any specific live listing.
Blocked page or unparsed page? A quick distinction
Two failures look similar in a log but need different fixes.
- Blocked. The response is a challenge, a CAPTCHA, or an empty shell with no listing markup. Fix by enabling stealth proxying and JavaScript rendering, and by spacing requests if the target throttles aggressive patterns.
- Rendered but unparsed. The HTML contains the listing, but your selectors return nothing or the wrong values. Fix the extraction rules or the AI extraction spec rather than the proxy settings.
A useful check is to request the page as HTML first and inspect whether listing content is present. If it is, the problem is downstream of fetching. If it is not, revisit rendering and proxy controls before touching selectors.
Choosing a plan from the published figures
Plans differ on four levers that matter for Properati collection: monthly API credits, concurrent requests, access to premium proxies and geotargeting, and support level. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules are included from the entry plan upward. Priority email support, a dedicated account manager, and team management appear only on the Business tier and above.
Credit consumption is the figure to watch. Requests start at one credit each; a successful request with JavaScript rendering costs five credits; premium proxies cost ten or twenty-five credits depending on whether rendering is also on. Because Properati pages generally need rendering and often need premium proxies, budget the higher per-request figure when sizing a plan. Credits are valid for one month and do not roll over, so match the plan to your monthly volume rather than accumulating a buffer.
The pricing table below preserves the published plan figures exactly; treat them as a dated reference and confirm current pricing before purchase.
Getting from docs to a first request
The path is short: create an account to receive an API key and starter credits, install an SDK or use cURL, then send a GET request with a Properati URL on properati.com. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and raw cURL works as well. A dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in any of those languages, which is useful if you want to confirm a configuration before writing application code.
For a first run, start with rendering on and a single listing URL. Inspect the returned HTML to confirm listing content is present, then add extraction rules. Only after that should you widen to search or category pages and add concurrency.
Compliance and data handling
The service is presented as GDPR and CCPA compliant, and it does not collect or store personal data from scraped sites unless the user explicitly requests it. That places the responsibility for what you request and how you retain it on your side. For property data, agent names and contact details are personal data in many jurisdictions, so decide deliberately whether you need them and how long you keep them. Review the acceptable use policy and the target site's terms before running collection at scale.
| Plan | Price per month | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included |
Figures are the published plan values as captured on 2026-11-15, exclusive of VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules are included on every plan listed. Credits are valid for one month and do not roll over. Confirm current pricing and terms before purchase.
Frequently asked questions
Can I scrape Properati without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby, or cURL. You still need somewhere to run that snippet, or you can use an automation platform such as n8n to call the API without writing scraper code.
How do I handle JavaScript when scraping Properati?
Set render_js to true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML. This is the step that turns a listing shell into markup containing prices, sizes, and agent details.
Can I scrape Properati from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This matters when Properati serves different content or listings depending on where the visitor appears to be located.
What's the rate limit for scraping Properati?
The API enforces concurrency limits per plan rather than per-target rate limits. If Properati throttles aggressive request patterns, space out requests or use multiple sessions. Your plan's concurrent request figure is the ceiling on simultaneous calls.
How do I get structured JSON from Properati?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language description of the fields. The response comes back as parsed JSON, ready to load into a database or analysis tool.
Which programming languages can I use to scrape Properati?
Any language that can send an HTTP request. Published SDKs cover Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too. Pick whichever your stack already uses.
How many credits does one Properati request consume?
Requests start at one credit each. A successful request with JavaScript rendering costs five credits, and premium proxies cost ten or twenty-five credits depending on whether rendering is also enabled. Because Properati pages usually need rendering and often need premium proxies, plan on the higher figure when estimating monthly volume.