Source · Workable

Workable Jobs API.

Every public Workable career site, one endpoint. No per-customer API keys to juggle.

Public Workable customers

24h refresh

12 months retention

Why people are confused about the Workable API

Workable offers a public Job Board API - but each Workable customer's API access is tied to their own account key. There is no first-party endpoint that exposes jobs across many Workable customers at once.

Workable customer careers pages live on apply.workable.com/<company> subdomains (or on customer-owned domains via embeds). JobsPipe indexes every public Workable careers page and normalizes the data into the same schema as our other sources.

Option 1

Get an API key from each Workable customer

Workable's Job Board API requires per-account credentials. Each customer must grant you access individually.

Option 2

Scrape apply.workable.com

Possible. Each customer is a separate config, and Workable's HTML/JSON shape varies by plan tier.

Option 3

Use JobsPipe

Every public Workable careers site, one endpoint. Same JSON schema as the rest of JobsPipe.

Workable API documentation

Workable's developer documentation lives at developer.workable.com and covers the Job Board API (read-only public postings per account), the main Workable API (full ATS surface, OAuth-scoped per account), and webhooks for downstream automation. The Job Board API is the closest to public - but each account's API key is private to that account, so aggregation across customers is not a feature. JobsPipe's documentation at /docs covers the unified JSON shape across Workable plus 30+ other sources.

Workable API key

Workable issues API keys at account level inside Workable admin under Integrations > API Access. Each key is scoped to one customer's data, and Workable does not mint public self-serve developer keys or cross-customer aggregator keys. JobsPipe needs no Workable credentials - we crawl public-facing careers pages and authenticate with one JobsPipe key.

Workable API integration

Single-customer Workable integration requires onboarding through that customer's Workable admin to mint you a per-account key. Cross-customer aggregator integration - what most teams arriving here actually want - is JobsPipe: every public Workable careers site, one endpoint, same JSON schema as 30+ other ATSs.

Sample request

curl "https://api.jobspipe.dev/v1/jobs?source=workable" \
     -H "Authorization: Bearer $JOBSPIPE_KEY" \
     -H "Accept: application/json"

Sample response

{
  "id": "wk_OWZmNzFlMjEtMzIwYg",
  "source": "workable",
  "tenant": "deelhq",
  "title": "Senior Account Executive, EMEA",
  "company": "Deel",
  "location": {
    "city": "London",
    "region": null,
    "country": "GB",
    "remote": false
  },
  "salary": null,
  "employment_type": "full_time",
  "posted_at": "2026-05-09T10:11:00Z",
  "expires_at": null,
  "apply_url": "https://apply.workable.com/deelhq/...",
  "description": "Deel is hiring a Senior AE to grow EMEA enterprise accounts. You'll own a quota of $1.5M+ ARR ..."
}

Every Workable job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.