Workable Jobs Scraper

What this Actor scrapes

Thousands of companies run their careers page on Workable, and every one of those boards is served by the same public widget JSON API (apply.workable.com/api/v1/widget/accounts/{subdomain}). This Actor talks to it directly: hand it one or more subdomains — the {subdomain} in apply.workable.com/{subdomain} or {subdomain}.workable.com — and it pulls every open posting for each board in one call, normalizing the result into one row schema. One scraper, every Workable employer.

What we handle for you

• 🔑 Keyless public API — no OAuth, no token, no per-company setup; the same widget endpoint the careers page itself calls.
• 🏢 Multi-company in one run — pass many subdomains; rows come back identically shaped, tagged with company / company_name.
• 🎯 Client-side filters — narrow by free-text searchQuery, department, or location after the fetch, at no extra request cost.
• 📝 Optional full descriptions — flip includeDescription on for the complete HTML posting body, or off for a faster, smaller payload.
• 🔁 Retries with backoff + fingerprint impersonation — curl-cffi presents a real browser handshake and retries transient 429/5xx so a large multi-employer batch finishes instead of dying midway.
• 🧊 Clean, typed rows — Pydantic-validated, ISO-8601 timestamps, stable IDs. Export JSON / CSV / Excel straight from the Apify Console.

Use cases

• Recruiting & sourcing — pull every open req from a target employer's Workable board in one pass.
• Job-board aggregation — add Workable coverage next to Workday / Greenhouse / Lever / Ashby / SmartRecruiters in one pipeline.
• SDR / BD hiring-intent signal — track which companies are actively hiring, where, and in which departments.
• HR-tech data pipelines — wire structured job rows into your CRM, dashboard, or n8n / Make workflow on a schedule.

Input

Paste this into the Apify Console, or send it as the run input over the API. Proxy settings are on by default; you rarely need to touch them.

{
  "companies": [
    "remotebase"
  ],
  "maxResultsPerCompany": 25,
  "includeDescription": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Output

One row per result, schema-validated before it is written. Export JSON, CSV, Excel or XML from the run, or read it over the API.

job_idtitlecompanycompany_namedepartmentlocation_citylocation_countryis_remoteemployment_typeurlposted_datedescription_html

{
  "job_id": "6E7795E82F",
  "title": "AI Engineer",
  "company": "remotebase",
  "company_name": "Remotebase",
  "department": "Core",
  "location_city": null,
  "location_country": "Pakistan",
  "is_remote": true,
  "employment_type": null,
  "url": "https://apply.workable.com/j/6E7795E82F",
  "posted_date": "2026-04-01",
  "description_html": null,
  "scraped_at": "2026-07-23T15:00:00Z"
}

Pricing

You pay only for results that land. Cap any run with maxTotalChargeUsd. See pricing & billing for worked examples.

Limitations

• One row per posting — a job listed at multiple locations[] entries emits only the first location.
• Only currently-live postings; no historical/removed posting archive.
• searchQuery / department / location filters run client-side after the fetch — Workable's own server-side facets don't work reliably for this endpoint.