# Workable Jobs Scraper (`fetch_cat/workable-jobs-scraper`) Actor

Scrape public Workable career boards by company slug or URL. Export job titles, locations, departments, workplace type, remote flags, dates, URLs, and optional descriptions.

- **URL**: https://apify.com/fetch_cat/workable-jobs-scraper.md
- **Developed by:** [Fetch Cat](https://apify.com/fetch_cat) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 4 total users, 1 monthly users, 96.4% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.02 / 1,000 job results

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?

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

Export public Workable company-board jobs and supported individual job pages with source identifiers, locations, departments, workplace labels, dates and application links. Optional detail collection can include description, requirements and benefits HTML. Public board records support separate recruiting and hiring research rather than access to private applicant systems or an automated application service.

### Quick start

Begin with a known board such as Recurly and a small shared cap, then inspect source links and filters before expanding a company list. The existing query example is:

```json
{
  "companySlugs": ["recurly"],
  "query": "engineer",
  "maxItems": 20,
  "includeDescription": false
}
```

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

https://youtu.be/1OW8gOqlZbY?t=25

### Ready-to-run examples

- [Export current Recurly Workable jobs](https://apify.com/fetch_cat/workable-jobs-scraper/examples/scrape-recurly-workable-jobs) — Start with the company board and its available public job metadata.
- [Find Recurly engineering jobs](https://apify.com/fetch_cat/workable-jobs-scraper/examples/scrape-recurly-engineering-jobs) — Try a title and description keyword filter.
- [Include software-engineer descriptions](https://apify.com/fetch_cat/workable-jobs-scraper/examples/scrape-recurly-software-engineer-jobs-with-descriptions) — Collect available public job descriptions for closer review.
- [View all public examples](https://apify.com/fetch_cat/workable-jobs-scraper/examples)

### What you get

One saved public job row with board or direct-posting identity, sourceType, sourceUrl and available employment metadata. Numeric company-board IDs and Jobs by Workable tokens can differ, so sourceJobId preserves a stable string form. Descriptions, requirements and benefits remain optional and can be unavailable on a public source.

### Who is it for?

- **Recruiting researchers** inspecting known companies' public roles and employment labels.
- **Sales and market analysts** reviewing bounded hiring signals by department or region.
- **Job-data teams** joining source-identified listings in their own datasets.
- **Automation developers** exporting public board records into existing reports or review workflows.

### How you can use the data

- **Review Recurly engineering candidates.** Use the existing recurly slug and engineer query, retaining title, departments and workplace context. Local filters match exposed source fields rather than guaranteeing all company roles or applicant eligibility.
- **Inspect optional public descriptions.** Enable descriptions for a small shortlist when you need requirements or benefits HTML. A detail request is needed only when the company feed omits the text, and missing fields remain distinct from a fully described job.
- **Retrieve a known current posting.** Use the existing Jobs by Workable URL template below and keep sourceType, sourceJobId and sourceUrl. Its identifier shape differs from company-board IDs, and a closed or unsupported link can produce a source warning rather than a fabricated job.
- **Maintain your own board observations.** Store IDs, job URLs, workplace labels and publication dates before comparing separate exports. Unavailable boards and pending work need their run diagnostics retained, while schedules, notifications and hiring conclusions are downstream work.

### Input settings

| Setting | JSON key | Type / default | Description |
| --- | --- | --- | --- |
| Company slugs | `companySlugs` | array, form example `["recurly"]` | Workable company slugs from apply.workable.com URLs, for example `recurly` from `https://apply.workable.com/recurly/`. |
| Start URLs | `startUrls` | array, form example `[{"url":"https://apply.workable.com/recurly/"}]` | Public company boards or individual job URLs from `apply.workable.com` and `jobs.workable.com/view`. |
| Search query | `query` | string | Optional case-insensitive keyword filter applied to each title and description. |
| Locations | `locations` | array | Optional location filters, for example `London`, `United States`, or `Remote`. |
| Departments | `departments` | array | Optional department filters, for example `Engineering`, `Product`, or `Sales`. |
| Work types | `workTypes` | array | Optional Workable job type or workplace filters, for example `full`, `hybrid`, or `remote`. |
| Remote only | `remote` | boolean | Set to true to keep only jobs marked as remote, or false to keep only non-remote jobs. Leave empty for both. |
| Maximum jobs | `maxItems` | integer, default `20` | Maximum number of job listings to save across all company boards. |
| Include job descriptions | `includeDescription` | boolean, default `false` | Include public description, requirements, and benefits HTML. An individual detail request is made only when the company feed does not contain it. |
| Maximum run time | `maxRunSeconds` | integer, 60–270, default `270` | Safety budget including shutdown time. Already saved rows remain available if the run reaches its limit. |

Provide at least one source in either list. API calls do not inherit the form's example company. Runs accept up to 100 unique sources combined, and connections are handled automatically, so no proxy settings are needed. See each input's help for validation and safety limits.

#### Existing board URL input

```json
{
  "startUrls": [
    {
      "url": "https://apply.workable.com/recurly/"
    }
  ],
  "maxItems": 20
}
```

#### Existing individual job URL input

```json
{
  "startUrls": [
    {
      "url": "https://jobs.workable.com/view/dHWbxHXmt9g9mfaewTC2eX/full-stack-engineer"
    }
  ],
  "maxItems": 1,
  "includeDescription": true
}
```

### Output data

The existing illustrative Recurly row shows shape rather than a current posting lookup:

```json
{
  "companySlug": "recurly",
  "jobTitle": "Senior Software Engineer, Platform Engineering",
  "location": "Broomfield, Colorado, United States",
  "departments": [],
  "workplace": "hybrid",
  "remote": false,
  "publishedAt": "2026-08-01",
  "url": "https://apply.workable.com/recurly/j/55F8A87FA4/",
  "jobId": 5999351,
  "sourceJobId": "5999351",
  "shortcode": "55F8A87FA4",
  "city": "Broomfield",
  "region": "Colorado",
  "country": "United States",
  "workType": "Full-time",
  "applicationUrl": "https://apply.workable.com/recurly/j/55F8A87FA4/apply/",
  "sourceType": "company_board",
  "descriptionHtml": null
}
```

| JSON key | Label | Type | Description |
| --- | --- | --- | --- |
| `companySlug` | Company slug | string | Company-board slug or normalized company name for a direct Jobs by Workable posting. |
| `companyName` | Company name | string / null | Company display name when available. |
| `jobTitle` | Job title | string | Public posting title. |
| `location` | Location | string / null | Combined city, region, and country. |
| `departments` | Departments | array | Employer-supplied departments or teams. |
| `workplace` | Workplace | string / null | Remote, hybrid, or on-site workplace mode. |
| `remote` | Remote | boolean | Whether Workable marks the role as fully remote. |
| `publishedAt` | Published | string / null | Workable publication timestamp or date. |
| `url` | Job URL | string | Canonical public job page. |
| `jobId` | Job ID | integer / string | Numeric company-board ID or UUID for a Jobs by Workable posting. |
| `sourceJobId` | Source job ID | string | Stable string representation of the source identifier. |
| `shortcode` | Shortcode | string | Company-board shortcode or Jobs by Workable token. |
| `city` | City | string / null | Posting city when supplied. |
| `region` | Region | string / null | Posting state or region when supplied. |
| `country` | Country | string / null | Posting country name. |
| `countryCode` | Country code | string / null | Country code when supplied by the source. |
| `workType` | Work type | string / null | Source employment or job type. |
| `applicationUrl` | Application URL | string | Public application link, or the job page if no separate link is available. |
| `employmentType` | Employment type | string / null | Source employment label, such as full-time. |
| `language` | Language | string / null | Posting language when supplied. |
| `descriptionHtml` | Description HTML | string / null | Public description, included only when requested. |
| `requirementsHtml` | Requirements HTML | string / null | Public requirements, included only when requested. |
| `benefitsHtml` | Benefits HTML | string / null | Public benefits, included only when requested. |
| `sourceType` | Source type | string | `company_board`, `company_job`, or `jobs_workable_job`. |
| `sourceUrl` | Source URL | string / null | Public Workable URL used for the result. |
| `raw` | Raw source record | object | Normalized source data and additional employer-supplied fields. |

#### Download your results

Open your run's dataset, choose **Export** and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See [Apify's download and export guide](https://docs.apify.com/storage/dataset#apify-console) for the available formats and field options.

### Pricing

The `start` event is charged once after input validation. A started run can incur this charge even when no jobs are available.

The `item` event applies to each saved job row. Unavailable sources and empty searches do not create job-result charges. The Actor stops collecting more jobs when the result-charge budget is exhausted. Keep the shared cap small when checking a board or filter.

See the [live Pricing tab](https://apify.com/fetch_cat/workable-jobs-scraper/pricing) for current rates and discounts. Platform usage can also apply.

### Tips for best results

- **Use company slugs for clean inputs**: they are shorter and less fragile than copied URLs.
- **Start with a small `maxItems`**: confirm the board and filters before scheduling large runs.
- **Request descriptions only when needed**: larger HTML fields are useful for detailed role reviews but make results heavier.
- **Leave filters empty for full board exports**: filters can exclude roles if company naming differs.
- **Check board availability**: not every company uses Workable or keeps old postings public.
- **Use multiple boards safely**: an unavailable board is recorded in the run summary while the Actor continues with other valid boards.

### Limits and caveats

- The Actor extracts public Workable career-board data. It does not access private applicant systems.
- Filters are applied locally to the public job title, description, location, department, employment type, and workplace fields that Workable exposes.
- Descriptions, requirements, and benefits are only included when `includeDescription` is enabled and available.
- Unavailable public boards and postings, or searches with no usable matches, finish successfully with an empty dataset and explanatory run warnings. An unavailable response does not establish whether a posting was private or deleted.
- Invalid inputs, broken extraction, essential storage or billing errors still fail. A mixed batch keeps useful jobs and reports isolated source failures. A run with no successfully processed available sources fails when extraction errors remain.
- Public Workable sources require no Workable API key.
- `RUN_SUMMARY` and `PENDING_WORK` in the default key-value store provide best-effort source warnings and progress. A hard timeout can prevent the final checkpoint. Start a new run for unfinished sources rather than resurrecting the same run.

The shared cap bounds saved jobs across boards. Leaving filters empty still does not guarantee a complete board archive. Public role, location and remote labels can change or be missing, and no hiring decision or application eligibility is inferred from them.

Keep RUN_SUMMARY and PENDING_WORK with your own interpretation of a partial export. Their presence reports warnings or unfinished boards rather than automatically creating a monitoring history or change alert.

#### Privacy and data handling

This Actor runs with Apify limited permissions and only processes data needed for the documented run. It uses job-search inputs and public job-posting results to produce the output dataset and sends requests to public Workable Jobs pages/endpoints. Results are stored in Apify run storage for your account. FetchCat does not use your inputs or outputs for advertising, does not use them for model training, and does not retain them outside the Apify run except for transient support debugging when you explicitly share run details. You are responsible for using the Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs.

### Automation and integrations

#### Save your settings for next time

Once you have an input that works for you, [save it as an Apify task](https://docs.apify.com/actors/running/tasks). This keeps your settings together so you can use them again without filling in the form from scratch.

#### Run on a schedule

Need fresh results regularly? You can [schedule the Actor or a saved task](https://docs.apify.com/actors/running/schedules) to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

#### Send results to your other tools

Use **n8n, Make or Zapier** to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the [Apify integration guides](https://docs.apify.com/integrations) for your chosen tool.

For a custom connection, an [Apify webhook](https://docs.apify.com/integrations/webhooks) can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

### API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its `defaultDatasetId` to fetch the results.

For setup instructions, see Apify's [JavaScript client guide](https://docs.apify.com/api/client/js), [Python client guide](https://docs.apify.com/api/client/python) and [Actor runs API reference](https://docs.apify.com/api/v2/acts-runs-post).

#### cURL

```bash
curl -X POST "https://api.apify.com/v2/acts/fetch_cat~workable-jobs-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companySlugs":["recurly"],"maxItems":10,"includeDescription":false}'
```

#### Node.js

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
  "companySlugs": ["recurly"],
  "maxItems": 10,
  "includeDescription": false
};

const run = await client.actor('fetch_cat/workable-jobs-scraper').call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python

```python
from apify_client import ApifyClient
import os

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("fetch_cat/workable-jobs-scraper").call(run_input={
  "companySlugs": ["recurly"],
  "maxItems": 10,
  "includeDescription": False
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)
```

### MCP and AI agents

You can ask your AI assistant to collect data with **Workable Jobs Scraper** and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the [Apify MCP server](https://mcp.apify.com/). MCP gives your assistant a way to find this scraper, run it and read the results. Follow the [official setup and sign-in guide](https://docs.apify.com/mcp) for your app.

#### Easier setup with an Apify plugin

If you use a supported coding assistant, the [official Apify plugin](https://docs.apify.com/agents/plugins) can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

#### Use Apify AI in Console

Prefer to keep everything in Apify? Open [Apify AI in Console](https://docs.apify.com/account/apify-ai) and ask it to find Fetch Cat's **Workable Jobs Scraper**. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

#### Choose your assistant

- **Claude and Claude Code (Anthropic):** [Apify setup guide](https://docs.apify.com/integrations/claude).
- **ChatGPT and Codex (OpenAI):** [Apify setup guides](https://docs.apify.com/integrations/openai).
- **Grok Bot (xAI):** [Apify plugin guide](https://docs.apify.com/integrations/grok-bot).
- **Gemini CLI (Google):** [MCP server setup guide](https://geminicli.com/docs/tools/mcp-server/). Use the server URL below with the HTTP configuration supported by Gemini CLI.

#### Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/workable-jobs-scraper"
    }
  }
}
```

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

#### Use Apify's general server

Already connected to the general Apify MCP server at `https://mcp.apify.com`? You can use it to find this scraper without adding another server. Ask your assistant to use **Workable Jobs Scraper** by Fetch Cat, or give it the identifier `fetch_cat/workable-jobs-scraper`.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

#### Example requests

- “Collect up to five Recurly engineering jobs and help me compare their locations and workplace labels.”
- “Get five public Recurly job descriptions and summarize the available requirements and benefits. Leave missing information marked as missing.”
- “Retrieve the public Workable posting at this job link and help me review its employment details. Tell me if it is unavailable instead of inventing a job.”

Normal Apify charges apply. Check the [live Pricing tab](https://apify.com/fetch_cat/workable-jobs-scraper/pricing) before asking your assistant to run a larger batch.

### Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through [x402](https://docs.apify.com/integrations/x402). This experimental option lets an agent use Apify without a conventional account.

[Apify AGI](https://agi.apify.com/) provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

#### Other ways for agents to pay

Apify also supports **MPP** for prepaid access through AGI and **Skyfire** for eligible Actors. If your agent already uses one of these, see the [agentic payment guide](https://docs.apify.com/agents/payments) to choose the right setup.

### FAQ

#### Can I scrape multiple Workable companies in one run?

Yes. Add multiple values to `companySlugs` or multiple URLs to `startUrls`.

#### Can I export Workable jobs to CSV or Excel?

Yes. Export the Apify dataset as CSV, Excel, JSON, XML, or RSS after the run.

#### Why did I get zero jobs?

Check that the company slug exists on `apply.workable.com`, remove strict filters, and try a small run without `query`, `locations`, or `departments`.

#### Why are descriptions missing?

Set `includeDescription` to `true`. Some boards or jobs still may not expose all detail fields.

#### Is this a Workable API alternative?

It can be used as an API-style export for public Workable career boards through Apify API, datasets, schedules, webhooks, and MCP.

### Related Actors

- [Ashby Jobs Scraper](https://apify.com/fetch_cat/ashby-jobs-scraper) — Collect public Ashby job-board openings and available job details.
- [ATS Jobs Scraper for 6 ATS Sources](https://apify.com/fetch_cat/ats-jobs-scraper) — Collect public job-board openings and available job details from supported applicant-tracking systems.
- [Built In Jobs Scraper](https://apify.com/fetch_cat/builtin-jobs-scraper) — Collect public Built In job listings and available company context.
- [Dice Jobs Scraper](https://apify.com/fetch_cat/dice-jobs-scraper) — Collect public Dice technology job listings and available job details.
- [Freelancer Jobs Scraper](https://apify.com/fetch_cat/freelancer-jobs-scraper) — Collect public freelance project listings and available project details.

### Support and feedback

For custom additions or integrations, email <hello@fetchcat.dev>.

Found an error or have a feature request? [Open an issue](https://apify.com/fetch_cat/workable-jobs-scraper/issues) with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See [Apify’s guide to sharing a run when reporting an issue](https://docs.apify.com/account/collaboration/general-resource-access#automatically-sharing-runs-via-actor-issues). Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. [Leave a review](https://apify.com/fetch_cat/workable-jobs-scraper/reviews) to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥

# Changelog

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

# Actor input Schema

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

Up to 100 unique public Workable sources across both source lists. Supports inline apply.workable.com company/job links, apply.workable.com/j short links, and jobs.workable.com/view job pages. Remote URL-list files are not supported. Connections are handled automatically; no proxy settings are needed. Omitted API inputs need companySlugs or startUrls. The displayed Recurly value is a form example, not an API default.

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

Optional case-insensitive keyword filter applied to each job title and public description, such as `engineer`, `marketing`, or `sales`.

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

Optional location text filters, for example London or United States. Remote-only selection uses the remote checkbox. At most 100 values.

## `workTypes` (type: `array`):

Optional Workable job type or workplace filters, for example full, hybrid, or remote. At most 100 values.

## `remote` (type: `boolean`):

Set to true to keep only jobs marked as remote, or false to keep only non-remote jobs. Leave empty for both.

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

Maximum number of job listings to save across all company boards.

## `companySlugs` (type: `array`):

Workable company slugs from apply.workable.com URLs, for example recurly. At most 100 unique sources combined with startUrls. The displayed Recurly value is a form example, not an API default. Both lists may be used, and duplicate sources are fetched once.

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

Optional department filters, for example Engineering, Product, or Sales. At most 100 values.

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

Include public description, requirements, and benefits HTML. The Actor requests an individual detail record only when the company feed does not contain it.

## `maxRunSeconds` (type: `integer`):

Safety budget from 60 to 270 seconds, default 270 when omitted. Includes a shutdown reserve. The independent wall-clock limit remains 270 seconds even if a platform timeout is longer or unlimited. A deadline failure preserves already saved jobs. Start a new run for unfinished sources rather than resurrecting the same run.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://apply.workable.com/recurly/"
    }
  ],
  "maxItems": 20,
  "companySlugs": [
    "recurly"
  ],
  "includeDescription": false
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

## `pendingWork` (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/recurly/"
        }
    ],
    "companySlugs": [
        "recurly"
    ]
};

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

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

```

## MCP server setup

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