# Workable Job Scraper — Workable Jobs API | $3/1K (`kenko404/workable-job-scraper`) Actor

Unofficial — not affiliated with Workable. Workable jobs API: give company names or apply.workable.com URLs and get every open role in one schema — title, department, function, location, employment type, apply link, posted date. One request per company.

- **URL**: https://apify.com/kenko404/workable-job-scraper.md
- **Developed by:** [KENKO](https://apify.com/kenko404) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 job listings

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/platform/actors/running/actors-in-store#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

## Workable Job Scraper — Workable Jobs API

Unofficial — not affiliated with Workable. Workable jobs API: give company names or apply.workable.com URLs and get every open role in one schema — title, department, function, location, employment type, apply link, posted date. One request per company.

### Input

```json
{
  "companies": [
    "persado",
    "https://apply.workable.com/blueground"
  ],
  "keywords": [
    "engineer",
    "developer",
    "manager"
  ],
  "maxJobsTotal": 200
}
```

Every filter is optional; `companies` is the only required field. `maxJobsTotal`
is what caps spend — you are billed per row delivered.

### Output

One row per open role, the same schema for every company:

| field | notes |
| --- | --- |
| `title`, `department`, `team` | as the board publishes them |
| `location`, `locations`, `country` | `locations` is every place the role is open; `location` is the first of them and `country` its ISO-2 code, resolved from the feed where the feed has one and otherwise **computed from the location text** |
| `workplaceType`, `isRemote` | the board's own field where it publishes one, otherwise **inferred from the location text** — remote if any published location reads remote; `null` when neither says, and `isRemote` follows `workplaceType`. It is a heuristic over free text and it is sometimes wrong: `"Remote, OR"` reads as remote work, not Oregon |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod` | the Workable feed this reads carries no pay field, so these and `salaryText` are always `null`. They are in the schema because the multi-ATS build fills them from boards that do publish pay |
| `postedAt` | ISO 8601, only where the board publishes a date. An open-ended age ("30+ days ago") is `null`, not a guess |
| `url`, `jobId`, `company`, `companySlug`, `provider` | |

Fields the board does not publish are `null` rather than guessed — except the ones
the table above marks as computed or inferred, which are derived from another field
on the same row and ship beside the field they came from.

### Pricing

$3 per 1,000 rows. You are charged for rows delivered — filters are applied
before anything is pushed, so a run that matches nothing costs nothing beyond
the platform's start event.

### Scope

Reads Workable's public job feed only, and only where the host's own
robots.txt permits it. No logins, no candidate data, no applications, no
personal data of any kind — job postings are the only thing it touches.

Need more than one ATS? The multi-ATS build detects Greenhouse, Lever, Ashby, Rippling, Workable and Personio from a bare company name, and reads Workday from a career-site URL.

***

Unofficial. Not affiliated with, endorsed by, or sponsored by Workable.

# Actor input Schema

## `companies` (type: `array`):

Company names, Workable board names, or board URLs. Accepts `persado`, `blueground`, or a full `https://apply.workable.com/...` URL. The board name is usually the company name in lower case.

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

Keep only roles whose title matches one of these. Whole-word matching, so `go` will not match `Google`. Leave empty for all roles.

## `excludeKeywords` (type: `array`):

Drop roles whose title or department matches any of these, e.g. `intern`, `contract`.

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

Keep roles whose location matches one of these, e.g. `London`, `Berlin`, `New York`.

## `countries` (type: `array`):

Keep roles in these countries, e.g. `US`, `GB`, `DE`. Resolved from the feed's own country field where present, otherwise from the location text.

## `departments` (type: `array`):

Keep roles in matching departments or teams, e.g. `Engineering`, `Sales`.

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

Keep only roles whose workplace type reads as remote — from the board’s own field where it publishes one, otherwise from the location text. A role open in several places counts if any one of them reads remote: the order a board lists its offices in says nothing about the role. Hybrid is excluded, and so is a role whose location says nothing, since it cannot be shown to be remote.

## `postedWithinDays` (type: `integer`):

Keep only roles published in the last N days. Roles with no publication date are excluded, since they cannot be shown to be recent. Leave empty for all.

## `searchDescriptions` (type: `boolean`):

Match `keywords` against the full job description as well as the title. Slower — descriptions must be fetched.

## `includeDescription` (type: `boolean`):

Add the full job description as readable plain text.

## `includeDescriptionHtml` (type: `boolean`):

Add the original HTML description. Large — expect 5-20 KB per role.

## `maxJobsPerCompany` (type: `integer`):

Cap on delivered roles per company, applied after your filters and newest-first — so with `keywords` set you get the N most recent matches, not the matches that happen to fall in the first N roles the board lists.

## `maxJobsTotal` (type: `integer`):

Hard ceiling on the run, so cost is bounded no matter how many roles the targets have.

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

Companies processed in parallel.

## Actor input object example

```json
{
  "companies": [
    "persado",
    "https://apply.workable.com/blueground"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "countries": [],
  "departments": [],
  "remoteOnly": false,
  "searchDescriptions": false,
  "includeDescription": false,
  "includeDescriptionHtml": false,
  "maxJobsPerCompany": 1000,
  "maxJobsTotal": 5000,
  "concurrency": 6
}
```

# 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 = {
    "companies": [
        "persado",
        "blueground",
        "skroutz"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kenko404/workable-job-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 = { "companies": [
        "persado",
        "blueground",
        "skroutz",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("kenko404/workable-job-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 '{
  "companies": [
    "persado",
    "blueground",
    "skroutz"
  ]
}' |
apify call kenko404/workable-job-scraper --silent --output-dataset

```

## MCP server setup

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