# JobServe Jobs Scraper — UK Contract & Permanent Jobs (`yugenox/jobserve-jobs-scraper`) Actor

Scrape JobServe jobs by keyword and location in the UK, US, Canada, Australia and more: title, agency or employer, location, day rate or salary with min/max/currency, contract or permanent, start date, duration, posted and closing dates, full description. No login.

- **URL**: https://apify.com/yugenox/jobserve-jobs-scraper.md
- **Developed by:** [Yugenox Corp](https://apify.com/yugenox) (community)
- **Categories:** Jobs, Automation
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## JobServe Jobs Scraper: UK contract and permanent jobs

Scrape **JobServe**, the job board for IT, engineering and professional contract and permanent roles, by keyword and location on the UK, US, Canadian, Australian, New Zealand, German, French, Swiss and UAE sites. Every job comes with the **title, the recruitment agency or employer, location, day rate or salary (with min, max, currency and period), contract or permanent, start date, duration, posted date and the agency's reference**. With full job details on (the default) you also get the **full description, closing date, city, region, coordinates and the advertiser's company profile**. No login, no cookies, no JobServe account.

### What you get

| | |
|---|---|
| **Job** | Title, job URL, short permalink, apply link, posted date, closing date, JobServe industry |
| **Advertiser** | Agency or employer name, its type (Employment Business, Employment Agency or Company), logo, company profile |
| **Location** | Location as shown, city, region, country, latitude and longitude |
| **Rate / salary** | As shown (e.g. "£650-675/day, inside IR35"), plus parsed **min, max, currency and period** (hour, day, year) |
| **Contract** | Contract, Permanent, Contract/Permanent, Full Time…; start date ("ASAP"), duration ("6 months") |
| **Description** | The full description as text and HTML, and the listing extract |
| **Reference** | The advertiser's own job reference and JobServe's posting number |

### How to use it

1. Enter one or more **keywords**, e.g. `python`, `SC cleared`, `project manager`. JobServe's own syntax works: `Python and AWS`, `"Data Engineer"`.
2. Optionally enter a **location**, e.g. `London`, `Manchester`, `Edinburgh` (add more under **More locations**). JobServe searches 50 miles around it. Leave it empty to search the whole country.
3. Pick the **JobServe country site** (United Kingdom by default), set **Max jobs**, and run.

Each keyword is searched in each location. **Max jobs** is the total for the run, shared fairly between your searches.

#### Input examples

Python contracts in London, last 3 days:

```json
{
  "keywords": ["python"],
  "location": "London",
  "jobType": ["Contract"],
  "postedWithin": "3",
  "maxItems": 100
}
```

Several searches at once, listing data only (cheaper and faster):

```json
{
  "keywords": ["SC cleared", "DV cleared"],
  "locations": ["Bristol", "Manchester", "Cheltenham"],
  "includeDetails": false,
  "maxItems": 500
}
```

Java jobs on the US site:

```json
{
  "keywords": ["java"],
  "country": "us",
  "maxItems": 50
}
```

You can also paste JobServe search URLs (`JobListing.aspx?q=…&lq=…`, `search-jobs-in-…` pages) or job URLs into **JobServe URLs**.

### Output example

```json
{
  "site": "jobserve",
  "jobId": "0ED087E596AFFB3AE1",
  "title": "Ruby on Rails Developer/Solutions Lead (Back End) - Remote",
  "company": "SmartSourcing Ltd",
  "companyType": "Employment Business",
  "location": "Remote, London as-hoc, UK",
  "city": "London",
  "region": "England",
  "country": "United Kingdom",
  "latitude": 51.512,
  "longitude": -0.065,
  "isRemote": true,
  "jobType": "Contract",
  "employmentTypes": ["Contract"],
  "industry": "IT",
  "salaryText": "£650-675/day, inside IR35",
  "salaryMin": 650,
  "salaryMax": 675,
  "salaryCurrency": "GBP",
  "salaryPeriod": "day",
  "startDate": "ASAP",
  "duration": "6 months",
  "postedDate": "2026-09-29T11:38:00.000Z",
  "expiresDate": "2026-10-13T11:38:00.000Z",
  "description": "Back End Ruby on Rails Developer/Solutions Lead (SC Cleared Preferred)\n\n£650-675 per day (Inside IR35) | 6 Month Contract | Remote with occasional London meetings …",
  "reference": "JSSS/KK-ROR849",
  "url": "https://www.jobserve.com/gb/en/search-jobs-in-London,-London,-United-Kingdom/RUBY-ON-RAILS-DEVELOPER-SOLUTIONS-LEAD-BACK-END-REMOTE-0ED087E596AFFB3AE1/",
  "permalink": "https://www.jobserve.com/g9BCH",
  "applyUrl": "https://www.jobserve.com/gb/en/W0ED087E596AFFB3AE1.jsap",
  "countrySite": "gb",
  "searchKeyword": null,
  "searchLocation": "London",
  "position": 1,
  "detailsFetched": true,
  "scrapedAt": "2026-10-01T22:18:27.212Z"
}
```

Every row has the same columns; a value the job doesn't state is `null`. `description`, `city`, `region`, coordinates, `expiresDate` and `companyDescription` are filled when **Include full job details** is on.

### Use cases

- **Contractor rates**: track day rates for a skill or clearance level by city, inside and outside IR35.
- **Recruitment market intelligence**: see which agencies are hiring for which roles, and how many.
- **Job alerts**: schedule a daily run with **Posted within: Last 24 hours**.
- **Lead lists for staffing firms**: find the agencies and employers advertising in your niche.
- **Job aggregation**: feed JobServe jobs into your own site, newsletter or ATS.

### FAQ

**Do I need a JobServe account, cookies or a login?** No. The scraper reads the same public job pages any visitor sees. It never logs in and needs nothing from you except a search.

**How many jobs can I get?** JobServe lists jobs from the last 7 days. Set **Max jobs** to 0 to get everything your searches find (up to 10,000 per search). A London search can return over 15,000 jobs, so use keywords to narrow it.

**How fast is it?** About 20 jobs every 2–3 seconds with listing data only, and about 2 jobs a second with full details.

**How do the filters work?** JobServe's own refinements need its interactive page, so the scraper applies **Job type**, **Posted within** and **Remote jobs only** to each job itself. Jobs that don't match are skipped and never charged. If 5 result pages in a row (100 jobs) have no match, that search stops and the status message says so.

**Why are there no jobs for my location?** JobServe returns nothing for a place it doesn't know. Try a town or city name, e.g. `Reading` or `Glasgow`. Only the search is charged, not jobs.

**What about the recruiter's name and phone number?** Job pages show the consultant's name and phone number. The scraper never collects them. Personal e-mail addresses and phone numbers inside descriptions are replaced with `[email removed]` / `[phone removed]`. You get the agency or company name, which is business information.

**Which proxy should I use?** Keep the default (Apify Proxy, datacenter). It comes with every Apify plan, including the free one. If JobServe refuses datacenter IPs for a while, the run switches to residential proxies when your account has them, and carries on without them when it doesn't.

**What does a run cost?** You pay per job saved, a small amount per job with full details, per search, and a small fee per run. See the Pricing tab. Jobs that are filtered out are never charged.

**Is it legal to scrape JobServe?** This Actor only collects publicly available data: job postings that anyone can see on JobServe without an account, such as the job title, advertiser, location, rate and description. Collecting publicly available data is generally legal, but you're responsible for how you use it. Job postings describe roles, not people, and the scraper leaves out the consultant contact details shown on job pages and masks personal e-mail addresses and phone numbers in descriptions. You must follow privacy laws such as GDPR, PIPEDA and CCPA, as well as JobServe's terms. If you're unsure, check with a lawyer. More on this: [Is web scraping legal?](https://blog.apify.com/is-web-scraping-legal/)

**Does it access any private data?** No. Everything comes from pages JobServe shows to any visitor without logging in. It never logs in, never applies to jobs, never opens CVs or candidate accounts, and follows JobServe's robots.txt.

This Actor is not affiliated with, endorsed by or sponsored by JobServe.

# Actor input Schema

## `keywords` (type: `array`):

Job titles or skills to search on JobServe, e.g. "python", "SC cleared", "project manager". Each keyword is searched separately (and in each location). JobServe's own syntax works too: "Python and AWS", ""Data Engineer"".

## `location` (type: `string`):

A town, city or region, e.g. "London", "Manchester", "Edinburgh". JobServe searches 50 miles around it. Leave empty to search the whole country. A place JobServe doesn't know returns no jobs (and costs nothing per job).

## `locations` (type: `array`):

Run the same keywords in several places, e.g. "Bristol", "Leeds".

## `country` (type: `string`):

Which JobServe site to search. Most jobs are on the UK site.

## `maxItems` (type: `integer`):

Maximum number of jobs for the whole run, shared fairly between your searches (a search that finds fewer leaves its share to the others). 0 = everything.

## `includeDetails` (type: `boolean`):

Open every job page for the full description (text and HTML), structured salary, closing date, city/region and coordinates, and the advertiser's company description. Off = listing data only (title, advertiser, location, rate, type, dates, a ~500-character extract), cheaper and faster.

## `startUrls` (type: `array`):

Optional: JobServe search URLs (JobListing.aspx?q=…\&lq=…, "search-jobs-in-…" pages) or job URLs (they end in the 18-character job ID, e.g. …-0ED087E596AFFB3AE1/).

## `jobType` (type: `array`):

Only these job types. "Contract/Permanent" jobs match both Contract and Permanent; on the US site "Full Time" counts as Permanent. Empty = all.

## `postedWithin` (type: `string`):

Only jobs posted in this period. JobServe itself lists jobs from the last 7 days.

## `remoteOnly` (type: `boolean`):

Only jobs whose location or title mentions remote work.

## `proxyConfiguration` (type: `object`):

Apify Proxy (datacenter) is the default and comes with every Apify plan. If JobServe refuses datacenter IPs for a while, the run switches to residential proxies when your account has them.

## Actor input object example

```json
{
  "keywords": [
    "python"
  ],
  "location": "London",
  "country": "gb",
  "maxItems": 20,
  "includeDetails": true,
  "postedWithin": "any",
  "remoteOnly": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All scraped jobs.

## `run` (type: `string`):

Status and statistics for this run.

## `report` (type: `string`):

RUN_REPORT: how the run ended, counts, requests and proxy use.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "python"
    ],
    "location": "London",
    "maxItems": 20,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("yugenox/jobserve-jobs-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": ["python"],
    "location": "London",
    "maxItems": 20,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("yugenox/jobserve-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "python"
  ],
  "location": "London",
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call yugenox/jobserve-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,yugenox/jobserve-jobs-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/129wGVsnZiH8WuuYm/builds/yCyiH6u1iRnP8IJWA/openapi.json