Reed.co.uk Jobs Scraper

Scrape job postings from Reed.co.uk, the UK's largest job site, with salary figures normalized to a common annual amount so they're actually comparable. Search by keyword, location, salary range, contract type and more, get clean structured JSON back, and only pay for the results you actually receive.

Try it now: fill in a search below, hit Start, and download your results as JSON, CSV or Excel once the run finishes.

Why use Reed.co.uk Jobs Scraper?

Reed's own search results mix hourly, daily and annual salaries, hide "competitive" salaries behind vague text, and give you HTML pages, not data. This Actor does the normalization work for you:

• Salaries converted to a comparable annual figure - £15.50 per hour and £300 per day are both converted to their annual-equivalent, using the same assumptions Reed's own site uses (37.5-hour week, 5-day week), so you can sort and filter postings by pay without doing the maths yourself.
• Remote/hybrid/on-site clearly separated into its own workModel field, instead of buried in free text.
• New-job monitoring: run the same search on a schedule and get only the postings you haven't seen before, so you can wire it into Slack, email or a spreadsheet without re-processing the same jobs every time.
• Personal data removed automatically: email addresses and UK phone numbers found inside job descriptions are redacted before the data ever reaches you.
• Pay only for delivered results (pay-per-event pricing) - a failed request, a duplicate, or a job already seen by monitoring mode costs you nothing.
• Runs on the Apify platform, so you get scheduling, an API, webhooks, dataset exports (JSON/CSV/Excel/HTML) and integrations (Zapier, Make, Google Sheets, n8n) for free.

Use cases

1. UK salary benchmarking - pull every posting for a role and location, and compare annualized salaries across hundreds of postings in a spreadsheet instead of reading each listing by hand.
2. Job market / competitor analysis - track which companies are hiring for which roles, in which locations and at what contract type (permanent/contract/temporary), over time.
3. New-job alerts - schedule a run every hour or day with monitoring mode on, and pipe new postings into Slack, email or a database via Zapier or n8n, without re-fetching jobs you've already processed.

How to use Reed.co.uk Jobs Scraper

1. Click Try for free (or Start if you're already looking at the Actor).
2. Fill in Keywords and, optionally, Location and any filters (salary range, contract type, working hours, work model, posted within). Or paste one or more Reed search/job URLs into Start URLs to use those instead.
3. Set Max results and whether you want full job details (Include job details) or just the faster/cheaper search-results data.
4. Click Start and wait for the run to finish.
5. Open the Dataset tab (or call the API) to download your results as JSON, CSV, Excel or HTML.

For a recurring search, add a Schedule and turn on Only new jobs (see Monitoring mode below).

Input

All fields are optional and have sensible defaults - the only thing you'll usually change is Keywords and Location. See the Input tab for the full form with descriptions, or provide JSON directly:

{
    "keywords": "python developer",
    "location": "London",
    "distanceMiles": 15,
    "salaryFrom": 40000,
    "contractTypes": ["permanent"],
    "includeDetails": true,
    "maxItems": 200,
    "onlyNewJobs": false,
    "monitorKey": "default",
    "maxConcurrency": 3
}

Notable fields:

Field	Description
keywords / location	Free-text search, same as typing into reed.co.uk's search box. Leave both empty to get the newest postings site-wide.
startUrls	One or more reed.co.uk search or job URLs. Overrides keywords/location/filters when set.
distanceMiles, salaryFrom/salaryTo, contractTypes, workingHours, workModel, postedWithin	Match the filters on reed.co.uk's own search page.
includeDetails	true (default): visit each job's page for the full description, exact location and confirmed contract type. false: use only the search-results data (faster, cheaper, less complete).
maxItems	Target number of results (default 20, max 10,000). The Actor never returns more than this.
onlyNewJobs / monitorKey	See Monitoring mode.
proxyConfiguration	Apify Proxy configuration; datacenter proxies are used by default.

Output

Each dataset item is one job posting, already normalized and PII-redacted. Example (from a real, live search - the full descriptionText/descriptionHtml are longer and truncated here for readability):

[
    {
        "jobId": "57258187",
        "url": "https://www.reed.co.uk/jobs/python-developer/57258187",
        "title": "Python Developer",
        "companyName": "Tenth Revolution Group",
        "companyProfileUrl": "https://www.reed.co.uk/company-profile/Tenth-Revolution-Group-72466",
        "locationText": "London",
        "city": "London",
        "region": "South East England",
        "postcode": null,
        "country": "GB",
        "isRemote": false,
        "workModel": "hybrid",
        "employmentType": ["FULL_TIME"],
        "contractType": "permanent",
        "salaryText": "£35,000 - £45,000 per annum",
        "salaryDisclosed": true,
        "salaryMin": 35000,
        "salaryMax": 45000,
        "salaryCurrency": "GBP",
        "salaryPeriod": "year",
        "salaryAnnualMin": 35000,
        "salaryAnnualMax": 45000,
        "datePosted": "2026-08-20T09:24:11.997Z",
        "validThrough": "2026-10-01T23:55:00.000Z",
        "descriptionSnippet": "Python Developer - London (Hybrid) - Up to 45,000 We're partnering with a growing technology-led business looking for a Python Developer...",
        "descriptionText": "Python Developer - London (Hybrid) - Up to £45,000\nWe're partnering with a growing technology-led business...",
        "descriptionHtml": "<p><strong>Python Developer - London (Hybrid) - Up to £45,000</strong></p>...",
        "isNew": true,
        "source": "reed.co.uk",
        "scrapedAt": "2026-09-26T05:19:45.139Z"
    },
    {
        "jobId": "57355173",
        "title": "Python Developer",
        "companyName": "Pontoon",
        "workModel": "remote",
        "isRemote": true,
        "contractType": "contract",
        "salaryText": "Salary negotiable",
        "salaryDisclosed": false,
        "salaryMin": null,
        "salaryAnnualMin": null
    },
    {
        "jobId": "57363584",
        "title": "AWS/Python Software Engineer",
        "companyName": "E.ON",
        "workModel": "hybrid",
        "contractType": "permanent",
        "salaryText": "Competitive salary",
        "salaryDisclosed": false,
        "salaryMin": null,
        "salaryAnnualMin": null
    }
]

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel from the Dataset tab or the API.

Output fields

Field	Type	Description
jobId, url	string	Reed's job ID and canonical URL (tracking parameters removed).
title, companyName, companyProfileUrl	string | null	Job title, employer name, and the employer's reed.co.uk profile page (not their own website; null if they don't have one).
locationText, city, region, postcode, country	string | null	Location as shown on the page, plus parsed components where Reed provides them.
isRemote, workModel	boolean | null, onsite/hybrid/remote/null	Derived from Reed's own work-model tag; null when Reed doesn't state one.
employmentType	string[]	e.g. ["FULL_TIME"], ["FULL_TIME","CONTRACTOR"].
contractType	permanent/contract/temporary/null
salaryText	string | null	The salary exactly as displayed on the page.
salaryDisclosed	boolean	false when Reed hides the number behind "Competitive salary" / "Salary negotiable" (the underlying figures, if any, are not reliable, so they're not exposed either).
salaryMin, salaryMax, salaryCurrency, salaryPeriod	number | null	The figures as posted (salaryPeriod: hour/day/week/month/year).
salaryAnnualMin, salaryAnnualMax	number | null	Annualized: hour × 1950 (37.5h × 52wk), day × 260 (5d × 52wk), week × 52, month × 12 - the same assumptions reed.co.uk's own site uses.
datePosted, validThrough	ISO 8601 string | null
descriptionSnippet, descriptionText, descriptionHtml	string | null	Short summary, plain text, and cleaned HTML - emails and UK phone numbers redacted in all three.
isNew	boolean	true if this job hasn't been seen before for this run's monitorKey (see below).
source, scrapedAt	string	Always "reed.co.uk", and the ISO timestamp the item was scraped.

includeDetails: false fills only the fields available from the search-results page; the rest are null.

Pricing

This Actor uses pay-per-event pricing.

Event	Price	When you're charged
Actor start	$0.003 per run	Once per run, regardless of how many results come back
detail-result	$0.50 per 1,000 results	Once per result with includeDetails: true (full job data)
listing-result	$0.10 per 1,000 results	Once per result with includeDetails: false (search-results data only)

A failed request, an in-run duplicate, or a job skipped by monitoring mode is never charged as a result - only the flat start fee applies regardless of how many (if any) results come back, which covers the fixed cost of a run, e.g. a scheduled monitoring run that finds nothing new.

Based on real Apify Cloud measurements, running this Actor costs roughly $0.13 per 1,000 results with includeDetails: true, $0.01 per 1,000 with includeDetails: false, and about $0.001 for a monitoring run that finds zero new postings - so pricing is set with a comfortable margin even if blocking or retries are worse than measured on a given day.

Monitoring mode

Set Only new jobs (onlyNewJobs: true) to get only postings you haven't seen before, and avoid paying for ones you have. Give each distinct search a Monitoring key (monitorKey) so their "seen" lists don't mix.

• First run for a given monitorKey: every job is new, nothing is skipped.
• Later runs: an already-seen job is skipped before its detail page is even fetched - no request, no dataset item, no charge. A job whose fetch failed is not recorded as seen, so it's retried on the next run instead of being silently lost.
• isNew is reported on every result regardless of this setting, so you can see what's new even without monitoring mode on.
• Recommended for scheduled monitoring: set Posted within to today or lastThreeDays alongside onlyNewJobs. A narrower search matches far fewer listing pages each run, so it's both faster and cheaper - useful because a monitoring run still has to fetch listing pages to discover what's new, even once most of a broad search's results are already marked as seen.
• To automate it, add a Schedule (e.g. every hour or every morning) with onlyNewJobs: true, and connect the run's webhook or dataset to Zapier, Make or n8n to post new jobs to Slack, email, or a spreadsheet.

Limitations

• Sorting isn't supported. reed.co.uk's robots.txt disallows crawling search URLs with a sortBy parameter, so this Actor never sends one; results come back in reed.co.uk's default order.
• maxItems is a target for successful results, not a hard request cap. The Actor queues a small buffer of extra candidate jobs (5% of maxItems, minimum 2) so a handful of failed detail pages (blocked, removed, unparseable) don't leave you short. If more detail pages fail than that buffer covers, you can get fewer than maxItems results - never more.
• Some blocking is expected and retried automatically. Like any scraper, requests through Apify's shared proxies are occasionally blocked (403) or rate-limited; the Actor retries with a fresh proxy session and backoff (up to 3 attempts) before giving up on that one page. In early testing, roughly half of first attempts through a datacenter proxy were blocked, and about 9 in 10 requests ultimately succeeded within 3 attempts - a small fraction of pages can still fail on a given run.
• Salary annualization is an estimate. It assumes a 37.5-hour, 5-day working week (reed.co.uk's own convention) and doesn't account for actual contracted hours, which reed.co.uk doesn't always state.
• Concurrent runs sharing the same monitorKey can overwrite each other's "seen" state, since it's read once at the start of a run and written once at the end. Use a distinct monitorKey per search, and avoid scheduling overlapping runs for the same one.

Legal disclaimer

This Actor only collects data that is already public on reed.co.uk - no login, no paywalled content, and no bypassing of CAPTCHAs or bot-detection. Personal data found in job descriptions (email addresses, phone numbers) is redacted before delivery. You are responsible for using the collected data in compliance with reed.co.uk's Terms of Service and any applicable data-protection law (e.g. UK GDPR) in your jurisdiction. This Actor isn't affiliated with or endorsed by Reed.co.uk.

FAQ

Does this Actor use my Reed account or require login? No. It only reads reed.co.uk's public search and job pages.

Why is a job's salary null even though the listing shows a number? Some postings mark their number as unreliable (e.g. "Competitive salary", "Salary negotiable"); when salaryDisclosed is false, the numeric fields are intentionally left null rather than showing a misleading figure.

Can I get notified only about brand-new postings? Yes - see Monitoring mode above.

Something looks wrong or missing. Please open an issue in this Actor's Issues tab with the search you ran and what you expected - reed.co.uk changes its page structure occasionally, and reports like this are how it gets fixed quickly. Custom scraping solutions are also available on request.

Changelog

• 0.1 - Initial release: keyword/location/filter search, full job-detail scraping, salary normalization and annualization, remote/hybrid detection, PII redaction, new-job monitoring mode, pay-per-event billing.