Reed Scraper - UK Jobs, Salaries & New-Job Alerts

For recruiters, job-market analysts and job seekers who want Reed UK job listings as clean spreadsheet-ready data. Give it search terms or Reed search URLs and get one row per job: title, company, location, displayed salary numbers, remote flag and posting date. No login, proxies or cookies, and no Reed account needed. Turn on new-job alerts (onlyNewSinceLastRun) and run it on a schedule to receive only jobs you have not been given before.

Pay-per-result: $0.0015 per job — 1,000 jobs = $1.50. You are charged only for rows that land in your dataset.

Quick start

1. Open the Input tab and use the prefill below, or replace the search term with your own (for example data analyst, nurse, electrician).
2. Click Start.
3. Open the dataset and export it as CSV, Excel, JSON or XML.

{
  "searchTerms": [
    "python"
  ],
  "startUrls": [],
  "maxPagesPerSearch": 2,
  "maxItems": 20,
  "onlyNewSinceLastRun": false,
  "stateStoreName": "reed-jobs-scraper-seen-jobs"
}

Use searchTerms, public Reed search-page startUrls, or both. maxPagesPerSearch defaults to 2 (range 1-10) and maxItems defaults to 100 (hard maximum 5,000), so maxItems doubles as your cost cap.

Example output

One flat row per job. This row is produced by the Actor's parser from a captured Reed search page:

{
  "id": "57397629",
  "url": "https://www.reed.co.uk/jobs/python-engineer/57397629",
  "title": "Python Engineer",
  "company": "Ncounter",
  "location": "London",
  "salaryText": null,
  "salaryMin": 90000,
  "salaryMax": 100000,
  "salaryCurrency": "GBP",
  "contractType": null,
  "remote": false,
  "postedAt": "2026-09-28T09:49:19.477"
}

Every row also carries searchTerm, page, position, sourceUrl and scrapedAt so you can trace where it came from. Any value Reed does not publish is null; nothing is guessed.

Use cases

• Recruiters and sourcers tracking which UK employers are hiring for a skill or job title, and at what advertised pay.
• Job-market analysts building UK salary-range and hiring-volume datasets by keyword and location, without opening listings one at a time.
• Job seekers who want a Reed job alert for a saved search delivered to a sheet, Slack or email on a schedule.
• Job boards and HR-tech teams that need structured UK listings instead of maintaining their own Reed parser.

Job alerts: get only new jobs

1. Set your search terms or Reed search URLs, then set onlyNewSinceLastRun to true.
2. Click Schedule on the run page (or create one under Schedules in the Apify Console). Daily works well for an active search.
3. The first run is a baseline: it delivers (and charges for) every job currently listed and remembers their ids. Every later run delivers only ids it has not delivered before for that search.
4. Add a webhook or integration (Slack, email via Zapier/Make, Google Sheets) on run success to forward the new rows.

A run with nothing new still succeeds with an empty dataset and costs nothing. stateStoreName only needs changing if you want to reset or isolate a watch.

Get new Reed job alerts in Discord, Telegram, Slack, Teams, Google Chat, your phone (ntfy/Pushover) or any app (webhook)

Want a Reed job alert in Discord, Telegram or on your phone instead of checking a dataset? Add one or more destinations in the Actor's Notifications (optional) section and each run sends the jobs it delivered. It is a monitor that notifies you: it only reads public Reed search pages, and it never applies to a job, contacts an employer or logs in to Reed.

Channel	Fill in	What you get
Discord	discordWebhookUrl	One card per job, 10 per message
Telegram	telegramBotToken + telegramChatId	Up to 10 jobs per message, one line each
Slack	slackWebhookUrl	Block Kit message, up to 10 jobs per message
Mattermost, Rocket.Chat	slackCompatibleWebhookUrl	Slack-style incoming webhook: a Markdown list (these apps do not render Slack Block Kit)
Microsoft Teams	teamsWebhookUrl	Adaptive Card from a Teams Workflows webhook, up to 10 jobs per card
Google Chat	googleChatWebhookUrl	Card in a space, up to 10 jobs per message
ntfy (phone push, no account)	ntfyTopic (optional ntfyServer, ntfyToken)	A push per job, up to 10, then one "...and N more"
Pushover (phone push)	pushoverUserKey + pushoverAppToken	A push per job, up to 10, then one "...and N more"
Any app: Zapier, Make, n8n, Pipedream, IFTTT, Home Assistant	webhookUrl	One JSON POST per run with every delivered row

Fill in as many as you like; each channel works on its own and a failing one never stops the others.

Setup, channel by channel

• Discord (1 minute): Server Settings → Integrations → Webhooks → New Webhook → pick the channel → Copy Webhook URL.
• Telegram (2 minutes): chat with @BotFather, send /newbot, paste the token into telegramBotToken. Add the bot to the chat or channel (administrator for a channel; for a chat with yourself press Start on the bot). telegramChatId is a numeric id (123456789, or -1001234567890 for a group or channel) or a public @channelusername.
• Slack: at api.slack.com/apps create an app (From scratch) → Incoming Webhooks → switch it on → Add New Webhook to Workspace → pick the channel → copy the https://hooks.slack.com/services/... URL.
• Mattermost or Rocket.Chat: create an incoming webhook in the app and paste its public https:// URL into slackCompatibleWebhookUrl. It must be reachable from the internet: localhost, private IP addresses and .local / .internal names are rejected.
• Microsoft Teams: in the channel open ... → Workflows → Post to a channel when a webhook request is received → finish the wizard and copy the URL (a host ending in .logic.azure.com or .powerplatform.com). The old "Office 365 connector" webhooks are retired and not supported.
• Google Chat: in the space open Apps & integrations → Webhooks → Add webhook, name it and copy the https://chat.googleapis.com/v1/spaces/... URL (needs a Google Workspace account that allows webhooks).
• ntfy (free, no account): install the ntfy app (or open ntfy.sh), subscribe to a topic with a long random name, and put the same name in ntfyTopic. Anyone who knows the topic can read it, so make it unguessable. Own server or a protected topic: set ntfyServer (public https:// address) and ntfyToken.
• Pushover: copy your user key from pushover.net into pushoverUserKey, create an application at pushover.net/apps/build and put its API token in pushoverAppToken. Pushover itself is a separate paid app after its trial: check their pricing.
• Any app (webhook): paste the catch-hook URL from Zapier, Make, n8n, Pipedream, IFTTT or Home Assistant into webhookUrl. It must be a public https:// address.

The recipe: a Reed job alert in five steps

1. Set your search terms (or paste a Reed search URL with your filters into startUrls).
2. Turn on onlyNewSinceLastRun.
3. Add your destination(s) from the table above.
4. Run it once. The first run is the baseline and sends the jobs currently listed (up to maxNotifications).
5. Create a Schedule (daily works for most searches, hourly for a busy one). From then on you only hear about jobs it has not delivered before.

{
  "searchTerms": [
    "python developer"
  ],
  "maxPagesPerSearch": 2,
  "maxItems": 100,
  "onlyNewSinceLastRun": true,
  "discordWebhookUrl": "https://discord.com/api/webhooks/<id>/<token>",
  "ntfyTopic": "your-long-random-topic-name",
  "maxNotifications": 25
}

The generic webhook (webhookUrl)

Each run sends one POST per 100 delivered rows (so usually one) with this body, followed by whatever your tool does with it:

{
  "source": "apify",
  "actor": "reed-jobs-scraper",
  "runId": "HG7ML7M8z78YcAPEB",
  "count": 2,
  "total": 2,
  "part": 1,
  "parts": 1,
  "items": [
    {
      "...": "the full dataset rows"
    }
  ]
}

count is the number of rows in this POST, total the number delivered in the run, and part / parts number the POSTs when a run delivers more than 100 rows. maxNotifications does not cap the webhook: your tool gets every delivered row. Your endpoint should answer with a 2xx status; redirects are not followed and a failure is reported in the run status, never retried in a loop.

What each message contains

Each job is announced as New job: <title> at <company> — <location> with the link, the salary when Reed shows one (its own text, or the parsed range), the contract type and a Remote flag when Reed publishes them, the posting date, and the search term it matched. Anything Reed does not publish is simply left out. Discord gets a card per job, Telegram one line per job, Slack Block Kit sections, Teams an Adaptive Card, Google Chat a card, and ntfy/Pushover a push that opens the job. Link previews are off, and titles are escaped so a title can never inject formatting or mentions.

What to expect

• Only delivered jobs are sent. A run that finds nothing new sends nothing, so there is no "no new jobs" spam. Rows the run could not deliver (for example because your spending limit was reached) are not sent.
• Without onlyNewSinceLastRun, every delivered row is sent, so a scheduled plain run would repeat the same jobs: use alert mode for alerts (the message then says "New job"; a plain run says "Job").
• maxNotifications (default 25, max 100) caps how many jobs go to chat and phone channels per run (the webhook is not capped). The rest are still in the dataset and the status message says so. ntfy and Pushover send at most 10 individual pushes, then one "...and N more" summary.
• Cost: notifications are free. You pay only the usual price for delivered jobs, exactly as without alerts. There is no extra charge for any channel.
• Failures never fail the run. A deleted webhook or an unreachable service leaves the run successful and the dataset complete, and the status message says what happened, for example Notified: Discord 12, Slack 12, ntfy 10 (+summary). Teams failed (HTTP 404) - check the webhook URL. The logs show the channel name and HTTP status only, never a URL or token.
• Your URLs, tokens and ntfy topic are stored as secret inputs. Anyone holding a webhook URL can post to that channel, so treat it like a password.
• It is a monitor that notifies you. It never applies to jobs, contacts employers or logs in to Reed. The messages go only to the destinations you set up.
• Nothing changes by default. With no destination set, a run behaves exactly as before and the dataset rows are identical.

Pricing

Pay-per-event: $0.0015 per delivered job — 1,000 jobs = $1.50. Rows skipped by robots.txt, blocked pages, failures, or already-seen alert history are not delivered and are not charged. A run that returns nothing is not charged. Price changes follow Apify's notice rules; the Pricing tab always shows the rate you pay.

Notifications to Discord, Telegram, Slack, Teams, Google Chat, ntfy, Pushover and webhooks are free: you pay only for delivered jobs, never for messages sent.

Limitations

• Search results only. The Actor reads Reed search-result pages. It never opens individual job detail pages, so full descriptions, requirements and application links are not included.
• Salary is what the search result exposes. Reed's captured search data gives salary numbers and a currency id but no formatted salary text or contract-type label, so salaryText and contractType are null. salaryMin and salaryMax can be annual figures (for example 90000) or day/hourly-style rates (for example 600) depending on the role; there is no unit field, so check the range before comparing. salaryCurrency is GBP only where the source id clearly maps to pounds.
• Robots.txt only. Every requested path is checked against Reed's robots.txt first; disallowed paths are skipped, not bypassed. Requests are spaced about three seconds apart with an identifying User-Agent. No login, CAPTCHA solving or proxies.
• Pages, not the full archive. Up to 10 pages per search. If a later page fails or becomes disallowed, rows already delivered are kept and the run reports partial results instead of pretending the search completed.
• No personal data. Only job and company fields are collected; nothing about recruiters or individuals.
• Layout changes. If Reed changes its page structure, the run fails with a clear error instead of returning bad rows.

Use it from your code, Make, Zapier or n8n

Built for automated pipelines: small runs, stable field names, one row per item, and you pay only for rows actually delivered.

One API call that runs the Actor and returns the data (replace $APIFY_TOKEN with your token from Apify Console → Settings → Integrations):

curl -s -X POST "https://api.apify.com/v2/acts/lukehunter~reed-jobs-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"searchTerms": ["python"], "maxPagesPerSearch": 2, "maxItems": 20}'

JavaScript (npm i apify-client):

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('lukehunter~reed-jobs-scraper').call({
  "searchTerms": [
    "python"
  ],
  "maxPagesPerSearch": 2,
  "maxItems": 20
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python (pip install apify-client):

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('lukehunter~reed-jobs-scraper').call(run_input={"searchTerms": ["python"], "maxPagesPerSearch": 2, "maxItems": 20})
items = client.dataset(run['defaultDatasetId']).list_items().items

Schedules, webhooks and no-code tools: save your input as a Task, add a Schedule (e.g. hourly or daily), and attach a webhook or one of the Integrations tab's connectors (Make, Zapier, n8n, Google Sheets, Slack) to push each run's results into your own system.

Only new items each run: set "onlyNewSinceLastRun": true on a scheduled Task and every run after the first delivers, and charges for, only items it hasn't delivered before for that same input. That makes it a ready-made change feed.

Reliability: an automated test runs this Actor's parser against the live site every day, and failures are fixed fast.

Feedback: an honest rating on the Store page, good or bad, helps others decide if this Actor fits their needs. Missing a field or found a problem? Open an issue on the Actor page.

FAQ

How much does it cost? $0.0015 per delivered job, so 1,000 jobs cost $1.50. Set maxItems to cap spend; it is a hard limit.

Can I get only new jobs, on a schedule? Yes. Turn on onlyNewSinceLastRun and attach an Apify Schedule. The first run is a baseline; later runs deliver only unseen jobs.

What export formats are available? Anything the Apify dataset supports: CSV, Excel, JSON, XML, RSS and HTML table, plus the API for direct integrations.

Why are salaryText and contractType empty? Reed's search data does not expose them, so the Actor returns null rather than inventing a value.

Can I use a Reed search URL I built with filters? Yes. Paste public Reed search-result URLs into startUrls; pagination is normalised and controlled by maxPagesPerSearch.

Can I get Reed job alerts in Discord, Telegram, Slack or on my phone? Yes. Set discordWebhookUrl, telegramBotToken + telegramChatId, slackWebhookUrl, teamsWebhookUrl or googleChatWebhookUrl, or use ntfyTopic (free, no account) or pushoverUserKey + pushoverAppToken for phone pushes. Mattermost and Rocket.Chat work through slackCompatibleWebhookUrl. With onlyNewSinceLastRun on and a schedule, each run sends only the jobs it has not delivered before. Setup steps for each are in the alerts section above. Notifications cost nothing extra.

Can I get Reed job alerts by email? Not natively. There are two routes. (1) Set webhookUrl to a Zapier, Make or n8n catch hook and add an email or Gmail step: the webhook delivers every row as JSON, so the email can list the jobs. (2) Apify's own run integrations and run notifications can email you when a run finishes, but they only send a link to the run or dataset, not the jobs themselves. For instant alerts without building anything, Telegram, ntfy or Pushover reach your phone directly.

Can I get Reed job alerts in WhatsApp? Not natively, and we do not use unofficial WhatsApp APIs, which risk getting your number banned. The official route is the WhatsApp Business Platform (Cloud API) with its own business account, message templates and pricing: point webhookUrl at a Zapier, Make or n8n flow that calls it. For free phone alerts use Telegram or ntfy instead.

More from this publisher

• Vinted Scraper & New Listing Alerts — public Vinted search listings with new-item alerts.
• Vinted Cross-Country Prices — compare public Vinted asking prices across countries.
• Jobindex Jobs Scraper — another public listing/data Actor from this batch.
• Pracuj.pl Jobs Scraper — another public listing/data Actor from this batch.
• Substack Scraper — another public listing/data Actor from this batch.