# Workable Jobs API & Change Monitor (`istenotools/workable-jobs-api`) Actor

Extract normalized public Workable jobs, locations, departments, descriptions, salaries, and hiring changes.

- **URL**: https://apify.com/istenotools/workable-jobs-api.md
- **Developed by:** [Isteno Tools](https://apify.com/istenotools) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 workable jobs

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 API & Change Monitor

<p align="center">
  <img src="https://api.apify.com/v2/key-value-stores/28WlO7n0iHj8sJN95/records/actor-icon-workable-jobs-api.png" alt="Workable Jobs API icon" width="180">
</p>

> **Unofficial independent tool.** Not affiliated with or endorsed by Workable Technology
> Limited. The Workable name identifies compatible public career-page URLs only.

Extract detailed public Workable vacancies from one or many company accounts into clean datasets.
Run current snapshots or monitor meaningful job additions, updates, and removals without a
Workable login or customer API key.

### Best for

- Recruiting, job-search, and talent-intelligence products
- Company and competitor hiring trackers
- Hiring-signal lead generation
- Search indexes, alerts, and research datasets

### What you get

- Stable shortcode-based job identifiers and content fingerprints
- Company, title, department, employment type, dates, and application URL
- Primary and additional locations plus remote or on-site status
- Plain-text and HTML descriptions
- Public salary fields when the company supplies them
- Keyword, location, department, remote, and date filters
- Exact `maxItems` result control and failure-safe change monitoring

### Run it

```json
{
  "startUrls": [
    {
      "url": "https://apply.workable.com/clients-blackbox-inc/"
    }
  ],
  "maxItems": 1000,
  "mode": "snapshot",
  "includeDescription": true,
  "includeCompensation": true
}
```

Use the company's public Workable account career page, not a generic short job link. Add several
accounts to one run when you need a multi-company feed.

### Monitor changes

Set `"mode": "changes"` and schedule the same input. The first changes run emits current jobs as
`added`; later runs emit only meaningful content changes and removals from healthy accounts. A
temporary account failure retains its previous state.

Each default-dataset item is one normalized public Workable job or job-change event. Source
diagnostics and run totals are stored in the unpaid `OUTPUT` record.

### Cost and reliability

`maxItems` is a hard paid-result cap. The Actor uses Workable's public published-jobs account feed,
bounded response sizes, HTTPS-only network checks, timeouts, and retries. Apify displays the active
price and maximum total charge before the run.

### FAQ

**Does it need Workable credentials?** No. It reads currently published account jobs only.

**Can it process multiple companies?** Yes. Add multiple public account career-page URLs.

**Does it apply to jobs or access candidates?** No. It never submits applications or accesses
candidates, resumes, unpublished jobs, customer accounts, cookies, or API keys.

# Actor input Schema

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

Add one or more public Workable job-board URLs. HTTPS only.

## `sources` (type: `array`):

Optional advanced source objects with url, provider, companyName, and label.

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

Hard cap across all sources. One default-dataset item is one chargeable result.

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

Snapshot emits current jobs. Changes emits only added, updated, and removed jobs versus saved state.

## `stateStoreName` (type: `string`):

Optional stable key-value store name. If omitted, one is derived from sources and filters.

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

Emit jobs whose title contains at least one term. Leave empty for all titles.

## `excludeTitleKeywords` (type: `array`):

Drop jobs whose title contains any term.

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

Case-insensitive location substrings. Leave empty for every location.

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

Case-insensitive department substrings. Leave empty for every department.

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

Emit only records identified as remote or hybrid.

## `postedAfter` (type: `string`):

Optional ISO date in YYYY-MM-DD format.

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

Fetch and normalize descriptions when the source exposes them.

## `includeCompensation` (type: `boolean`):

Include public salary or compensation fields when the source exposes them.

## `maxConcurrency` (type: `integer`):

Bounded request concurrency across sources and detail pages.

## `requestTimeoutSecs` (type: `integer`):

Maximum time allowed for each source request.

## `retryCount` (type: `integer`):

Retries timeout, rate-limit, and server errors with backoff.

## `failOnSourceError` (type: `boolean`):

When disabled, healthy sources still return results and failed sources cannot create false removals.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://apply.workable.com/clients-blackbox-inc/"
    }
  ],
  "sources": [],
  "maxItems": 1000,
  "mode": "snapshot",
  "titleKeywords": [],
  "excludeTitleKeywords": [],
  "locations": [],
  "departments": [],
  "remoteOnly": false,
  "includeDescription": true,
  "includeCompensation": true,
  "maxConcurrency": 5,
  "requestTimeoutSecs": 30,
  "retryCount": 2,
  "failOnSourceError": false
}
```

# Actor output Schema

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

No description

## `summary` (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 = {
    "startUrls": [
        {
            "url": "https://apply.workable.com/clients-blackbox-inc/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("istenotools/workable-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 = { "startUrls": [{ "url": "https://apply.workable.com/clients-blackbox-inc/" }] }

# Run the Actor and wait for it to finish
run = client.actor("istenotools/workable-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 '{
  "startUrls": [
    {
      "url": "https://apply.workable.com/clients-blackbox-inc/"
    }
  ]
}' |
apify call istenotools/workable-jobs-api --silent --output-dataset

```

## MCP server setup

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