Gumtree Scraper — UK Classifieds, Prices, Sellers

Scrape Gumtree — the UK's #1 classifieds platform — by keyword, category, and location. Returns titles, prices, conditions, seller types, locations, images, descriptions, and listing URLs.

Features

• Search by keyword — any search term across all categories or a specific category slug
• Location filter — restrict to a UK city or region (e.g. london, manchester, glasgow)
• Price range — optional min/max GBP price filters
• Access resilient — uses the browse path (/for-sale/...) which avoids the access challenge that hits the /search?... path; RESIDENTIAL GB proxy recommended for production
• Rich data — dual-source extraction (JSON-LD + gumtreeDataLayer) gives 20+ fields per listing
• Pay per result — you are charged only for listings actually returned

Output Fields

Field	Type	Description
listing_id	string	Gumtree numeric listing ID
title	string	Listing title
description	string	Full listing description
url	string	Listing page URL
price	float	Price in GBP
price_currency	string	Always GBP
price_pennies	int	Price in pence
condition	string	New, Used, Refurbished
availability	string	InStock, OutOfStock
location	string	City/area string (e.g. "Hackney, London")
posted_age	string	How long ago posted (e.g. "2 days")
seller_type	string	trade or private
seller_name	string	Seller name (null on search results)
images	array	Image URLs
image_count	int	Number of images
thumbnail	string	First image URL
is_trade	bool	Trade seller flag
is_delivery	bool	Delivery offered
is_gbg_verified	bool	Gumtree Verified badge
promotions	array	e.g. ["FEATURED"]
has_video	bool	Video included in listing
category	string	Category slug (e.g. "iphone")
category_id	int	Gumtree numeric category ID
search_query	string	The query used (provenance)
search_location	string	Location filter used
page_number	int	Page number the listing came from
parse_confidence	float	0–1 quality score; < 0.5 = drift warning
warnings	array	Machine-readable parse warnings
scraped_at	string	ISO-8601 UTC timestamp

Input

Parameter	Type	Default	Description
query	string	required	Search keyword(s)
location	string	UK-wide	Location slug (e.g. london)
category	string	all	Category slug (e.g. iphones, cars-vans-motorbikes)
priceMin	integer	—	Minimum price in GBP
priceMax	integer	—	Maximum price in GBP
maxItems	integer	100	Maximum listings to return (0 = all)
proxyConfiguration	object	RESIDENTIAL GB	Apify proxy config

Access Notes

Gumtree's /search?... query path triggers a JS challenge (HTTP 247 with window.rbzns). The browse path (/for-sale/...) is not challenged. This actor uses the browse path exclusively. Apify RESIDENTIAL GB proxy is recommended for production cloud runs.

Pricing

Pay-per-event: $1.50 per 1,000 listings (charged per listing-item event, only for records actually returned).

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.