Reed Jobs Scraper: reed.co.uk UK Jobs & Salaries

Scrape reed.co.uk UK jobs into clean rows — title, apply URL, and salary as numbers where published — at $0.50 per 1,000 jobs, with no key at all or through Reed's official Jobseeker API.

Reed Jobs Scraper extracts UK jobs from reed.co.uk by keyword and location, salary band, contract type or a single employer's feed, and returns every listing in one flat, stable schema with the title and apply URL and, wherever Reed publishes them, the company, location, salary as minimum and maximum numbers and a teaser. With no key it reads the public search pages, and those rows also carry the posted date, the pay period (hourly, daily and annual kept apart), contract type and hours, hybrid/remote arrangement and category wherever Reed publishes them. Supply the free Reed Jobseeker API key and it reads Reed's official API instead, whose search results publish fewer fields; Known limits lists exactly which. A since date skips jobs posted before it, before they are charged.

What you get

• Salary as numbers, not text: salaryMin, salaryMax, salaryCurrency and salaryPeriod — hourly, daily and annual rates are told apart correctly instead of all being labelled 'per year', wherever Reed publishes the period (on the API route that takes includeDescription)
• workType normalized to permanent/contract/temporary plus full-time or part-time, and remote normalized to onsite, hybrid or remote, where Reed publishes them (Known limits lists the API route's gaps)
• Official API when you supply a free key, public search pages when you do not — the same keys either way, with the public-page route filling more of them
• since skips jobs posted before a date you choose, before they are charged, so a daily monitor pays for new postings only; a row whose posted date Reed did not send is kept rather than guessed at
• Optional full job description (HTML and plain text) on either route; without it, the short teaser from the search result ships at no extra cost
• Stable sourceId per job for deduplication across runs, and a schemaVersion so keys never change under you

Sample row:

{
  "sourceId": "reed:57205630",
  "sourceUrl": "https://www.reed.co.uk/jobs/software-engineer/57205630",
  "source": "reed",
  "title": "Software Engineer",
  "company": "Vermillion Analytics",
  "companyId": "100633",
  "location": "London",
  "city": "London",
  "region": "London",
  "country": "GB",
  "remote": "hybrid",
  "workType": "full-time",
  "category": "Engineer",
  "subcategory": "Software Engineer",
  "salaryText": "£35,000 - £45,000 per annum",
  "salaryMin": 35000,
  "salaryMax": 45000,
  "salaryCurrency": "GBP",
  "salaryPeriod": "year",
  "postedAt": "2026-08-06T12:54:07.117Z",
  "expiresAt": "2026-09-17T23:59:59.000Z",
  "applyUrl": "https://www.reed.co.uk/jobs/software-engineer/57205630/apply"
}

Input

Field	Description
query	Keywords, e.g. "software developer". Leave empty to list everything in a location.
location	UK town, city or region, e.g. "London"
distanceMiles	Radius around the location (default 10)
employmentType	any, permanent, contract or temporary
workPattern	any, full-time or part-time
minSalary	Lowest advertised salary to include, in GBP
maxSalary	Highest advertised salary to include, in GBP
employerProfileId	Return one company's whole feed instead of a search (use the companyId from any row)
since	ISO date; jobs listed before it are skipped and never charged
includeDescription	Fetch the full description per job (slower, same price)
apiKey	Optional free Jobseeker API key; also read from REED_API_KEY
maxItems	Hard cap on delivered jobs (default 25)
maxCostUsd	Hard stop on spend, enforced before each request

Pricing

Pay per event. You are charged only for delivered, validated results — never for empty pages, blocked requests, or duplicates. maxCostUsd is a hard stop enforced before each request.

Event	Price	Unit
run-start	$0.001	per run
job	$0.0005	per delivered job — $0.50 per 1,000

• 1,000 jobs ≈ $0.50
• A daily 100-job monitor ≈ $1.53/month
• 25,000 jobs ≈ $12.50

Why this actor

• Salary arrives as numbers with the right period attached wherever Reed publishes one — day rates stay day rates and hourly stays hourly, instead of every figure being reported as an annual salary
• Prefers Reed's own free Jobseeker API when you give it a key, which is the lowest-risk way to read this board; the public-page route is only the fallback
• One price per job whether or not you ask for the full description: includeDescription costs one extra request, not an extra event, so a detail-rich export is still $0.50 per 1,000
• Charged only for validated rows. A blocked or empty run bills nothing at all, not even a run-start fee: empty pages, duplicate promoted listings and blocked requests never bill you
• maxItems and maxCostUsd are enforced before the request that would exceed them, so a broad query cannot run away with your credit
• A blocked or changed page fails the run with a typed error instead of quietly finishing with zero rows

Known limits

• Without an API key the public search pages return 25 jobs per page and stop answering past the last page of a query; split a broad search by location, salary band or since to go deeper
• Without includeDescription a row carries only short text: a teaser of about 150 characters on the public-page route, and the truncated description from Reed's search response on the API route. Full descriptions need includeDescription on either route, at one extra request per job
• Reed omits salary entirely when the advertiser hides it — salaryMin, salaryMax and salaryText are then null rather than zero
• On the public-page route, remote reads unknown, and workType, category, subcategory and region are null, on the listings where Reed leaves that field out
• On the API route, Reed's documented search response carries only the job id, employer, title, a truncated description, location and minimum and maximum salary. So on that route: remote is always unknown and category and subcategory are always null, because the Jobseeker API publishes neither, even in its detail record; region is filled only when Reed's location reads "Town, County"; salaryPeriod, expiresAt and the advertiser's own applyUrl come only from each job's detail record, which the actor fetches when includeDescription is on, so without it they are null and applyUrl is the Reed job page; salaryCurrency is GBP whenever a salary is present; and postedAt is read from a date field the API documentation does not list, so it can be null, and a since filter then keeps the row rather than dropping it
• Reed's API search response carries no contract type or hours, so on the API route workType is filled only from a contract or temporary employmentType filter or from a workPattern filter. A bare permanent filter leaves it null, because permanent says nothing about full-time or part-time; so does filtering on neither. Set includeDescription to fetch each job's own detail record, which does carry both
• applyUrl is the advertiser's own link when Reed publishes one, otherwise the job page that carries the apply button — it is never a guessed URL
• UK listings only — country is always GB
• Employer postings only; no candidate, applicant or recruiter personal data is collected

Use from an AI agent (MCP)

Add the actor as an MCP tool in Claude Desktop / Cursor via the Apify MCP server:

{ "mcpServers": { "reed-jobs": { "url": "https://mcp.apify.com?actors=<your-username>/reed-jobs", "headers": { "Authorization": "Bearer <APIFY_TOKEN>" } } } }

The tool accepts exactly the input fields above and returns the same rows.

Use from n8n / Make

Use the Apify node → "Run actor" with actor <your-username>/reed-jobs and a JSON input such as {"query":"data engineer","location":"Bristol","since":"2026-09-01","maxItems":500} on a daily schedule, then "Get dataset items".

FAQ

Do I need the Reed API key?

No. Without one the actor reads the public search pages, which carry the most fields per row. With one it uses Reed's official API, which is free to register, is the route Reed intends for this data, and returns up to 100 jobs per page instead of 25. Its search results carry fewer fields (Known limits lists them), and with includeDescription the full description still costs one extra request per job on either route.

Why are some salaries null?

Reed lets advertisers hide the salary. When they do, no figure is published anywhere on the listing, so the actor reports null rather than inventing a zero.

How do I scrape one company's jobs?

Run any search, take the companyId off a row from that employer, and pass it as employerProfileId with an empty query.

Do I need a proxy?

No. reed.co.uk answers from datacenter IPs today. If that changes the run fails with a typed block error and you can enable Apify Proxy in the input.

Legal and data posture

This actor reads publicly listed job advertisements from reed.co.uk. When you supply a free Jobseeker API key it uses Reed's own official API, which is the intended route for this data. It never logs in, never uses accounts or cookies from accounts, and collects no personal data about candidates. Request rates are modest and 429 responses are honoured with backoff. Data is delivered to you for your own use; we do not build or resell a corpus.

Support

Open an issue on the Issues tab; first response within 6 hours on business days. Every run writes a RUN_SUMMARY record to the key-value store with items delivered, events charged, and the stop reason.