Reed.co.uk Jobs Feed β€” UK Job Listings with Salary & Contact avatar

Reed.co.uk Jobs Feed β€” UK Job Listings with Salary & Contact

Pricing

from $2.00 / 1,000 results

Go to Apify Store
Reed.co.uk Jobs Feed β€” UK Job Listings with Salary & Contact

Reed.co.uk Jobs Feed β€” UK Job Listings with Salary & Contact

Extract structured job listings from reed.co.uk β€” the UK's #1 job site. Salary details, employer profiles, incremental mode, and MCP-ready output.

Pricing

from $2.00 / 1,000 results

Rating

0.0

(0)

Developer

Black Falcon Data

Black Falcon Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

πŸ” What is Reed.co.uk Jobs Feed β€” UK Job Listings with Salary & Contact?

Extract structured job listings from reed.co.uk β€” the UK's #1 job site. Salary details, employer profiles, incremental mode, and MCP-ready output.

Reed.co.uk Jobs Feed β€” UK Job Listings with Salary & Contact

reed.co.uk is a public source platform, but it does not provide the kind of structured export most teams need for recurring data workflows. This actor bridges that gap by turning the source into clean JSON with company metadata, with direct API access and a schema that is easier to reuse in dashboards, enrichment pipelines, and agent workflows.

🎯 What you can do with this actor

  • Feed compact listing data into AI agents, MCP tools, and ranking workflows without carrying full raw payloads every time.
  • Start with lightweight search runs, then enable detail enrichment only when you need deeper company or listing context.

✨ Why choose this actor?

FeatureThis actorTypical alternatives
Collection strategyCan stay lightweight or add enrichment only when neededOften fixed to one scraping mode
AI-agent usabilityCompact output mode for smaller, more controllable payloadsOften full payload only
Schema qualityKeeps company metadata in a consistent output shapeOften inconsistent across runs
Stable downstream schemaTyped fields with nulls when unavailableOften requires extra cleanup

πŸš€ Quick start

Basic search:

{
"query": "software engineer",
"maxResults": 50,
"graduate": false,
"includeDetails": true,
"descriptionMaxLength": 0,
"compact": false,
"incrementalMode": false
}

Incremental monitoring:

{
"query": "software engineer",
"maxResults": 50,
"graduate": false,
"includeDetails": true,
"descriptionMaxLength": 0,
"compact": false,
"incrementalMode": true,
"stateKey": "daily-monitor"
}

πŸ“Š Sample output

{
"title": "Example title",
"company": "Example company",
"location": "Example location",
"url": "https://reed.co.uk"
}

βš™οΈ Input reference

ParameterTypeDefaultDescription
Search
querystringβ€”Job search keywords (e.g. 'software engineer', 'nurse', 'marketing manager').
locationstringβ€”City, region, or postcode (e.g. 'London', 'Manchester', 'EC2R').
maxResultsinteger50Maximum total results to return (0 = unlimited).
Filters
jobTypeenumβ€”Filter by contract type.
workTypeenumβ€”Filter by hours.
postedByenumβ€”Filter by recruiter type.
salaryFromintegerβ€”Filter: minimum salary (annual Β£).
salaryTointegerβ€”Filter: maximum salary (annual Β£).
graduatebooleanfalseOnly show graduate positions.
employerIdintegerβ€”Filter by specific Reed employer ID.
Enrichment
includeDetailsbooleantrueFetch full job details (description, salary type, external URL). Costs 1 extra API call per job.
descriptionMaxLengthinteger0Truncate description to N characters. 0 = no truncation.
Output
compactbooleanfalseCore fields only β€” optimized for AI-agent and MCP workflows.
Incremental Tracking
incrementalModebooleanfalseOnly return new/changed jobs since previous run. Requires a stable stateKey.
stateKeystringβ€”Identifier for the tracked job universe (e.g. 'london-devs'). Different queries should use different keys.

πŸ“¦ Output fields

Each result can include company metadata, depending on listing content and the enrichment options enabled for the run.

This actor returns structured dataset items through the default Apify dataset output. See the sample output above for the practical field shape.

⚠️ Known limitations

  • Contact information is only returned when the source exposes it directly; many listings will still rely on apply URLs rather than named contacts.
  • Company profile fields depend on source availability and may be limited for portals that do not expose employer metadata.
  • Field population rates always depend on the source site itself, so null values are normal for data points the source does not publish on every listing.

πŸ’° How much does it cost to scrape reed jobs feed?

This actor uses pay-per-event pricing, so you pay a small run-start fee and then only for results that are actually emitted. The source currently looks efficient to access, which helps keep pricing attractive for repeat usage.

EventPriceWhen
actor-start$0.01Each run
result$0.002Per emitted record

Example costs:

ScenarioResultsCost
Quick test10$0.03
Daily monitor50$0.11
Full scrape500$1.01

πŸ’‘ Use cases

Recruiting and sourcing

Pull reed.co.uk listings into dashboards, triage queues, or recruiter workflows without re-normalizing the source on every run.

Recurring monitoring

Track only newly posted or changed listings on scheduled runs, which is better suited to alerts and daily pipeline jobs than repeated full exports.

AI-agent and MCP workflows

Feed compact listing data into ranking, summarization, classification, or agent pipelines without burning unnecessary context on large descriptions.

Data pipelines and exports

Export repeatable JSON to CSV, warehouses, internal APIs, or downstream transformations without site-specific cleanup logic in every consumer.

πŸ€– AI-agent and MCP usage

This actor is suitable for AI-agent workflows because the output is structured and the input can intentionally reduce payload size for downstream tools.

  • compact returns a smaller core schema for ranking, classification, and MCP tool calls.
  • descriptionMaxLength lets you cap description size so larger batches stay practical in model context windows.
{
"query": "software engineer",
"maxResults": 10,
"graduate": false,
"includeDetails": true,
"descriptionMaxLength": 300,
"compact": true,
"incrementalMode": false
}

πŸ”„ Incremental mode

Incremental mode is intended for repeated monitoring runs where only new or changed listings should be emitted.

Change typeMeaning
NEWFirst time seen in the monitored result set
CHANGEDPreviously seen listing with updated content
UNCHANGEDSame listing and content as a prior run when unchanged emission is enabled
EXPIREDListing disappeared from the monitored result set when expired emission is enabled

πŸ“– How to scrape reed jobs feed

  1. Open the actor in Apify Console and review the input schema.
  2. Enter your search query and location settings, then set maxResults for the amount of data you need.
  3. Enable optional enrichment fields only when you need richer output such as descriptions, contacts, or company data.
  4. Run the actor and export the dataset as JSON, CSV, or Excel for downstream analysis.

❓ FAQ

What data does this actor return from reed.co.uk?

It returns structured listing records with fields such as company metadata, plus the core identifiers and metadata defined in the dataset schema.

Can I fetch full descriptions and detail fields?

Yes. Enable the detail-related input options when you need richer fields such as descriptions, employer metadata, or contact details from the listing detail pages.

Does it support recurring monitoring?

Yes. Incremental mode is built for recurring runs where you only want newly seen or changed listings instead of a full repeat dataset every time.

Is it suitable for AI agents or MCP workflows?

Yes. Compact mode and output-size controls make it easier to use the actor in AI-agent workflows where predictable fields matter more than raw page size.

Why use this actor instead of scraping the site ad hoc?

Because it already handles direct API access, keeps a stable schema, and exposes filters and enrichment options in a form that is easier to automate repeatedly.

This actor is intended for publicly accessible data workflows. Always review the target site terms and your own legal requirements for the way you plan to use the data.