# Workable Jobs Scraper: Any Board, No API Key (`glitchbound/workable-jobs-scraper`) Actor

Every open role from any Workable job board, by company domain or account name. Titles, locations, departments, employment type and descriptions as clean JSON. No API key and no proxy: give it a domain and it finds the board.

- **URL**: https://apify.com/glitchbound/workable-jobs-scraper.md
- **Developed by:** [Daniel Meshulam](https://apify.com/glitchbound) (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 $1.50 / 1,000 job postings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Jobs Scraper: Any Board, No API Key

**Every open role from any Workable job board, by company domain or account name. Titles, locations, departments, employment type and descriptions as clean JSON. No API key and no proxy: give it a domain and it finds the board.**

### Features

- **Any workable board, from the URL or token you already have.** No API key, no
  login, no cookies, no proxy: this reads the public feed workable publishes so
  that job boards can index it.
- **Every posting, not the first page.** Paging is handled, including the
  places where workable reports a total it does not honour.
- **One row per job, as clean JSON**, with the same field names on every run.
- **Filters that cost you nothing.** Rows dropped by `titleKeywords`,
  `locationKeywords` or `remoteOnly` are never charged for.
- **Errors are per company.** One bad id does not end the run, and error rows
  are not charged.
- **Run it on a schedule** and the rows become a record of who started hiring
  and when.

### How to use it

1. Click **Try for free**, or add this Actor to a task.
2. Put one or more companies or board ids in the input. The
   example below is a real one.
3. Optionally narrow it with `titleKeywords`, `locationKeywords` or
   `remoteOnly`. Filtered rows are not billed.
4. Run it. Results appear in the dataset and can be exported as JSON, CSV,
   Excel or fetched from the API.

### Input

| Input | Type | Default | What it does |
|---|---|---|---|
| `companies` | array of strings | none | Company domains or names, one per line, e.g. zego.com |
| `boards` | array of strings | none | Board tokens to read, one per line, e.g. zego |
| `titleKeywords` | array of strings | none | Keep only roles whose title contains any of these, one per line, e.g. security or staff engineer |
| `locationKeywords` | array of strings | none | Keep only roles whose location contains any of these, one per line, e.g. London or Israel |
| `remoteOnly` | true or false | false | Keep only roles flagged remote by the ATS, or whose title or location says remote or anywhere |
| `includeDescription` | true or false | false | Fetch the description text as well |
| `maxResultsPerCompany` | number | `1000` | Ceiling on roles taken from any single board |
| `maxItems` | number | none | A hard ceiling on rows for the entire run, across every company |

```json
{
  "boards": ["zego"],
  "titleKeywords": ["engineer"],
  "remoteOnly": true
}
```

### Output

One row per job. This is the shape, with the fields workable actually publishes:

```json
{
  "title": "Senior Software Engineer",
  "location": "Berlin, Germany",
  "url": "https://boards.example.com/jobs/8130725",
  "jobId": "8130725",
  "postedAt": "2026-08-20T09:14:02Z",
  "departments": ["Engineering"],
  "description": "We are looking for...",
  "employmentType": "full-time",
  "isRemote": true,
  "company": "zego",
  "atsPlatform": "workable",
  "boardToken": "zego",
  "boardUrl": "https://boards.example.com/zego"
}
```

| Field | |
|---|---|
| `title` | the role as the company wrote it |
| `location` | as published, not normalised |
| `url` | the public posting, ready to open |
| `jobId` | the ATS's own id, stable across runs |
| `postedAt` | ISO 8601 UTC |
| `departments` | list |
| `description` | opt in, off by default because it is expensive at the source |
| `employmentType` | full time, contract, intern, as the source says |
| `isRemote` | true only for genuinely remote roles |
| `company` | what you asked for, echoed back |
| `atsPlatform` | which system it came from |
| `boardToken` | the board id used |
| `boardUrl` | the public board this came from |

### What people use this for

Hiring data is not really about jobs. It is the earliest public signal a
company gives that something changed, and it is why three different kinds of
buyer end up on the same dataset:

- **Sales and go-to-market.** A company that opens six engineering roles this
  month is a company with new budget. Job postings say which team is growing
  and in which city, weeks before anything shows up in a funding announcement.
- **Investors and market research.** Headcount by function, tracked over time,
  across a whole portfolio or a whole sector. Every row carries the company,
  the team and the date, so a weekly run is a time series.
- **Recruiting and talent.** Where a competitor is hiring, which roles they have been trying to fill for months, and how fast a team is growing. Workable does not publish pay, so no row here claims to know it.

Run it once for a snapshot. Run it on a schedule and the same rows become a
record of who started growing and when.

### You do not need the board token

```json
{ "companies": ["zego.com"] }
```

Every other workable Actor asks you for a board token, and there is no directory
mapping a company to its token. This one derives candidates from the domain and
**verifies each against the live API**, which is sound because workable answers
`404` for a board that does not exist and `200` for one that exists with nothing
open. A `200` is proof, not a maybe.

Measured across 30 companies, deriving and verifying resolved 90% against
50% for reading the careers page for a link. Stripe's careers page is a
JavaScript app that names no board at all, and it still resolves.

### What makes workable different

- Measured: `zego` 30 open roles. Workable skews to mid-size European companies, so the boards are smaller and there are many more of them.

- **An account that exists but has nothing open is common here**, and it is reported as exactly that. Workable answers 404 for an account that does not exist, so the two never get confused.

### Filters that cost you nothing

Filtered rows are **not charged**. Keywords match as plain text, so `c++` and
`node.js` mean exactly that rather than being read as regular expressions.

### Integrations and API

Every run writes to a dataset you can export as JSON, CSV or Excel, or read
from the Apify API. The Actor can be scheduled, called from another Actor, or
wired into Make, Zapier, Slack, Google Sheets and the rest of Apify's
integrations. It is also callable by an AI agent through the Apify MCP server,
and the output schema means the agent gets field descriptions rather than raw
JSON.

### Looking for an Indeed or Glassdoor API? There isn't one, and this is why you don't need it

Indeed has no public jobs API. Neither does Glassdoor, ZipRecruiter or LinkedIn
Jobs, and all four block you at the edge. Measured from an ordinary residential
address on 2026-08-01, with normal browser headers:

```
indeed.com/jobs          403      0 bytes
glassdoor.com/Job/...    403      0 bytes
ziprecruiter.com         403      0 bytes
upwork.com/nx/search     403      0 bytes
```

Zero bytes. Cloudflare rejects the request before it reaches an application, so
there is nothing to parse and no proxy budget that fixes it.

**But none of those four originate job data.** They aggregate it from company
career pages, and those pages run on systems like workable that publish a free,
keyless, public API, because companies want their openings indexed. That API
answered with real jobs from the same connection, in the same minute.

Going to the source is also fresher. An aggregator shows you its last crawl.
This shows you the board.

### FAQ

**Do I need an API key or an account with workable?**
No. This reads the public feed workable publishes for indexing. Nothing here is
behind a login, a paywall or a bot wall.

**What am I charged for?**
Rows returned. Rows removed by your filters are not charged, and neither are
error rows.

**Can I get only what changed since my last run?**
Run it on a schedule and compare `jobId`, which is stable across runs. For
change tracking with the work already done, see the sibling Actors below.

**A board came back empty. Is the company not hiring?**
An empty board is a real answer here and is reported as one.

### Notes

- The source is a public API that companies publish deliberately. Nothing here
  is behind a login, a paywall or a bot wall.
- An empty board is a real answer and is reported as one.
- Errors are per company. One bad token does not end the run, and error rows
  are not charged.

# Actor input Schema

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

Company domains or names, one per line, e.g. zego.com. The Actor derives the likely workable board token and verifies it against the live API before reading it, so you do not need to know the token.

## `boards` (type: `array`):

Board tokens to read, one per line, e.g. zego. A platform:token form is also accepted and the platform is ignored.

## `titleKeywords` (type: `array`):

Keep only roles whose title contains any of these, one per line, e.g. security or staff engineer. Matched as plain text, case-insensitive, so c++ and node.js mean exactly that. Filtered rows are not charged.

## `locationKeywords` (type: `array`):

Keep only roles whose location contains any of these, one per line, e.g. London or Israel. Filtered rows are not charged.

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

Keep only roles flagged remote by the ATS, or whose title or location says remote or anywhere.

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

Fetch the description text as well. Off by default because it is expensive at the source rather than here: Greenhouse returns 111 KB for a board without it and 1.97 MB with, an 18x difference for the same jobs. Rippling's board API returns no description at any setting.

## `maxResultsPerCompany` (type: `integer`):

Ceiling on roles taken from any single board.

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

A hard ceiling on rows for the entire run, across every company. The per-company limit above caps each one separately, so fifty companies at a thousand each is still fifty thousand rows; this caps the total. The run stops cleanly when it is reached and nothing beyond that point is fetched or charged. Leave empty for no ceiling.

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

Proxy settings. Every source here is a public API a company publishes on purpose so its openings get indexed, and none of them block datacenter addresses, so the default is fine.

## Actor input object example

```json
{
  "companies": [
    "zego.com"
  ],
  "remoteOnly": false,
  "includeDescription": false,
  "maxResultsPerCompany": 1000,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

All rows this run produced, as JSON.

# 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": [
        "zego.com"
    ],
    "maxResultsPerCompany": 1000
};

// Run the Actor and wait for it to finish
const run = await client.actor("glitchbound/workable-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 = {
    "companies": ["zego.com"],
    "maxResultsPerCompany": 1000,
}

# Run the Actor and wait for it to finish
run = client.actor("glitchbound/workable-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 '{
  "companies": [
    "zego.com"
  ],
  "maxResultsPerCompany": 1000
}' |
apify call glitchbound/workable-jobs-scraper --silent --output-dataset

```

## MCP server setup

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