Totaljobs Jobs Scraper — UK Job Listings

What does Totaljobs Jobs Scraper do

Totaljobs Jobs Scraper collects publicly available job listings from totaljobs.com, a UK job board. It can be used to retrieve jobs matching a keyword and location, then save the listing data to an Apify dataset.

The actor follows Totaljobs search result pages and processes listings until the requested maximum number of jobs is reached or no more result pages are available. Each dataset item represents one job listing.

Collected records include the job title, employer, location, salary information when shown, job type, posting date, job URL, and the available listing description or summary. Some fields may be empty when the corresponding information is not displayed in the public listing.

Use the actor only for data that is publicly accessible on Totaljobs and in accordance with the website's applicable terms and policies.

Input

Configure the actor with the job search criteria and the number of listings to collect.

Field	Type	Description
keyword	string	Job title, skill, profession, or other search term to use on Totaljobs. For example, data analyst, nurse, or software engineer.
location	string	UK location to search in. This can be a city, region, county, or other location accepted by Totaljobs, such as London, Manchester, or Birmingham.
max_results	integer	Maximum number of job listings to collect. The actor stops when this limit is reached or when no additional listings are available.

Example input:

{
  "keyword": "software engineer",
  "location": "London",
  "max_results": 50
}

Use specific keywords and locations where possible. Search result availability depends on the listings currently returned by Totaljobs for the selected criteria.

Output example

The actor stores results in the default Apify dataset. A typical item can look like this:

{
  "job_title": "Software Engineer",
  "company_name": "Example Technology Ltd",
  "location": "London",
  "salary": "£45,000 - £60,000 per annum",
  "job_type": "Permanent",
  "posted_date": "Posted 2 days ago",
  "description": "We are looking for a Software Engineer to join our product development team and build scalable web applications.",
  "job_url": "https://www.totaljobs.com/job/software-engineer/example-technology-ltd-job123456789"
}

Output values reflect the content available on the corresponding public job listing at the time of collection. Salary, employment type, posting date, company name, and description fields may be unavailable for some listings.

Dataset records can be viewed in the Apify Console, exported as JSON, CSV, Excel, XML, or RSS, or consumed through the Apify API.

Use cases

• Build a list of current UK job opportunities for a role, skill, or location.
• Monitor new vacancies for recruitment, workforce planning, or job-market research.
• Compare advertised salaries, employers, locations, and contract types across searches.
• Feed job-listing data into internal dashboards, spreadsheets, or reporting workflows.
• Create alerts or automated pipelines for specific job keywords and UK locations.
• Collect public vacancy data for labour-market analysis and trend reporting.

Pricing

This actor uses pay-per-event pricing. Charges are based on the actor's configured event pricing for collected job listings.

The buyer also pays for their own Apify platform compute usage while the actor runs. Compute consumption depends on factors such as the number of requested results, available result pages, and the time required to retrieve and process listing pages.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.