Python Developer - London (Hybrid) - Up to £45,000
...", "isNew": true, "source": "reed.co.uk", "scrapedAt": "2026-09-26T05:19:45.139Z" }, { "jobId": "57355173", "title": "Python Developer", "companyName": "Pontoon", "workModel": "remote", "isRemote": true, "contractType": "contract", "salaryText": "Salary negotiable", "salaryDisclosed": false, "salaryMin": null, "salaryAnnualMin": null }, { "jobId": "57363584", "title": "AWS/Python Software Engineer", "companyName": "E.ON", "workModel": "hybrid", "contractType": "permanent", "salaryText": "Competitive salary", "salaryDisclosed": false, "salaryMin": null, "salaryAnnualMin": null } ] ``` You can download the dataset in various formats such as JSON, HTML, CSV, or Excel from the **Dataset** tab or the API. #### Output fields | Field | Type | Description | | ---------------------------------------------------------- | -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `jobId`, `url` | string | Reed's job ID and canonical URL (tracking parameters removed). | | `title`, `companyName`, `companyProfileUrl` | string | null | Job title, employer name, and the employer's reed.co.uk profile page (not their own website; `null` if they don't have one). | | `locationText`, `city`, `region`, `postcode`, `country` | string | null | Location as shown on the page, plus parsed components where Reed provides them. | | `isRemote`, `workModel` | boolean | null, `onsite`/`hybrid`/`remote`/`null` | Derived from Reed's own work-model tag; `null` when Reed doesn't state one. | | `employmentType` | string\[] | e.g. `["FULL_TIME"]`, `["FULL_TIME","CONTRACTOR"]`. | | `contractType` | `permanent`/`contract`/`temporary`/`null` | | | `salaryText` | string | null | The salary exactly as displayed on the page. | | `salaryDisclosed` | boolean | `false` when Reed hides the number behind "Competitive salary" / "Salary negotiable" (the underlying figures, if any, are not reliable, so they're not exposed either). | | `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod` | number | null | The figures as posted (`salaryPeriod`: `hour`/`day`/`week`/`month`/`year`). | | `salaryAnnualMin`, `salaryAnnualMax` | number | null | Annualized: `hour × 1950` (37.5h × 52wk), `day × 260` (5d × 52wk), `week × 52`, `month × 12` - the same assumptions reed.co.uk's own site uses. | | `datePosted`, `validThrough` | ISO 8601 string | null | | | `descriptionSnippet`, `descriptionText`, `descriptionHtml` | string | null | Short summary, plain text, and cleaned HTML - emails and UK phone numbers redacted in all three. | | `isNew` | boolean | `true` if this job hasn't been seen before for this run's `monitorKey` (see below). | | `source`, `scrapedAt` | string | Always `"reed.co.uk"`, and the ISO timestamp the item was scraped. | `includeDetails: false` fills only the fields available from the search-results page; the rest are `null`. ### Pricing This Actor uses [pay-per-event](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing. | Event | Price | When you're charged | | ---------------- | ----------------------- | ----------------------------------------------------------------------- | | Actor start | $0.003 per run | Once per run, regardless of how many results come back | | `detail-result` | $0.50 per 1,000 results | Once per result with `includeDetails: true` (full job data) | | `listing-result` | $0.10 per 1,000 results | Once per result with `includeDetails: false` (search-results data only) | A failed request, an in-run duplicate, or a job skipped by monitoring mode is never charged as a result - only the flat start fee applies regardless of how many (if any) results come back, which covers the fixed cost of a run, e.g. a scheduled monitoring run that finds nothing new. Based on real Apify Cloud measurements, running this Actor costs roughly $0.13 per 1,000 results with `includeDetails: true`, $0.01 per 1,000 with `includeDetails: false`, and about $0.001 for a monitoring run that finds zero new postings - so pricing is set with a comfortable margin even if blocking or retries are worse than measured on a given day. ### Monitoring mode Set **Only new jobs** (`onlyNewJobs: true`) to get only postings you haven't seen before, and avoid paying for ones you have. Give each distinct search a **Monitoring key** (`monitorKey`) so their "seen" lists don't mix. - **First run** for a given `monitorKey`: every job is new, nothing is skipped. - **Later runs**: an already-seen job is skipped before its detail page is even fetched - no request, no dataset item, no charge. A job whose fetch failed is *not* recorded as seen, so it's retried on the next run instead of being silently lost. - `isNew` is reported on every result regardless of this setting, so you can see what's new even without monitoring mode on. - **Recommended for scheduled monitoring:** set **Posted within** to `today` or `lastThreeDays` alongside `onlyNewJobs`. A narrower search matches far fewer listing pages each run, so it's both faster and cheaper - useful because a monitoring run still has to fetch listing pages to discover what's new, even once most of a broad search's results are already marked as seen. - To automate it, add a [Schedule](https://docs.apify.com/platform/schedules) (e.g. every hour or every morning) with `onlyNewJobs: true`, and connect the run's webhook or dataset to [Zapier](https://apify.com/integrations), Make or n8n to post new jobs to Slack, email, or a spreadsheet. ### Limitations - **Sorting isn't supported.** reed.co.uk's `robots.txt` disallows crawling search URLs with a `sortBy` parameter, so this Actor never sends one; results come back in reed.co.uk's default order. - **`maxItems` is a target for successful results, not a hard request cap.** The Actor queues a small buffer of extra candidate jobs (5% of `maxItems`, minimum 2) so a handful of failed detail pages (blocked, removed, unparseable) don't leave you short. If more detail pages fail than that buffer covers, you can get fewer than `maxItems` results - never more. - **Some blocking is expected and retried automatically.** Like any scraper, requests through Apify's shared proxies are occasionally blocked (403) or rate-limited; the Actor retries with a fresh proxy session and backoff (up to 3 attempts) before giving up on that one page. In early testing, roughly half of first attempts through a datacenter proxy were blocked, and about 9 in 10 requests ultimately succeeded within 3 attempts - a small fraction of pages can still fail on a given run. - **Salary annualization is an estimate.** It assumes a 37.5-hour, 5-day working week (reed.co.uk's own convention) and doesn't account for actual contracted hours, which reed.co.uk doesn't always state. - **Concurrent runs sharing the same `monitorKey` can overwrite each other's "seen" state**, since it's read once at the start of a run and written once at the end. Use a distinct `monitorKey` per search, and avoid scheduling overlapping runs for the same one. ### Legal disclaimer This Actor only collects data that is already public on reed.co.uk - no login, no paywalled content, and no bypassing of CAPTCHAs or bot-detection. Personal data found in job descriptions (email addresses, phone numbers) is redacted before delivery. You are responsible for using the collected data in compliance with reed.co.uk's Terms of Service and any applicable data-protection law (e.g. UK GDPR) in your jurisdiction. This Actor isn't affiliated with or endorsed by Reed.co.uk. ### FAQ **Does this Actor use my Reed account or require login?** No. It only reads reed.co.uk's public search and job pages. **Why is a job's salary `null` even though the listing shows a number?** Some postings mark their number as unreliable (e.g. "Competitive salary", "Salary negotiable"); when `salaryDisclosed` is `false`, the numeric fields are intentionally left `null` rather than showing a misleading figure. **Can I get notified only about brand-new postings?** Yes - see [Monitoring mode](#monitoring-mode) above. **Something looks wrong or missing.** Please open an issue in this Actor's **Issues** tab with the search you ran and what you expected - reed.co.uk changes its page structure occasionally, and reports like this are how it gets fixed quickly. Custom scraping solutions are also available on request. ### Changelog - **0.1** - Initial release: keyword/location/filter search, full job-detail scraping, salary normalization and annualization, remote/hybrid detection, PII redaction, new-job monitoring mode, pay-per-event billing. # Actor input Schema ## `keywords` (type: `string`): Job title or keywords to search for. Ignored if Start URLs is set. ## `location` (type: `string`): UK location to search near, e.g. "London" or "Manchester". Leave empty to search all of the UK. Ignored if Start URLs is set. ## `distanceMiles` (type: `integer`): Search radius around Location. Only used when Location is set. Must be one of the values reed.co.uk supports: 0, 1, 3, 5, 10, 15, 20, 30, 50 (other values are rejected). ## `salaryFrom` (type: `integer`): Minimum annual salary in GBP. reed.co.uk only offers fixed filter values (e.g. 10000, 12000, ..., 100000); the closest lower value is used automatically and a warning is logged if your value doesn't match exactly. ## `salaryTo` (type: `integer`): Maximum annual salary in GBP. reed.co.uk only offers fixed filter values (e.g. 10000, 12000, ..., 100000); the closest higher value is used automatically and a warning is logged if your value doesn't match exactly. ## `contractTypes` (type: `array`): Filter by contract type. Leave empty to include all types. ## `workingHours` (type: `array`): Filter by full-time/part-time. Leave empty to include all. ## `workModel` (type: `array`): Filter by onsite/hybrid/remote. Leave empty to include all. reed.co.uk only supports one value per request, so selecting 2 values runs 2 separate searches (results never overlap); selecting all 3 is the same as leaving this empty. ## `postedWithin` (type: `string`): Only include jobs posted within this time window. ## `startUrls` (type: `array`): Reed.co.uk search URLs (e.g. https://www.reed.co.uk/jobs/python-developer-jobs) or direct job URLs. When set, this takes priority over Keywords/Location/all filters above. ## `includeDetails` (type: `boolean`): If true, visits each job's detail page for the full description, exact location and confirmed contract type (slower, one extra request per job). If false, uses only the data available on the search results page (faster, cheaper). ## `maxItems` (type: `integer`): Maximum number of job results to return. ## `onlyNewJobs` (type: `boolean`): If true, skips jobs already seen in a previous run with the same Monitoring key, and does not charge for them. Intended for scheduled runs that monitor for new postings. ## `monitorKey` (type: `string`): Name for the monitoring state used by "Only new jobs". Use a different key per distinct search so their seen-job lists don't mix. ## `maxConcurrency` (type: `integer`): Maximum number of pages fetched in parallel. Kept low by default to reduce blocking. ## `proxyConfiguration` (type: `object`): Apify Proxy configuration. Datacenter proxies are recommended and used by default. ## Actor input object example ```json { "keywords": "python developer", "location": "", "distanceMiles": 10, "contractTypes": [], "workingHours": [], "workModel": [], "postedWithin": "any", "startUrls": [], "includeDetails": true, "maxItems": 20, "onlyNewJobs": false, "monitorKey": "default", "maxConcurrency": 3, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): No description ## `summary` (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 '