Totaljobs Scraper
Pricing
from $2.00 / 1,000 results
Scrape job listings from totaljobs.com — UK's largest job board. Salary data, full descriptions, company profiles, contact info, and incremental monitoring.
Direct Totaljobs search URLs to scrape. If provided, query and location are ignored.
Job search keyword (e.g., 'software-developer', 'data-analyst'). Not required when startUrls is provided.
Location filter (e.g., 'London', 'Manchester', 'Birmingham')
Sort order for results
Search radius around location in km (requires location)
Filter by contract/employment type
Filter by work schedule (full-time / part-time)
Filter by how to apply (e.g., INTERNAL = apply on company site only)
Skip sponsored/promoted listings. Filters out items where isSponsored=true.
Fetch each job's detail page for full description, ISO dates, salary, and geo coordinates. Slower but much richer data.
Controls how job detail pages are fetched. 'auto' (recommended) = actor chooses best method automatically. 'cheerio' = lightweight HTTP-only detail fetching. 'playwright' = browser-based detail fetching (heavier, for WAF-protected portals).
Format for job description text (requires Include Detail Pages)
Maximum number of job listings to return (0 = unlimited)
Maximum number of search result pages to scrape
full = return all jobs found. incremental = only return jobs not seen in previous runs (requires stateStoreName).
KV store name for incremental state. Use same name across scheduled runs. State is scoped per query+location+geo combination.
Named KV store for cross-run dedup. Same name across runs = only new jobs pushed.
Field used as unique key for dedup (default: jobKey)
Custom dataset name. Supports masks: {DATE} = YYYYMMDD, {TIME} = HHMMSS
Select subset of output fields. Use dot notation for nested: 'ceSalary.min'. If empty: all fields returned.
When true, each result contains only the 11 most essential fields: jobKey, title, company, location, url, portalUrl, datePosted, workFromHome, unifiedSalary, geo, and description. Use this in AI-agent and MCP workflows where token budgets matter.
Truncate the description field to this many characters, appending '...' if truncated. 0 means no truncation. Use in AI-agent workflows to control context window usage. Pairs well with compact mode.
Apify proxy configuration. Some portals require residential proxy (handled automatically). Your Apify plan must include proxy access.
{ "useApifyProxy": true}Maximum number of concurrent requests