# NHS Jobs Scraper — New Vacancy Alerts (`magnova/nhs-jobs-scraper`) Actor

Search NHS Jobs — the official NHS recruitment board for England and Wales — by keyword, trust, location, Agenda for Change band and contract. Structured posting records plus only-new alerts on any saved search. $0.005 per posting, no start fee.

- **URL**: https://apify.com/magnova/nhs-jobs-scraper.md
- **Developed by:** [Magnova](https://apify.com/magnova) (community)
- **Categories:** Business, Automation, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 1,000 job postings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## NHS Jobs Scraper — New Vacancy Alerts

Search **NHS Jobs** — the official NHS recruitment board for England and Wales, run by the NHS Business Services Authority — and get structured posting records from the live vacancies NHS trusts publish there. Search by keyword, location and distance, employer/trust, Agenda for Change band, contract type, working pattern and staff group; take the current corpus in one run, or attach a monitor store and receive **only the postings that are new** on every run after.

No API key, no login, no proxies. Records are read from the board's own public candidate search pages — the same pages any visitor sees.

### What you get

Every delivered record is one posting, shaped like this (a real record delivered by this Actor):

```json
{
 "recordType": "POSTING",
 "advertRef": "C9220-26-0779",
 "jobTitle": "NICU Senior Staff Nurse",
 "employerName": "Whittington Hospital NHS Trust",
 "location": "London N19 5NF",
 "salary": "£47,951 to £56,863 a year",
 "payScheme": "Agenda for change",
 "band": "Band 6",
 "contractType": "Permanent",
 "workingPattern": "Full time",
 "datePosted": "2026-11-11",
 "closingDate": "2026-11-25",
 "descriptionSnippet": "We are looking for enthusiastic, dynamic and motivated Band 6 Neonatal staff nurses to join the Neonatal Unit at the Whittington Health Trust. We are ranked as 'Outstanding' for caring by the Care Quality Commission. If you are looking for flexible work that can fit around your family commitments this could be just what you are looking for! We are a level 2 unit within the North Central North East London Perinatal Network. We provide specialist care to neonates from 27 weeks gestation. The unit…",
 "vacancyUrl": "https://www.jobs.nhs.uk/candidate/jobadvert/C9220-26-0779"
}
```

### Pricing

**$0.005 per posting delivered — $5.00 per 1,000 postings. No start fee, no platform surcharge from this Actor.**

- A first corpus run capped at 500 postings costs **$2.50**.
- A staffing agency watching one profession UK-wide sees roughly 300–1,200 new postings a month — **$1.50–$6.00 that month** — and quiet days cost nothing.
- Tier discounts apply automatically: SILVER pays $0.00425 per posting, GOLD and above $0.0035.

**Not charged:**

- Postings already seen by your monitor store (duplicates)
- Postings outside your `publishedSince` cursor window
- Postings silently seeded on a `monitorOnlyNew` first run
- ERROR records and the run SUMMARY record

### Three ways to run it

**1. Corpus (default).** A run delivers the current matches for your search, newest first, up to your per-run cap. This is the backfill: use it to build a dataset, a jobs board or a market snapshot.

**2. Only-new monitoring.** Pick one of your key-value stores as the *Monitor state store* and schedule the run (hourly, daily, weekly). The first run delivers the current matches as a baseline; every later run delivers only postings whose advert reference was never seen. The reference is the board's own stable advert id — so only-new works by construction, not by fuzzy matching. Prefer to start clean? Turn on **Start monitoring silently** (`monitorOnlyNew`): the first run remembers the current matches without delivering or charging anything, and only postings published afterwards are ever delivered.

**3. Stateless cursor.** Hold state in your own workflow (Make, Zapier, a scheduler) instead: pass `publishedSince` (e.g. `"2026-11-01"`) and only postings whose NHS Jobs "Date posted" is on or after that date are delivered. The check runs on each advert's own posted date — boundary-inclusive and exact.

### Inputs

| Input | What it does |
|---|---|
| Keywords | A role, skill or phrase — an occupation, a specialty, an employer term. Empty = search by filters alone. |
| Location | A town, city or postcode area. Empty = all of England and Wales. |
| Distance | The board's own radius steps (5–100 miles) around the location. |
| Employer / trust | Filter to one NHS trust or other NHS employer, by name. |
| Pay bands / grades | The board's own codes: `BAND_2`–`BAND_9` (incl. `BAND_8A`–`BAND_8D`), `CONSULTANT`, `SPECIALTY_DOCTOR`, and the other published grades. |
| Contract types | `Permanent`, `Fixed-Term`, `Bank`, `Locum`, `Apprenticeship`, `Secondment`, `Training`, `Honorary`, `NHS Reservist`, `Voluntary`. |
| Working patterns | `full-time`, `part-time`, `job-share`, `flexible-working`, `remote-working`, `term-time-hours`, `compressed-hours`, `annualised-hours`. |
| Staff groups | The NHS staff group codes (`NURSING_AND_MIDWIFERY_REGD`, `MEDICAL_AND_DENTAL`, `ALLIED_HEALTH_PROF`, …). |
| Posted on/after | The stateless cursor described above. |
| Monitor state store | Your key-value store — the memory behind only-new delivery. One store per saved search. |
| Start monitoring silently | Skip the baseline: seed silently, deliver only what's new afterwards. |
| Maximum postings per run | Delivery (and charge) cap per run, 1–1,000. Default 500. |
| Maximum total charge per run (USD) | Optional hard stop for the run's charges. |

### Output fields

| Field | Meaning |
|---|---|
| `advertRef` | The advert's stable reference on NHS Jobs — the only-new key. |
| `jobTitle` | The title as published. |
| `employerName` | The employer's name as published — an NHS trust or other NHS employer. |
| `location` | The location line as published — town and postcode. |
| `salary` | The salary exactly as published (e.g. "£47,951 to £56,863 a year"). |
| `payScheme` / `band` | The pay scheme (e.g. "Agenda for change") and — for adverts whose scheme carries one — the band/grade label, read from the advert's own page and validated against the board's own grade labels. Adverts on other schemes publish no band; the field is then absent, never invented. |
| `contractType` / `workingPattern` | As published (e.g. "Permanent", "Full time"). |
| `datePosted` / `closingDate` | The board's own "Date posted" and the advert's closing date, as ISO dates. Every delivered record carries a verified `datePosted`. |
| `descriptionSnippet` | The first ~500 characters of the advert's job summary as plain text, with any email addresses or phone numbers the text contained removed. |
| `vacancyUrl` | The advert's page on NHS Jobs. |

Each run also ends with one **SUMMARY** record (totals, duplicates skipped, detail pages read, whether the run caught up or stopped at a cap), and an **ERROR** record if NHS Jobs could not be read — in that case nothing is charged for undelivered postings and the monitor state is not advanced, so the next run catches up.

### Use it from an AI agent (MCP)

This Actor is agent-ready: it is callable through Apify's MCP server like any public Actor. An agent can run a one-off search ("the newest Band 6 nursing postings in London") or keep a saved search under watch and report only what is new since the last check — the input schema is small, every field is described with examples, and the output is one flat record per posting.

### NHS Jobs API

There is no official NHS Jobs API for this data — this Actor is the API: one structured record per posting, from the board's own public pages, with only-new delivery and a stateless date cursor for workflow tools.

### FAQ

**Which NHS jobs are covered?** jobs.nhs.uk only — the recruitment board for NHS trusts in England and Wales. NHS Scotland (jobs.scot.nhs.uk), Northern Ireland and employers who recruit through Trac are separate platforms and are **not** covered by this Actor.

**Why do some records have no band?** The band exists only where the advert's pay scheme carries one — Agenda for Change adverts publish a band; consultant and other medical-grade adverts publish their grade instead (use the pay-band filter, which covers all grades). The Actor reads the band from the advert's own page and ships it only when it matches one of the board's own grade labels.

**Why is there no contact email or phone?** By design. Every advert page carries an "Employer contact details" block naming an individual to contact, and enquiry details sometimes appear inside advert text. That block is never read, and any email addresses or phone numbers inside the job summary text are removed before delivery. Employer *names* — business data, as published — are included.

**How are the dates defined?** `datePosted` is the board's own "Date posted" for the advert — the day it went live on NHS Jobs. The `publishedSince` cursor and the newest-first ordering both run on exactly this date.

**What if NHS Jobs is down or changes shape?** The run writes an ERROR record, charges nothing for undelivered postings, and leaves the monitor state untouched so the next run catches up. The Actor also reports its own failures and silent data drift to the publisher automatically.

**How does this compare to a snapshot scraper?** Snapshot tools re-sell you the whole corpus on every run (some also add a start fee). This Actor charges the corpus once, then only for postings that are actually new — a quiet day costs $0.00.

### Legal and data note

NHS Jobs is the NHS's official, public recruitment board; the vacancies are published by NHS trusts for public dissemination, and this Actor reads them through the board's own public candidate pages — no login, no account, no CAPTCHA bypass. It ships business and vacancy data only: trust names as published, locations, salaries, pay schemes and bands, dates and a contact-scrubbed job summary. No individual contact persons, email addresses or phone numbers are collected or delivered.

# Actor input Schema

## `keywords` (type: `string`):

What to search for on NHS Jobs — a role, skill or phrase (e.g. "nurse", "physiotherapist", "medical secretary"). Matched the way the board itself matches keywords. Leave empty to search by location, employer or filters alone.

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

A town, city or postcode area (e.g. "London", "Manchester", "LS1"). The board searches around it; use "Distance" to set the radius. Leave empty for the whole of England and Wales.

## `distanceMiles` (type: `string`):

How far around the location to search, using the board's own distance steps. Only applies when a location is given; without one it is ignored. Leave unset to use the board's own default radius.

## `employer` (type: `string`):

Filter to one employer — an NHS trust or other NHS employer name as the board knows it (e.g. "Whittington", "Imperial College Healthcare"). Leave empty for all employers.

## `payBands` (type: `array`):

Filter by the board's own pay band / grade codes: BAND_2, BAND_3, BAND_4, BAND_5, BAND_6, BAND_7, BAND_8A, BAND_8B, BAND_8C, BAND_8D, BAND_9, CONSULTANT, DOCTOR_OTHER, FOUNDATION_DOCTOR, SPECIALIST, SPECIALTY_DOCTOR, SPECIALTY_REGISTRAR, VERY_SENIOR_MANAGER. Several codes are combined with OR. Leave empty for all bands and grades.

## `contractTypes` (type: `array`):

Filter by contract type, using the board's own values: Apprenticeship, Bank, Fixed-Term, Honorary, Locum, NHS Reservist, Permanent, Secondment, Training, Voluntary. Several values are combined with OR. Leave empty for all contract types.

## `workingPatterns` (type: `array`):

Filter by working pattern, using the board's own values: full-time, part-time, job-share, flexible-working, remote-working, term-time-hours, compressed-hours, annualised-hours. Several values are combined with OR. Leave empty for all patterns.

## `staffGroups` (type: `array`):

Filter by NHS staff group code: NURSING_AND_MIDWIFERY_REGD, MEDICAL_AND_DENTAL, ALLIED_HEALTH_PROF, HEALTHCARE_SCIENTISTS, CLINICAL_SERVICES, ADMINISTRATIVE_AND_CLERICAL, ESTATES_AND_ANCILLARY, PROF_SCIENTIFIC_AND_TECHNICAL, STUDENTS. Several codes are combined with OR. Leave empty for all staff groups.

## `publishedSince` (type: `string`):

Optional stateless cursor for workflow tools (Make, Zapier, your own scheduler) that hold state themselves: only postings whose NHS Jobs "Date posted" is this ISO date or later are delivered — for example "2026-11-01" or "2026-11-01T00:00:00Z". The check runs on each advert's own posted date, boundary-inclusive and exact. Leave empty for no cursor.

## `monitorOnlyNew` (type: `boolean`):

Off (default): the first run delivers the search's current postings as a baseline batch (charged), later runs deliver only new ones. On: the first run silently remembers the current postings without delivering or charging anything, and only postings published afterwards are ever delivered. Only applies when a monitor store is selected; without a store every run is a baseline run.

## `monitorStore` (type: `string`):

A key-value store this Actor may read and write to remember which postings it has already seen — this is what makes only-new delivery work across runs. Use one store per saved search. Pick any store you own; the Actor keeps one small state record in it. Without a store, every run delivers the search's postings as a baseline and remembers nothing. If the store is missing or cannot be opened, the run continues in baseline mode and the SUMMARY record says so — it never crashes. The Actor remembers every posting it processed (including ones outside the cursor window), so widening the window later does not re-deliver old postings.

## `maxResults` (type: `integer`):

Hard cap on postings delivered (and charged) in one run. Results come back newest first (the board's Date posted order), so a capped run delivers the most recent matches. Postings a capped run could not deliver stay unseen in monitoring mode and are delivered by the next run if they still match.

## `maxTotalChargeUsd` (type: `number`):

Optional hard stop for this run's charges: delivery stops as soon as the charged postings reach this amount (checked conservatively at the highest per-posting price, so the run may stop slightly early on discounted tiers), and the SUMMARY record reports stoppedByMaxCharge. Undelivered new postings stay unseen, so the next run delivers them. Leave empty for no cap. The run-level maximum charge in the run options is also honoured exactly.

## Actor input object example

```json
{
  "keywords": "nurse",
  "location": "London",
  "distanceMiles": "10",
  "employer": "Whittington",
  "payBands": [
    "BAND_6"
  ],
  "contractTypes": [
    "Permanent"
  ],
  "workingPatterns": [
    "full-time"
  ],
  "staffGroups": [
    "NURSING_AND_MIDWIFERY_REGD"
  ],
  "publishedSince": "2026-11-01",
  "monitorOnlyNew": false,
  "maxResults": 100,
  "maxTotalChargeUsd": 1
}
```

# Actor output Schema

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

No description

# 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 = {
    "keywords": "nurse",
    "location": "London",
    "monitorOnlyNew": false,
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("magnova/nhs-jobs-scraper").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 = {
    "keywords": "nurse",
    "location": "London",
    "monitorOnlyNew": False,
    "maxResults": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("magnova/nhs-jobs-scraper").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 '{
  "keywords": "nurse",
  "location": "London",
  "monitorOnlyNew": false,
  "maxResults": 100
}' |
apify call magnova/nhs-jobs-scraper --silent --output-dataset

```

## MCP server setup

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

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/mdeAoepPRLr0ChUzw/builds/YyyFd3J0WJsL3Tirx/openapi.json
