# Reed Jobs Scraper: reed.co.uk UK Jobs & Salaries (`djbrooks111/reed-jobs`) Actor

Scrape reed.co.uk UK jobs by keyword, location, salary or employer: title, apply URL, and company, location and salary as min/max numbers where published. No key needed; the no-key route adds posted date, pay period, contract type, hybrid/remote and category. $0.50 per 1,000 jobs + $0.001 per run.

- **URL**: https://apify.com/djbrooks111/reed-jobs.md
- **Developed by:** [David Brooks](https://apify.com/djbrooks111) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 delivered jobs

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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:

```json
{
  "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:

```json
{ "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.

# Actor input Schema

## `query` (type: `string`):

Search keywords, e.g. "software developer". Leave empty to list everything in a location.

## `location` (type: `string`):

UK town, city or region, e.g. "London" or "Greater Manchester".

## `distanceMiles` (type: `integer`):

Radius around the location. Reed's own default is 10.

## `employmentType` (type: `string`):

Restrict to permanent, contract or temporary postings.

## `workPattern` (type: `string`):

Restrict to full-time or part-time postings.

## `minSalary` (type: `integer`):

Lowest advertised salary to include, in GBP.

## `maxSalary` (type: `integer`):

Highest advertised salary to include, in GBP.

## `employerProfileId` (type: `string`):

Reed employer profile id (the `companyId` on any row of this actor's output) — returns that company's full job feed instead of a keyword search.

## `since` (type: `string`):

ISO date, e.g. 2026-09-01. Jobs first listed before this date are skipped and never charged.

## `includeDescription` (type: `boolean`):

Fetch the full job description per job (one extra request per job; slower, same price). Without it you still get the teaser.

## `apiKey` (type: `string`):

Optional free Jobseeker API key from https://www.reed.co.uk/developers/jobseeker. With a key the actor uses Reed's official API; without one it reads the public search pages. Can also be supplied as the REED_API_KEY environment variable.

## `maxItems` (type: `integer`):

Hard cap on delivered jobs for this run. Default 25 keeps free trials cheap; raise it for production.

## `maxCostUsd` (type: `number`):

Hard stop: the run never charges more than this. Enforced before each request, not after.

## `stateNamespace` (type: `string`):

Optional suffix for this actor's cross-run state store, so separate schedules or test runs keep separate monitor baselines and watermarks (e.g. `prod`, `staging`).

## `proxyConfiguration` (type: `object`):

No proxy is needed for reed.co.uk today. Enable one only if you see blocks.

## `outputFormat` (type: `string`):

flat (default): one level of keys, spreadsheet-friendly. nested: keep objects.

## Actor input object example

```json
{
  "query": "software developer",
  "location": "London",
  "distanceMiles": 10,
  "employmentType": "any",
  "workPattern": "any",
  "includeDescription": false,
  "maxItems": 25,
  "maxCostUsd": 5,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "outputFormat": "flat"
}
```

# Actor output Schema

## `results` (type: `string`):

Every delivered row, validated against the actor's entity schema (flat keys, ISO dates, sourceUrl, scrapedAt, sourceId). Only delivered rows are billed.

## `runSummary` (type: `string`):

RUN_SUMMARY: items delivered, events charged, USD charged, blocks met, requests made, the typed error if the run failed, and actor-specific meta.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "software developer",
    "location": "London",
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("djbrooks111/reed-jobs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "query": "software developer",
    "location": "London",
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("djbrooks111/reed-jobs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "software developer",
  "location": "London",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call djbrooks111/reed-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,djbrooks111/reed-jobs"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/QYQZTfhxYlNFl8FYj/builds/CbMgNr6jz5PUSyeBu/openapi.json