# Workable Public Jobs API (`zinin/workable-public-jobs-api`) Actor

Fetch published factual jobs from one to three buyer-known Workable public career accounts.

- **URL**: https://apify.com/zinin/workable-public-jobs-api.md
- **Developed by:** [Tim Zinin](https://apify.com/zinin) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 50.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.28 / 1,000 published job delivereds

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/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

## Workable Public Jobs API

Turn one to three Workable career accounts you already know into a clean,
deterministic Dataset of published job facts. Use the rows for recruiting-market
research, hiring monitoring, spreadsheet analysis, change detection, or a job
data pipeline—without maintaining a browser scraper.

The Actor uses Workable's documented public careers interface with
`details=false`. It does not discover accounts, request job descriptions, or
collect candidate data.

![Known account to validated published job facts](https://api.apify.com/v2/key-value-stores/u4bH4JeJnPmIMe4mr/records/workable-public-jobs-api-source-validation.webp)

### What you get

Every successful result is one complete factual published-job row in the run's
default Dataset. Each row includes:

- stable source and job identifiers;
- employer, title, department, employment type, and remote flag;
- visible structured locations, with hidden locations removed;
- published and created dates;
- official canonical job and application URLs;
- source counts, a factual-use notice, and a deterministic change fingerprint.

All requested accounts validate before any result is delivered. A malformed
second account therefore cannot leave you with a paid partial first account.
Rows are sorted deterministically, so repeated equivalent input is easy to diff.

### Who uses it

- Recruiters and talent analysts comparing known employer career pages.
- Market researchers monitoring role mix, remote hiring, or posting activity.
- Data teams feeding normalized public job facts into Sheets, SQL, or BI tools.
- Automation builders who need a strict Dataset contract and predictable errors.

This is not a global job search engine. You provide the exact accounts to read.

### Quick start

Run the public sample Task `fetch-workable-public-jobs` (Task ID
`3tGe4dw0RnkGzRd6U`). Its prefill reads the public Hugging Face career account
and returns up to 25 current jobs. The live number can change whenever that
employer publishes or closes roles.

For your own run, start with:

```json
{
  "schemaVersion": "1.0",
  "accounts": ["huggingface"],
  "titleContains": "",
  "locationContains": "",
  "remoteOnly": false,
  "maxResults": 25
}
```

An account may also use the exact canonical root form:
`https://apply.workable.com/huggingface/`.

### Input reference

| Field | Required | Meaning |
| --- | --- | --- |
| `schemaVersion` | Yes | Use the supported contract version `1.0`. |
| `accounts` | Yes | One to three exact lowercase slugs or canonical `apply.workable.com` career roots. |
| `titleContains` | Yes | Optional literal, case-insensitive title filter; use `""` for all titles. |
| `locationContains` | Yes | Optional literal filter across non-hidden country, country code, city, and region values. |
| `remoteOnly` | Yes | Keep only jobs Workable marks as telecommuting. |
| `maxResults` | Yes | Deliver at most 1–100 rows after all accounts validate. |

Filters are Unicode-normalized literal text, not regular expressions. Accounts
must be unique after normalization. The Actor rejects unknown keys and does not
silently repair missing fields.

### How it works

For each account, the Actor performs two sequential bounded requests:

1. It requests the exact documented public account route on `www.workable.com`
   with `details=false` and automatic redirects disabled.
2. It accepts only the byte-exact expected redirect to Workable's owned
   `apply.workable.com` public widget endpoint, then validates the complete JSON
   response before normalization.

Every source job must have the closed 19-field public shape, a valid date, and
matching official URLs derived from its ten-character shortcode. Identical
duplicates collapse; conflicting duplicates fail the whole batch. Descriptions,
top-level coarse locations, and nested locations marked hidden are discarded.

After all accounts pass, the Actor filters, sorts, caps, and atomically submits
one complete batch to the default Dataset.

### Output Dataset

![Analysis-ready factual job rows](https://api.apify.com/v2/key-value-stores/u4bH4JeJnPmIMe4mr/records/workable-public-jobs-api-dataset-rows.webp)

The `overview` Dataset view shows title, employer, department, remote status,
published date, official URL, and fingerprint. A complete fictional example is:

```json
{
  "schemaVersion": "1.0",
  "source": "workable-public-careers-api",
  "sourceName": "Workable",
  "sourceAccount": "example-account",
  "sourceApiUrl": "https://www.workable.com/api/accounts/example-account?details=false",
  "sourceDocumentationUrl": "https://help.workable.com/hc/en-us/articles/115012771647-Using-the-Workable-API-to-create-a-careers-page",
  "sourceJobId": "A1B2C3D4E5",
  "jobId": "workable:example-account:A1B2C3D4E5",
  "employerName": "Example Labs",
  "title": "Example research role",
  "code": "RES-1",
  "department": "Research",
  "employmentType": "Full-time",
  "remote": true,
  "visibleLocations": [],
  "education": null,
  "experience": "Mid-Senior level",
  "function": "Research",
  "industry": "Computer Software",
  "publishedOn": "2026-08-20",
  "createdOn": "2026-08-20",
  "canonicalUrl": "https://apply.workable.com/j/A1B2C3D4E5",
  "applicationUrl": "https://apply.workable.com/j/A1B2C3D4E5/apply",
  "sourceAccountPostingCount": 1,
  "sourceDuplicateCount": 0,
  "sourceAccountIndex": 1,
  "sourceComplete": true,
  "rightsNotice": "Official Workable public published-job facts only; descriptions, hidden locations, applications, candidate data and employer branding are excluded.",
  "changeFingerprint": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
}
```

The example is illustrative, not a current vacancy or employer claim.

### Field interpretation

- `remote` reproduces Workable's exact `telecommuting` boolean; it is not an
  inference from the title.
- `visibleLocations` contains only non-hidden structured locations. Empty does
  not mean the job is location-free.
- `publishedOn` and `createdOn` are source-provided calendar dates.
- `canonicalUrl` and `applicationUrl` are inert output values. The Actor never
  fetches them or submits an application.
- `changeFingerprint` hashes the normalized factual row while excluding source
  counters and account order, making factual changes easy to detect.
- An empty Dataset means the accounts validated but no row matched the filters.

### Pricing

The Actor uses Pay Per Event. `apify-actor-start` is charged once when a run
starts. The primary event `result-found` is charged once per complete row after
that row is delivered to the default Dataset.

| Tier | Actor start | Each delivered row |
| --- | ---: | ---: |
| FREE | $0.015000 | $0.001500 |
| BRONZE | $0.014250 | $0.001425 |
| SILVER | $0.013500 | $0.001350 |
| GOLD | $0.012750 | $0.001275 |
| PLATINUM | $0.012300 | $0.001230 |
| DIAMOND | $0.012000 | $0.001200 |

Cost is `start price + delivered rows × row price`. At the FREE tier, the
public Task's 25-row cap costs at most **$0.052500**. A maximum 100-row run costs
at most **$0.165000**. Zero results and validation failures do not charge
`result-found`; the automatic start charge still applies.

Before Dataset delivery, the runtime verifies that the run budget covers the
complete selected batch. It fails closed rather than silently trimming a paid
batch or reporting success when named charge settlement is uncertain.

### API and automation

Start the public sample Task through the Apify API:

```bash
curl -X POST \
  "https://api.apify.com/v2/actor-tasks/3tGe4dw0RnkGzRd6U/runs?token=YOUR_APIFY_TOKEN&waitForFinish=180"
```

For a custom Actor run, send the same Input JSON to Actor ID
`UyqEsc0B3rygCMNco`, then read `defaultDatasetId` from the terminal Run object:

```bash
curl \
  "https://api.apify.com/v2/datasets/DEFAULT_DATASET_ID/items?clean=1&format=json&token=YOUR_APIFY_TOKEN"
```

In Make, Zapier, or n8n, use one HTTP step to start the Task, wait for a terminal
Run status, and pass the default Dataset items URL downstream. Do not blindly
retry a timed-out client request: first check whether the original paid Run was
created and reached a terminal state.

### Source rights and data handling

Workable documents its public account endpoint as an alternative way to obtain
published jobs for a careers page in its
[API careers-page guide](https://help.workable.com/hc/en-us/articles/115012771647-Using-the-Workable-API-to-create-a-careers-page).
The Actor deliberately requests `details=false` and retains only bounded factual
fields.

You must be authorized to process the supplied accounts and remain responsible
for Workable's [terms](https://www.workable.com/terms), employer terms, and your
downstream use. This Actor grants no rights to employer content. It excludes
descriptions, hidden locations, application contents, candidate data, logos,
and employer branding.

The Actor stores successful normalized rows only in the run's default Dataset.
It does not create a history database, contact employers or candidates, or send
the job data to an AI service.

### Security

- Runs use Apify `LIMITED_PERMISSIONS` and need no Workable API key, cookie, or
  login.
- Input cannot supply an arbitrary hostname, port, path, query, or redirect.
- Requests use HTTPS, automatic redirects are disabled, and only two exact
  Workable-owned routes are allowed.
- The Actor uses no browser, proxy, language model, child Actor, or application
  endpoint.
- Source bodies use bounded size, fatal UTF-8 decoding, closed JSON shapes, and
  exact URL checks. Unsafe control text is rejected before Dataset delivery.

### Hard limits

| Limit | Value |
| --- | ---: |
| Accounts per run | 1–3 |
| Source requests | Up to 2 per account; maximum 6 |
| Delay between account starts | At least 1 second |
| Retries / automatic redirects | 0 / 0 |
| Timeout per request | 8 seconds |
| Canonical response size | 2,097,152 decoded bytes |
| Source jobs per account | 500 |
| Visible locations per job | 20 |
| Identical duplicates | 400 |
| Delivered rows | 1–100 |
| Compact bytes per row / batch | 16,384 / 1,900,000 |
| Actor memory / hard timeout | 128 MB / 150 seconds |

Source-interface drift, a 501st source job, a conflicting duplicate, an invalid
date or URL, an oversize response, or a second redirect fails the complete run.

### Troubleshooting

**Why did the run report `input_invalid`?**

Check that all six Input fields exist, account values use exact lowercase slugs
or canonical roots, accounts are unique, and `maxResults` is between 1 and 100.

**Why did the run report `source_redirect_invalid` or `source_shape_invalid`?**

Workable's public route or response no longer matched the bounded contract, or
the account slug was not a compatible public careers account. The Actor withheld
the complete batch rather than guessing.

**Why did the run report `buyer_budget_insufficient`?**

Raise `maxTotalChargeUsd` enough to cover the start event and every selected row,
or lower `maxResults`. No Dataset batch was opened for that rejected delivery.

**Why did the run report `delivery_charge_uncertain`?**

The named `result-found` settlement did not match the delivered row count. Check
the run and Dataset before retrying; the Actor deliberately does not compensate,
delete, or repeat a potentially paid write.

### FAQ

**Does it search all Workable employers?** No. Supply one to three accounts you
already know and are authorized to process.

**Does it include job descriptions?** No. The source is requested with
`details=false`, and description fields are excluded.

**Can it apply to a job?** No. Application URLs are inert output only.

**Can I monitor changes?** Yes. Store snapshots downstream and compare `jobId`
and `changeFingerprint`. The Actor itself stores no history.

**Are zero results billed?** No `result-found` event is charged for zero rows,
but the automatic Actor-start event still applies.

# Actor input Schema

## `schemaVersion` (type: `string`):

Use the current factual-job contract.

## `accounts` (type: `array`):

Enter 1–3 exact account slugs, such as huggingface, or canonical apply.workable.com career roots. The Actor does not discover accounts.

## `titleContains` (type: `string`):

Optionally keep jobs whose normalized title contains this literal text. This is not a regular expression.

## `locationContains` (type: `string`):

Optionally match literal text in non-hidden country, region, city, or country-code fields.

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

Keep only jobs Workable marks as telecommuting.

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

Return at most 1–100 complete rows after every requested account validates.

## Actor input object example

```json
{
  "schemaVersion": "1.0",
  "accounts": [
    "huggingface"
  ],
  "titleContains": "",
  "locationContains": "",
  "remoteOnly": false,
  "maxResults": 25
}
```

# Actor output Schema

## `jobs` (type: `string`):

Zero to 100 deterministic factual rows with official Workable URLs.

# 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 = {
    "schemaVersion": "1.0",
    "accounts": [
        "huggingface"
    ],
    "titleContains": "",
    "locationContains": "",
    "remoteOnly": false,
    "maxResults": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("zinin/workable-public-jobs-api").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 = {
    "schemaVersion": "1.0",
    "accounts": ["huggingface"],
    "titleContains": "",
    "locationContains": "",
    "remoteOnly": False,
    "maxResults": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("zinin/workable-public-jobs-api").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 '{
  "schemaVersion": "1.0",
  "accounts": [
    "huggingface"
  ],
  "titleContains": "",
  "locationContains": "",
  "remoteOnly": false,
  "maxResults": 25
}' |
apify call zinin/workable-public-jobs-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zinin/workable-public-jobs-api"
        }
    }
}

```

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/UyqEsc0B3rygCMNco/builds/6cYffI9bmjtEqXlF2/openapi.json