Skip to content

MLS Scraper API for Public Listing Pages

A hosted scraping API is useful when you want public MLS-syndicated listing pages as data without running your own headless browser fleet.

OUTPUT FORMATSHTMLJSONMarkdown

You send a listing URL; the service renders the JavaScript, rotates proxies, and returns HTML or structured JSON. This guide covers what you can pull, how to shape the request, what each option costs in credits, and where scraping stops being the right tool.

What you can pull from a public MLS listing page

Three workflows come up most often: collecting listings, tracking list prices, and gathering agent contact details and specialties. For a single listing page, the fields the API is set up to return are:

  • Property address
  • List price
  • Beds and baths
  • Square footage
  • Lot size
  • Year built
  • MLS number
  • Days on market
  • Agent info

Those fields are the ones the page describes as parsing in one call across MLS-syndicated sites. If a field you need is not in that list, it can still be extracted from anything that renders on the public page using CSS selectors or AI-driven extraction — but treat that as a per-site configuration task, not a guaranteed default.

Beyond a single listing: four adjacent capabilities

The same API surface covers several tasks that sit next to listing extraction. Each one changes what you get back, so pick by output rather than by habit:

  • Screenshot capture. Renders the page in a real browser and returns a visual capture. Useful when you need to see how a listing actually displays, or to archive a page state alongside the extracted fields.
  • Google SERP extraction. Pulls search-result data for real-estate queries, so you can see which listings and pages surface for a market or property term. The output is search results, not listing records.
  • Markdown output. Returns a listing page as clean Markdown, which is the practical format when you want to feed the page into an LLM for property analysis or market-comps work.
  • n8n automation. Runs the same request inside an n8n workflow so listing monitoring can be scheduled without writing scraper code.

A quick rule: use structured extraction when you need fields in a database, Markdown when a model will read the page, screenshots when a human needs to see it, and SERP data when the question is about visibility rather than the listing itself.

How a request is shaped

The basic flow is: create an account, get an API key, then send a GET request with the target URL. The service handles rendering and bot bypass and returns the page. To get structured output rather than raw HTML, add extraction rules.

  • render_js — render JavaScript before returning the page.
  • stealth_proxy — route through stealth proxies for harder bot protection.
  • country_code — geotarget the request.
  • extract_rules — pull fields with CSS selectors.
  • ai_extract_rules — describe the fields you want in natural language and get structured JSON back.

A request builder in the dashboard lets you test a configuration without writing code. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too.

Field map and a worked example

Suppose you point the API at a public listing page and use ai_extract_rules to ask for the standard set. A returned record would look conceptually like this (values are illustrative placeholders, not a real listing):

  • address: "123 Example St"
  • list_price: 450000
  • beds: 3
  • baths: 2
  • square_footage: 1800
  • lot_size: "0.2 acres"
  • year_built: 1998
  • mls_number: "EX000000"
  • days_on_market: 12
  • agent: { name: "...", phone: "...", specialties: "..." }

Use this as a shape to validate against, not as a schema the service guarantees. If a site omits a field, the extractor returns what is present; design your pipeline to tolerate missing keys rather than assuming every listing is complete.

Credit costs per request

Credits are consumed per successful request and the cost depends on which options you enable. The published figures are:

  • Base request: from 1 credit.
  • render_js: 5 credits.
  • Premium proxies: 10 credits without JS rendering, 25 credits with JS rendering.
  • stealth_proxy: 75 credits.

So a stealth-proxy request with JS rendering is the most expensive common combination. Before committing to a plan, estimate your monthly page count multiplied by the per-request credit cost of the options you actually need — not the base rate.

Choosing a plan tier

The plans differ mainly in monthly API credits and concurrent requests; JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots/extraction rules are included from the Hobby tier upward. Priority email support, a dedicated account manager and team management appear from the Business tier upward.

A simple way to choose: divide your monthly credit budget by your per-request credit cost to get the number of pages you can process, then check that the concurrency figure covers your peak parallel workers. If you need more credits or concurrency than the top listed tier, contact sales.

Three different failures, three different fixes

When a run does not return the data you expected, the cause is usually one of these, and they need different responses:

  1. Blocked request. The target site served a challenge or empty page. Try render_js, then premium proxies, then stealth_proxy — each step raises the credit cost.
  2. Selectors matched nothing. The page rendered but your extract_rules pointed at elements that are not there. Re-inspect the rendered HTML, or switch to ai_extract_rules and describe the fields in plain language.
  3. Legal or terms-of-service limit. The page is behind a login, or the site's terms prohibit the collection you are attempting. No API option fixes this; stop and review the site's terms before continuing.

Separating these three early saves both credits and time.

Getting started

Sign up, take the API key, and send a GET request with a public listing URL. The free tier includes 1,000 credits with no card required, which is enough to test rendering and extraction on a handful of pages before you scale. Documentation and code samples are available for every supported language, and a dashboard request builder lets you try configurations without writing code.

Credit cost per successful request by option
OptionCredits
Base requestfrom 1
render_js5
Premium proxy (no JS)10
Premium proxy + JS rendering25
stealth_proxy75

Figures reflect the captured pricing page and may change; check current pricing before committing.

Feature availability by plan tier
FeatureHobby / Freelance / StartupBusiness / Business+ / Enterprise
JavaScript renderingIncludedIncluded
Rotating & Premium ProxiesIncludedIncluded
GeotargetingIncludedIncluded
Screenshots & Extraction RulesIncludedIncluded
Priority Email SupportNot includedIncluded
Dedicated Account ManagerNot includedIncluded
Team ManagementNot includedIncluded

Plan names and inclusions reflect the captured pricing page; verify current plans before purchase.

Frequently asked questions

Do I need an MLS account to use the scraper?

No. You need an API key from the scraping service, not an MLS login. The service works on public-facing pages and does not provide access to member-only or post-login content.

Is scraping MLS data legal?

Public-facing pages can usually be scraped, but you should review the target site's terms of service before deploying and avoid post-login content. Legal position varies by site and jurisdiction; this is not legal advice.

What data can I extract?

Any content that renders on the public page. You have two routes to structured JSON: point extract_rules at elements with CSS selectors, or let ai_extract_rules handle extraction by describing the fields you want in plain language. The standard listing set covers address, list price, beds, baths, square footage, lot size, year built, MLS number, days on market and agent info.

How do I start?

Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies and returns the data. 1,000 free credits are available to test.

Which programming languages can I use?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java. Plain cURL works too.

How much does it cost?

1,000 free credits on signup, no card required. Paid plans start at $19/month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, 75 for stealth_proxy.