Reed Jobs Scraper

Pulling jobs off Reed.co.uk by hand is slow work: you open each advert, copy the title and salary, note the company and location, then paste it all into a sheet. This scraper skips that. Give it a Reed search URL, or just a few roles and cities, and every matching job comes back as a clean row with the salary, employer, location, and full description already split into fields. Run one search or a whole batch of role-and-city pairings, and pay only for the jobs you pull.

What you get

Each job advert becomes one row with a steady set of fields, grouped like this:

• Role — roleTitle, roleSummary, listingUrl, jobPostId, workMode, fullTime, partTime, quickApply
• Employer — employerName, employerUrl, employerLogo
• Location — placeName, regionName
• Pay — payMin, payMax, payText
• Dates — postedAt, updatedAt, expiresAt, collectedAt

Quick start

1. Open Reed.co.uk, run the search you want, and copy the URL from your browser. Paste it into Reed search or listing URLs — or skip the URL and fill in Search terms and Job locations instead.
2. Set Jobs per URL or query to cap how many jobs each search returns.
3. Press Start.
4. Export the results as JSON, CSV, Excel, or XML when the run finishes.

Use cases

• Job board aggregation — keep a niche or regional job site stocked with fresh UK postings
• Hiring demand tracking — watch which roles and skills employers are advertising, and where
• Salary benchmarking — compare pay ranges for the same role across cities and work modes
• Recruitment lead generation — find companies actively hiring for the skills you place
• Labour market research — build a dataset of live vacancies for analysis or reporting

Input

You can drive the scraper two ways: paste Reed URLs directly, or give it search terms and locations and let it build the searches for you. If you supply both terms and locations, it pairs every term with every location and runs each pairing on its own.

Field	Type	Required	Description
jobSearchUrls	array of strings	No	Reed.co.uk search or listing URLs to scrape, one per line. When set, the search terms and locations are skipped. Prefilled with a Manchester Python developer search.
searchTerms	array of strings	No	Roles, skills, or employer names to look up. Only read when jobSearchUrls is empty.
jobLocations	array of strings	No	UK towns, cities, or postcodes to search within. Only read when jobSearchUrls is empty.
resultsPerQuery	integer	No	Jobs to pull per URL or search pairing. Default 50, up to 1000.
timeoutSeconds	integer	No	Seconds to wait on each request before giving up. Default 45.

Example input

{
    "jobSearchUrls": [],
    "searchTerms": [
        "Product Manager",
        "UX Designer"
    ],
    "jobLocations": [
        "Manchester",
        "Leeds"
    ],
    "resultsPerQuery": 50,
    "timeoutSeconds": 45
}

Output

Every job from your searches becomes one row, paginated automatically until the per-query limit is reached or the results run out. Fields that an advert does not publish come back as null, so your columns stay the same from row to row.

Example output

{
    "jobPostId": 56867019,
    "roleTitle": "Senior Software Engineer",
    "roleSummary": "We are looking for a Senior Software Engineer to join our platform team...",
    "listingUrl": "https://www.reed.co.uk/jobs/senior-software-engineer/56867019",
    "employerName": "Vermillion Analytics",
    "employerUrl": "https://www.reed.co.uk/jobs/vermillion-analytics/p100633",
    "employerLogo": "https://resources.reed.co.uk/profileimages/logos/thumbs/Logo_100633.png",
    "placeName": "Manchester",
    "regionName": "Greater Manchester",
    "payMin": 60000,
    "payMax": 75000,
    "payText": "£60,000 - £75,000 per annum",
    "workMode": "Hybrid",
    "fullTime": true,
    "partTime": false,
    "quickApply": true,
    "postedAt": "2026-05-06T14:09:00.507",
    "updatedAt": "2026-05-18T14:17:17.513",
    "expiresAt": "2026-06-17T23:59:59",
    "collectedAt": "2026-06-30T04:22:42.503Z"
}

Output fields

Field	Type	Description
jobPostId	integer	Reed's own numeric ID for the job post
roleTitle	string	Headline of the advertised role
roleSummary	string	Full write-up of the role, duties, and requirements
listingUrl	string	Direct link to the job post page on Reed
employerName	string	Company or recruitment agency behind the advert
employerUrl	string	Link to the employer's profile page on Reed
employerLogo	string	Link to the employer's logo image when published
placeName	string	Main location label shown on the advert
regionName	string	County or wider region the role sits in
payMin	integer	Bottom of the stated salary range, when given
payMax	integer	Top of the stated salary range, when given
payText	string	Salary written out in plain language with its rate period
workMode	string	How the role is worked: Remote, Hybrid, or On-site
fullTime	boolean	True when the role is advertised as full-time
partTime	boolean	True when the role is advertised as part-time
quickApply	boolean	True when the post accepts Reed's one-step application
postedAt	string	ISO timestamp for when the advert first went live
updatedAt	string	ISO timestamp for the most recent edit
expiresAt	string	ISO timestamp for when the advert is due to close
collectedAt	string	ISO timestamp marking when the row was captured

Tips for best results

• Use a real Reed URL when you can. Running a search on Reed.co.uk and pasting the URL gives you the exact filters you want; search terms and locations are the quick path when you do not have a URL handy.
• Keep resultsPerQuery modest on test runs. Try 20 to 50 first to confirm the fields fit your pipeline, then raise it for the full pull. The limit applies per URL or pairing, so each search gets a fair share.
• Mind the pairing math. Five search terms across four locations is twenty separate searches; the run grows quickly, so size it before you start.
• Raise timeoutSeconds toward 60 if you see requests timing out on slow pages.
• Salary fields can be empty. When an advert lists "Competitive" instead of a figure, payMin and payMax come back as null while payText still carries the wording.

How can I use Reed job data?

How can I use the Reed Jobs Scraper to track hiring demand across UK cities? Give it your target roles in searchTerms and a list of cities in jobLocations. It pairs each role with each city and returns every matching advert as a row with roleTitle, employerName, placeName, and payText. Group the rows by city or role to see where hiring is heaviest and which skills come up most.

How can I scrape Reed.co.uk salaries for benchmarking? Each row carries payMin, payMax, and a readable payText, alongside workMode and placeName. Pull a batch of adverts for one role, then compare pay ranges by location or by remote, hybrid, and on-site work to build a current salary picture for that role.

How can I export Reed job listings into a spreadsheet or CRM? Run the scraper, then download the dataset as CSV or Excel, or push it straight into a database or CRM through Apify's integrations. Every advert is one flat row with the employer, link, location, and dates already split out, so it drops into your tools without extra cleanup.

How can I collect Reed recruitment leads for an agency? Search the skills you place for, and the output gives you employerName and employerUrl for each company advertising right now. Filter for the roles you specialise in and you have a live list of employers worth a conversation.

Is it legal to scrape data?

Our actors are ethical and do not extract any private user data, such as email addresses or private contact information. They only extract what the user has chosen to share publicly. We therefore believe that our actors, when used for ethical purposes by Apify users, are safe.

However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.

You can also read Apify's blog post on the legality of web scraping.

Support

Questions, feature requests, or a field you'd like added? Reach out at data.apify@proton.me and we'll get back to you.