Reed Jobs Real-Time Data

The fastest way to collect Reed.co.uk job postings on Apify. Turn any UK job search into clean, structured JSON — ready for spreadsheets, dashboards, automations, and AI workflows. Results land in your dataset in real time, as each job is collected.

Built for recruiters, talent teams, job boards, market researchers, and builders who need reliable UK hiring data at scale — without slow setups or messy exports.

---

Why this Actor

	Reed Jobs Real-Time Data	Typical job data tool
Speed	Fast per-job collection	Often 5–15 s per job
Memory	512 MB default	2–4 GB+
Setup	Run in seconds with prefilled input	Often complex configuration
Cost	Low compute, efficient runs	High
Output	Structured JSON, LLM-ready	Often messy or incomplete
Scale	Up to 1,000 jobs per keyword	Often capped lower
Filters	Full Reed.co.uk search filters	Often keyword-only
Modes	Search · Company jobs · Job links	Usually one mode only

---

Three ways to collect jobs

Mode	What it does	Best for
Job search	Keyword + location search with Reed filters	Market scans, role tracking, location-based hiring
Company jobs	All open roles from specific employers	Competitor monitoring, account-based recruiting
Job links	Structured data from individual Reed job URLs	Enriching a list you already have

Enable one or combine all three in a single run.

---

What you get — every job, fully structured

Each record is one job posting with featureType, jobId, and scrapedAt so you can sort, filter, and join with your own data.

Field	What it tells you
title, company, location, remoteWorkingOption	Role, employer, place, and work style
jobUrl, applyUrl, companyUrl, companyLogo	Direct links and employer branding
descriptionText, descriptionHtml	Full job description (when descriptions are enabled)
employmentType, contractType, isFullTime, isPartTime	How the role is classified
salary, salaryMin, salaryMax, salaryPeriod	Compensation signals
sector, parentSector, taxonomy	Industry and role category
isGraduate, isEasyApply, isAgency, isDirectEmployer	Listing and employer signals
postedAt, updatedAt, expiresAt	Freshness and availability
snippet	Short preview text from search results
searchQuery, searchLocation, searchCompany, position	Which search produced this row and its rank
totalResultsCount	Total matches for the search query

Set includeRaw: true if you need extended record data for custom processing.

featureType values: job (search) · company_job (company jobs) · scrape_by_url (job links)

---

Search like Reed.co.uk — get data like a database

Use the same filters job seekers use on Reed:

• Keywords — one search per keyword (e.g. software engineer, nurse, project manager)
• Title — narrow to a specific role name
• Company — filter by employer name
• Location — London, Manchester, Birmingham, and more (or UK-wide)
• Contract type — permanent, contract, temporary
• Employment hours — full-time, part-time
• Work style — remote, hybrid, on-site
• Date posted — any time, past month, week, or 24 hours
• Sort — relevance or most recent
• Salary range — minimum and maximum in GBP
• Radius — miles around your location
• Volume — up to 1,000 jobs per keyword
• Full descriptions — toggle complete job text on or off

---

Use cases — real outcomes

• Recruiting pipelines — build candidate-ready job lists by role, location, and seniority
• Job boards and aggregators — feed your product with fresh Reed listings daily
• Market and salary research — track who is hiring, where, and for what skills
• Competitive intelligence — monitor competitor hiring by company and function
• Sales and BD — spot companies in hiring mode for timely outreach
• Staffing agencies — track UK demand by region, role, and employer
• AI assistants and agents — summarize listings, score fit, draft outreach, or answer hiring questions
• Data warehouses and CRMs — push JSON into Snowflake, BigQuery, HubSpot, Airtable, or your stack via API

---

LLM and MCP integration

Output is structured JSON — ideal for ChatGPT, Claude, Gemini, LangChain, LlamaIndex, CrewAI, and custom agents. No cleanup step. No manual formatting. Just records your model can read.

Recommended workflow

1. Run the Actor with your keywords, companies, or job links.
2. Pull dataset items via Apify API, webhook, or export JSON/CSV.
3. Pass records to your LLM, vector store, or automation — one job per row.

Example: one job record for an LLM prompt

{
  "featureType": "job",
  "jobId": "57102667",
  "title": "R&D Software Engineer",
  "company": "FDM Group",
  "location": "London",
  "remoteWorkingOption": "hybrid",
  "employmentType": "contract",
  "salary": "£ 70,000 - £ 80,000 per annum",
  "descriptionText": "FDM is a global business and technology consultancy seeking a Software Engineer...",
  "postedAt": "2026-07-08T13:24:24.403",
  "jobUrl": "https://www.reed.co.uk/jobs/r-d-software-engineer/57102667",
  "searchQuery": "software engineer",
  "searchLocation": "London",
  "position": 1,
  "scrapedAt": "2026-07-11T12:00:00.000Z"
}

Apify MCP (Model Context Protocol)

Use the Apify MCP server so AI assistants can:

• Run this Actor with natural-language instructions
• Read dataset results directly in the chat
• Chain with other Actors (e.g. collect → score → CRM)

Typical MCP tool flow:

User: "Find 25 remote software engineer jobs in London and summarize each for outreach"
→ MCP runs Actor with jobKeywords=["software engineer"], jobLocation="London", jobRemote=["remote"]
→ MCP reads dataset items
→ LLM summarizes and drafts messages

API quick start

curl -X POST "https://api.apify.com/v2/acts/YOUR_ACTOR_ID/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "enableJobSearch": true,
    "jobKeywords": ["software engineer"],
    "jobLocation": "London",
    "jobsPerQuery": 25,
    "fetchJobDetails": true
  }'

Dataset items: GET https://api.apify.com/v2/datasets/{datasetId}/items?format=json

---

Input reference

Enable only what you need. All features are independent.

Input	Type	Default	Description
Job search
enableJobSearch	boolean	true	Keyword + location search
jobKeywords	string[]	["software engineer"]	One search per keyword
jobLocation	string	London	City or region (empty = UK-wide)
jobTitle	string	—	Optional title filter
jobCompany	string	—	Optional employer filter
jobTypes	enum[]	—	permanent, contract, temporary
jobEmploymentHours	enum[]	—	full_time, part_time
jobRemote	enum[]	—	remote, hybrid, onsite
jobDatePosted	enum	any	any, month, week, day
jobSort	enum	relevance	relevance or date
graduateOnly	boolean	false	Graduate listings only
directEmployerOnly	boolean	false	Direct employer preference
hideTrainingJobs	boolean	false	Exclude training listings
salaryFrom / salaryTo	integer	0	Annual salary range (GBP)
proximityMiles	integer	10	Search radius in miles
jobsPerQuery	integer	25	Max jobs per keyword
fetchJobDetails	boolean	true	Full descriptions and employer details
Company jobs
enableCompanyJobs	boolean	false	Employer profile scraping
companyUrls	string[]	—	Reed company profile URLs
jobsPerCompany	integer	25	Max jobs per company
Job links
enableScrapeByUrl	boolean	false	Scrape individual job URLs
jobUrls	string[]	—	Reed job page URLs
Output & limits
maxItems	integer	10000	Global cap across all features
webhookUrl	string	—	Optional real-time POST URL — dataset is always written; webhook is additional
webhookFormat	enum	json	json (full record) or slack (Slack message)
includeRaw	boolean	false	Attach extended record data
proxyConfiguration	object	residential GB	Apify proxy settings

Full schema: see .actor/input_schema.json or the Input tab on Apify Console.

---

Output reference

Each dataset row is one job record. Filter by featureType:

featureType	Description
job	Job from keyword search
company_job	Job from company profile
scrape_by_url	Job from a direct URL

Traceability fields on search results:

• searchQuery — keyword that produced this row
• searchLocation — location used in the search
• position — rank in results for that search

Export formats: JSON, CSV, Excel, RSS, or via API.

---

Webhook delivery (optional)

Every record is always saved to the Apify dataset first. If you set webhookUrl in the Output & limits section, each new job is also POSTed in real time to your endpoint — useful for CRMs, Slack, Zapier, Make, or custom pipelines.

Setting	Description
webhookUrl	Your endpoint (https). Leave empty to use dataset only.
webhookFormat	json — full job object. slack — compact Slack incoming-webhook message.

Webhook delivery is best-effort: a failed webhook never stops the run or prevents dataset writes.

Example — search with Slack alerts

{
  "enableJobSearch": true,
  "jobKeywords": ["data analyst"],
  "jobLocation": "Manchester",
  "jobsPerQuery": 50,
  "webhookUrl": "https://hooks.slack.com/services/YOUR/WEBHOOK/URL",
  "webhookFormat": "slack"
}

Example — search with JSON webhook to your CRM

{
  "enableJobSearch": true,
  "jobKeywords": ["project manager"],
  "jobLocation": "Birmingham",
  "fetchJobDetails": true,
  "webhookUrl": "https://your-crm.example.com/api/jobs",
  "webhookFormat": "json"
}

---

Quick start — run immediately

The default input is ready to test. Open the Actor on Apify and click Start with no changes:

{
  "enableJobSearch": true,
  "jobKeywords": ["software engineer"],
  "jobLocation": "London",
  "jobsPerQuery": 25,
  "fetchJobDetails": true
}

Remote roles in London

{
  "enableJobSearch": true,
  "jobKeywords": ["software engineer"],
  "jobLocation": "London",
  "jobRemote": ["remote"],
  "jobsPerQuery": 50,
  "fetchJobDetails": true
}

Company hiring monitor

{
  "enableJobSearch": false,
  "enableCompanyJobs": true,
  "companyUrls": ["https://www.reed.co.uk/jobs/awin-69909/p69909"],
  "jobsPerCompany": 50
}

Enrich a URL list

{
  "enableJobSearch": false,
  "enableScrapeByUrl": true,
  "jobUrls": [
    "https://www.reed.co.uk/jobs/r-d-software-engineer/57102667"
  ]
}

---

Proxy & performance

• Apify residential proxy (GB) is enabled by default — optimised for Reed.co.uk.
• Default memory: 512 MB — enough headroom for most runs.
• Results are streamed to the dataset as they are collected; long runs do not pile up data in memory.

---

Limitations & compliance

• Not affiliated with Reed.co.uk. Use responsibly and comply with applicable laws and Reed's Terms of Service.
• Respect rate limits and data protection regulations when collecting and storing job data.
• Some filters depend on what Reed.co.uk exposes for a given search — unavailable filters are skipped gracefully.

---

Contact & custom work

Need something beyond this Actor? I build custom scrapers, data pipelines, and full-stack web applications for startups and enterprises.

• Email: dubem115@gmail.com
• GitHub: github.com/DrunkCodes

Reach out for:

• Custom Apify Actors (any website or data source)
• UK job market, recruitment, and hiring intelligence at scale
• LLM & MCP integrations with your data stack
• Web apps, dashboards, and automation tools

---

Reed Jobs Real-Time Data · by DrunkCodes