Real Estate Scraper API

Every API in this category

Send a public page URL to the category endpoint. The target website determines which fields can be extracted; there is no social-media-style scraper name to supply.

Fields depend on the target and request context. A dedicated guide is not a guarantee that every field is available on every page.

The 19 dedicated pages

Choose a guide for your target. This list is generated from the same category data as the catalogue and structured page list.

How a Real Estate API call works

Real Estate requests are synchronous: submit a public listing URL and read the structured result from the same response.

STEP 1Send the listing URL and only the rendering or proxy options required by that portal. Authenticate with your username and API key.

curl --request POST 'https://api.scraping-bot.io/scrape/real-estate' \
  --user "YOUR_USERNAME:YOUR_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
  "url": "https://www.zillow.com/homedetails/YOUR_LISTING",
  "options": {
    "useChrome": false,
    "premiumProxy": false
  }
}'

Replace the example URL with an actual public property listing.

STEP 2Read the property data and inspect the returned target status before saving fields or comparing listings.

Request parameters

See the documentation for the complete request and response examples.

Credits, refunds and limits

Current plans start at 1 credit for a standard Real Estate call. Legacy plans have a 16-credit base rate before applicable options. The API does not guarantee that every property field is present on every portal.

Request limits depend on your plan. Respect rate-limit responses, avoid uncontrolled retries and check target-specific proxy requirements. Additional targeting or special-domain rules can affect costs; confirm your configuration in the pricing plans and documentation.

Real Estate API or Raw HTML scraper?

Questions about the Real Estate API

Which property websites can I use?

The dedicated pages below describe the targets in the catalogue. Start with the guide for your portal and test a representative public listing.

Does one request crawl all listings in a city?

No. The endpoint takes a listing URL. Building a city-wide dataset requires collecting listing URLs and submitting separate requests.

Are surface units and energy ratings identical across portals?

No. Inspect surfaceAreaUnit and the returned fields. Energy information depends on the country, the portal and what the listing publishes.

Which data should I collect?

Use public pages and collect only the data needed for your use case. Public availability does not remove privacy, copyright or contractual obligations; assess those before using or republishing the results.

Other categories