OnTheMarket Properties Scraper

Scrape property listings from OnTheMarket.com — the UK's leading property portal. Extract properties for sale or to rent by location, with bedroom, bathroom, and price filters.

What you get (20+ fields per property)

Field	Description
id	OTM property ID
title	Full property title (e.g. "2 bedroom flat for sale")
operation	sale or rent
property_type	Flat, House, Studio, etc.
address	Full address string
price	Numeric price in GBP
price_text	Original price string (e.g. "£300,000")
price_qualifier	e.g. "Offers in excess of", "Guide price"
bedrooms	Number of bedrooms
bathrooms	Number of bathrooms
location_lat / location_lon	GPS coordinates
agent_name	Estate agency name
agent_telephone	Agent phone number
url	Direct link to the property listing
images	Array of image objects (default + webp URLs)
thumbnail	First image URL
days_listed	Listing age label (e.g. "Added today", "Reduced > 14 days")
recently_added	Boolean
reduced	Boolean — price was reduced
exclusive	Boolean — OTM exclusive listing
features	Array of property feature strings

Input

Parameter	Type	Description
operation	string	sale or rent (default: sale)
location	string	Location slug from OTM URL (e.g. london, manchester, bristol)
minBeds	integer	Minimum bedrooms
maxBeds	integer	Maximum bedrooms
priceMin	integer	Minimum price (GBP)
priceMax	integer	Maximum price (GBP)
maxItems	integer	Max properties to return (default: 100; 0 = all)
proxyConfiguration	object	Proxy settings (RESIDENTIAL GB recommended)

Finding the location slug

Visit OnTheMarket.com, search for a location, and copy the slug from the URL:

• https://www.onthemarket.com/for-sale/property/london/ → slug is london
• https://www.onthemarket.com/for-sale/property/west-london/ → slug is west-london
• https://www.onthemarket.com/to-rent/property/edinburgh/ → slug is edinburgh

Pricing

Pay per result — you are charged only for properties actually returned:

• property-item: $0.00189 per property ($1.89 per 1,000)

Usage examples

50 cheapest 2-bed flats for rent in London under £2,500/month:

{
  "operation": "rent",
  "location": "london",
  "minBeds": 2,
  "maxBeds": 2,
  "priceMax": 2500,
  "maxItems": 50
}

All 3+ bed houses for sale in Manchester between £200k–£500k:

{
  "operation": "sale",
  "location": "manchester",
  "minBeds": 3,
  "priceMin": 200000,
  "priceMax": 500000,
  "maxItems": 200
}

Technical notes

• Data source: __NEXT_DATA__ embedded Redux state (no scraping of CSS classes — structural JSON extraction only).
• Proxy: Apify RESIDENTIAL GB proxy prefilled — recommended for reliable access.
• Pagination: up to 34 pages × 30 results = ~1,020 properties per search (OTM platform limit).
• Parse confidence: every record includes parse_confidence (0–1) and warnings so you know immediately if OTM changed their data structure.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Dubai Property Scraper
• Realtor Scraper
• Redfin Scraper
• Rightmove Listings
• Zillow Scraper
• Zoopla Properties Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.