# Workable Jobs Search Scraper (`jobsapi/workable-jobs-search-scraper`) Actor

Scrape job listings from Workable, a modern recruitment platform. Extract job titles, companies, locations, descriptions, and employment types from organizations using Workable ATS.

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

## Pricing

from $2.99 / 1,000 workable career roles

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?

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

## Workable Public Jobs Search Scraper

This Actor reads public job search results and detail pages on `jobs.workable.com`. It emits complete, detail-verified records with more than 20 populated source facts per record when the posting exposes them. Search cards are enriched from the matching public detail page and its JobPosting data. Missing optional facts are omitted.

### Inputs

- `search` searches with `query` and returns up to `maxItems` complete jobs.
- `single` verifies one exact `jobUrl`.
- `multiple` verifies exact `jobUrls`, `urls`, or `startUrls`.
- `maxRequests` sets a hard request ceiling.

Direct URLs must be HTTPS `https://jobs.workable.com/view/<id>/<slug>` URLs. The Actor verifies the page ID, canonical URL, structured JobPosting URL when present, title, company, and a readable description. It emits `applyUrl` only when the page exposes a real application link.

The job dataset includes listing and detail facts such as Workable job identifiers, title, employer, logo and profile links, employer description and website, workplace type, location and structured address, department, employment labels, posted date, JobPosting location and applicant-location fields, description text/HTML and bullets, requirements, benefits, public application link, and canonical URLs. The dataset schema is strict; the validator checks field types, populated source facts, and the greater-than-20-fact threshold.

See [sample output](examples/sample-output.json), copied from the locally validated public Onramp Lab record.

### Access policy

Requests use ordinary direct Chrome navigation with one request at a time, zero retries, no proxy or session cookies, and fingerprint injection disabled. The Actor sends no custom headers or user agent. If a public navigation returns HTTP 401, 403, 429, or 451, redirects to a login boundary, or displays a source-authored access challenge, the Actor stops, discards all buffered job rows, and stores `SKIPPED` with its diagnostic and request receipts. Network and browser transport failures are stored as `DEFERRED`; they are not retried or worked around.

`OUTPUT_SUMMARY`, `SOURCE_METADATA`, `RUN_DIAGNOSTICS`, and `REQUEST_RECEIPTS` are stored separately from the job-only dataset. A successful local run is not evidence of an Apify Cloud run.

### Local validation

```text
npm ci --ignore-scripts
npm test
npm run lint
apify validate-schema .actor/input_schema.json
apify validate-schema .actor/dataset_schema.json
apify validate-schema .actor/key_value_store_schema.json
apify validate-schema .actor/output_schema.json
```

Before running the Actor, confirm the selected storage path does not exist and inspect any existing `apify_storage` directory. Preserve existing data. On Windows, use a fresh relative storage path and `--resurrect`:

```powershell
$store = 'storage-workable-validation'
if (Test-Path $store) { throw "Choose a fresh path: $store already exists" }
if (Test-Path 'apify_storage') { throw 'Preserve or isolate the existing legacy apify_storage directory first' }
$env:APIFY_LOCAL_STORAGE_DIR = $store
apify run --input-file ./INPUT.json --resurrect
node validate-datasets.js $store
```

The isolated dataset validator reconciles output rows with `OUTPUT_SUMMARY`, checks strict schema keys and types, verifies unique job IDs and URLs, validates request receipts, readable descriptions, and the populated source-fact threshold. Keep the resulting local storage as validation evidence. Do not use `--purge` or Cloud push/run for this local workflow.

# Changelog

This Actor's version history is a separate document: https://apify.com/jobsapi/workable-jobs-search-scraper/changelog.md

# Actor input Schema

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

Search discovers jobs; single and multiple accept exact public Workable detail URLs.

## `query` (type: `string`):

Public Workable search phrase used in search mode.

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

Exact number of detail-verified jobs required in search mode.

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

Hard ceiling for search and detail requests in one run.

## `jobUrl` (type: `string`):

Exact HTTPS jobs.workable.com/view/<id>/<slug> URL.

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

Exact public Workable detail URLs for multiple mode.

## `urls` (type: `array`):

Optional alias for jobUrls, accepted only in single or multiple mode.

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

Optional Apify-style list of objects containing exact public Workable detail URLs.

## Actor input object example

```json
{
  "mode": "search",
  "query": "developer",
  "maxItems": 3,
  "maxRequests": 12
}
```

# Actor output Schema

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

No description

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

No description

## `sourceMetadata` (type: `string`):

No description

## `diagnostics` (type: `string`):

No description

## `requestReceipts` (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/workable-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/workable-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/workable-jobs-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobsapi/workable-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/hPNhIHvE9NDuv42j7/builds/1kJIKKzVAd6bvwXB6/openapi.json