# JobServe Jobs Scraper (`jobsapi/jobserve-jobs-search-scraper`) Actor

Cloud-ready scraper for public JobServe listings with bounded requests, Apify Proxy support, verified detail enrichment and normalized job, recruiter, salary, date and application data.

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

## Pricing

from $2.99 / 1,000 jobserve job records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does JobServe Jobs Scraper do?

JobServe Jobs Scraper searches public listings on [JobServe](https://www.jobserve.com/) and returns normalized job and recruiter data. It is an unofficial JobServe API alternative for recruitment research, job-board monitoring and integrations; it does not require a JobServe account. It supports `search`, `single`, and `multiple` modes and enriches verified search cards from public `.jsjob` detail pages.

### Why use this scraper?

Search by keyword, market, country, location, remote preference, industry, posting date and job type. The Actor preserves the useful fields on each listing, including title, salary or day rate, contract type, description, reference, recruiter and application permalink. Schedule recurring searches on Apify, use the API, or connect the dataset to downstream tools.

### What data can it extract?

| Field | Type | Description |
| --- | --- | --- |
| title, reference | string | Listing identity |
| location, locationSalary, jobType | string | Work location and engagement |
| description, descriptionHtml | string | Public role details |
| company, recruiter, contact | string | Advertiser and recruiter information |
| postedDate, startDate | string | ISO dates when the source provides parseable dates |
| rate, visaRequirements | string | Compensation and visa text |
| url, jobUrl, canonicalUrl | string | Absolute JobServe listing URLs |
| applyUrl, applicationUrl, applicationProvider | string | Public application target metadata |
| responseReceipts, contentHash, fieldCoverage, dataQuality | object/string | Sanitized provenance and quality metadata |

### How to scrape JobServe

1. Set `mode` to `search` for discovery, or provide `jobUrls` for `single`/`multiple` direct detail retrieval.
2. Set keywords and select a JobServe market for search mode.
3. Add optional location and filter values, or provide an existing public search URL.
4. Choose maxResults and start the Actor.
5. Export JSON, CSV, Excel or connect through the Apify API.

### Pricing

Runs consume the normal Apify compute and network allocation. Start with a small maxResults value when tuning filters, then schedule larger searches as needed.

### Input and output

See the input tab for all filter fields. JobServe may vary the available filters by country. Output records are rectangular: fields unavailable on a listing are omitted rather than filled with placeholders. UI/navigation cards are discarded, and direct application URLs are reported but never followed or submitted. You can download the dataset in JSON, HTML, CSV or Excel.

### Cloud execution and quality contract

The Actor is cloud-supported and uses Apify Proxy when credentials are available. maxRequests bounds all network attempts, maxResponseBytes limits page size, and every accepted job has a stable recordId, a SHA-256 contentHash, response receipts and complete-record status. The default dataset contains only complete job records; request receipts, run health, summary metadata and access diagnostics are written to the named key-value-store records linked from the output.

### Troubleshooting and responsible use

If no records are returned, try a less restrictive keyword or an existing search URL that opens without an account. Public listings can change or disappear. Use only data you are authorized to process, respect JobServe terms and privacy law, and avoid collecting personal contact information without a legitimate purpose. Report problems in the Issues tab.

# Actor input Schema

## `mode` (type: `string`):

Search public JobServe results or fetch one/multiple direct public detail pages.

## `jobUrls` (type: `array`):

Public JobServe detail URLs used by single or multiple mode.

## `websiteCountry` (type: `string`):

JobServe market to search, for example United Kingdom or United States.

## `searchCountries` (type: `array`):

Optional country filters supported by the selected JobServe market.

## `keywords` (type: `string`):

Job title, skill or phrase to search for.

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

Optional city, region or comma-separated locations.

## `distance` (type: `string`):

Optional radius label such as Within 50 miles.

## `remoteWorking` (type: `boolean`):

Restrict results to remote-work listings when supported.

## `industries` (type: `array`):

Optional JobServe industry filters.

## `datePosted` (type: `string`):

Optional recency filter such as Within 3 days.

## `jobType` (type: `string`):

Engagement filter such as Permanent or Contract.

## `jobTitle` (type: `string`):

Optional exact title filter.

## `salaryRate` (type: `array`):

Optional salary or day-rate filters.

## `visaEligibility` (type: `array`):

Optional visa eligibility filters.

## `category` (type: `array`):

Optional listing categories.

## `advertisedBy` (type: `string`):

Optional advertiser filter.

## `searchUrl` (type: `string`):

Optional public JobServe URL. When supplied, filter fields are not used to construct a URL.

## `maxResults` (type: `integer`):

Maximum listings to return.

## `timeoutSeconds` (type: `integer`):

Maximum seconds for each public page request.

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

Enrich search cards with their public JobServe detail pages.

## `concurrency` (type: `integer`):

Maximum concurrent public detail requests.

## `maxRetries` (type: `integer`):

Retries for transient public HTTP failures.

## `requestDelayMs` (type: `integer`):

Polite delay before each public request.

## `maxRequests` (type: `integer`):

Hard upper bound on all search and detail network requests, including retries.

## `maxResponseBytes` (type: `integer`):

Reject public pages larger than this many bytes.

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

Apify Proxy configuration applied to public JobServe requests. The default uses Apify Proxy when available.

## Actor input object example

```json
{
  "mode": "search",
  "websiteCountry": "United Kingdom",
  "keywords": "Accountant",
  "remoteWorking": false,
  "jobType": "Any",
  "maxResults": 100,
  "timeoutSeconds": 30,
  "includeDetails": true,
  "concurrency": 4,
  "maxRetries": 2,
  "requestDelayMs": 50,
  "maxRequests": 120,
  "maxResponseBytes": 10485760,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `health` (type: `string`):

No description

## `requests` (type: `string`):

No description

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

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jobsapi/jobserve-jobs-search-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("jobsapi/jobserve-jobs-search-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 '{}' |
apify call jobsapi/jobserve-jobs-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobsapi/jobserve-jobs-search-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/WsADf09hmJZpPc1DZ/builds/xRq3WwrJ2rDrEIZ8F/openapi.json