Workable jobs as JSON: a keyword search across every company on Workable, and any one company's board
- endpoints
- 3
- credit per call
- 1
The Workable Jobs API returns Workable job postings as JSON in two ways: a keyword search across every company that hires on Workable (Workable's own job index at jobs.workable.com), and one company's board on apply.workable.com.
/workable/v1
- POST/workable/v1/company_jobs1 credit
- POST/workable/v1/job_detail1 credit
- POST/workable/v1/search1 credit
1 credit per call≈ $1/1,000 calls1,000 free credits, no card
Get a free API keyRun the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
Workable Jobs API
3 of 3 endpoints, ready to run
Jobs from every company hiring on Workable that match your words, with company, location, workplace, posted date and full description
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
What Workable Jobs endpoints does ReefAPI ship?
3 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
company_jobs
1 crEvery open job on one company's Workable board → jobs[] (id, title, url, company, location, l…
- required
- company
- optional
- limit, cursor, page
job_detail
1 crOne Workable posting in full by company + job_id.
- required
- company, job_id
- optional
- —
search
1 crCross-company search over Workable's own job index (jobs.workable.com) → jobs[] with title, u…
- required
- query
- optional
- workplace, remote, location, posted_within_days, max_pages, limit, cursor, page
Every parameter, every allowed value →
Missing a Workable Jobs endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the Workable Jobs API works
Workable Jobs is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 746 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
From a skill to every matching Workable job, then one company's board
Search across companies when you do not know who is hiring; read a board when you do. Old POST /ats-jobs/v1/... calls keep working unchanged; the call for Workable on its own is POST /workable/v1/<action>.
{"query": "python engineer", "limit": 20, "max_pages": 1}On 2026-11-21: 1,866 matching jobs at Workable companies; 20 came back in 0.76 seconds (Man Group, Stack Builders, Trexquant, payabl. and others) in Bulgaria, the United Kingdom, Argentina, Brazil, the United States, Poland, Canada, Malaysia, Portugal and Lithuania, each with its full description.
{"company": "workana-premium"}One company's board: 189 open jobs; 20 came back in 1.1 seconds with title, link, location, locations, department, workplace, posted date and apply link. Board rows carry no description.
{"company": "workana-premium", "job_id": "1B3F59CCCB"}One board posting in full, with description, requirements and benefits. 3 of 3 job ids sent by a customer for this board answered on 2026-11-21.
Jobs from every company on Workable for a skill and place, with company name, location, workplace type, posted date and description, and any one company's full list of open roles.
curl -X POST https://api.reefapi.com/workable/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"python engineer"}'{
"ok": true,
"data": { … },
"meta": {
"api": "workable",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a Workable job field contains
Fields that read differently from how they look. Each row was measured through this API on 2026-11-21 unless it gives another date.
| Field | What it holds |
|---|---|
| id (search) | A 22-character code from the jobs.workable.com link (5FcG2iD4fDc75LpE4GFP4p). It is not a board job id and cannot be sent to job_detail; the search row already carries the full description. |
| id (company_jobs) | The board's 10-character job code (1B3F59CCCB), the one job_detail takes together with the account subdomain. Valid only while the role is open. |
| company | In search, the company's display name (Man Group). In company_jobs, the account subdomain you sent (workana-premium). A search row does not give the subdomain. |
| total (search) | Workable's own count for the query after its workplace and location filters: 1,866 for python engineer. posted_within_days is applied by us afterwards, so compare count with total and read dropped_by_date_filter. |
| workplace_type, remote | remote, hybrid or onsite as Workable states it; on the python engineer page remote 10, hybrid 7, on-site 3. |
| location, locations | City, region and country as Workable writes them ("Sofia, Sofia City Province, Bulgaria"). Workable lists a role once per location, so one role can be several rows. |
| pages_read, budget_exhausted | How many pages of 20 the search read, and whether it stopped because max_pages ran out while Workable had more. |
| description | Present on 20 of 20 search rows (1,264 to 8,771 characters of text). Board rows from company_jobs have none; job_detail adds description, requirements and benefits. |
workplace and location are applied by Workable itself (measured 2026-09-28 on python engineer, 2,043 jobs: remote 1,041, hybrid 488, on-site 514, London 66). Workable has no country parameter: location matches how Workable writes the place, so a city name works and a bare country code does not.
What Workable returns, measured
Every number below was read through this API on 2026-11-21, unless a row gives another date.
python engineer: 1,866 jobs. Each row: title, link, company name, location, locations, workplace type, remote flag, posted and updated dates and full description (1,264 to 8,771 characters of text) on 20 of 20; employment type on 16, department on 15.
Workable's index spans many countries: one page of 20 python engineer jobs was in Bulgaria, the United Kingdom, Argentina, Brazil, the United States, Poland, Canada, Malaysia, Portugal and Lithuania. Workplace on that page: remote 10, hybrid 7, on-site 3.
workplace and location are applied by Workable itself (measured 2026-09-28 on python engineer, 2,043 jobs: remote 1,041, hybrid 488, on-site 514, London 66). posted_within_days is applied by us over the pages max_pages allows (20 jobs a page, 5 by default, up to 25); pages_read and budget_exhausted say whether the budget cut the result short.
workana-premium: 189 open jobs, ids as 10-character codes (1B3F59CCCB), locations such as Argentina, Mexico City, Colombia and São Paulo, workplace remote on 19 of 20. An account with no open jobs answers total 0; a name that is not a Workable account answers NOT_FOUND.
Workable lists a role once per location: Stack Builders' Remote Contractor - Senior Python Engineer was 6 rows (2 cities in Argentina, 4 in Brazil). Group by title and company to count roles.
Workable has no salary field: 0 of 20 search rows had pay. A search row gives the company's name and a jobs.workable.com link, not its account subdomain, and its 22-character id is not a board job id; the search row already carries the description. Board rows carry no description; job_detail does.
What people build with Workable Jobs
The jobs this data is most often used for.
Find every Workable job for a skill in a city or remote, across all companies, with the full description.
Collect new postings daily with posted_within_days and a fixed page budget.
Track open roles at a list of companies from their Workable boards.
Merge Workable, Greenhouse, Lever and Ashby jobs into one list without remapping fields.
endpoints
credit per call
What Workable Jobs data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
- 1,000 free credits on signup, no card
- One key, all 746 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/workable/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"python engineer"}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/workable/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "python engineer"
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Workable Jobs.
Is there a Workable API?▾
Yes. The workable API on ReefAPI searches the jobs of every company hiring on Workable and reads any company's Workable board, as JSON with company, location, workplace type, posted date and full description, in the same shape as the Greenhouse, Lever and Ashby APIs. Workable's public careers pages and job index are read without a Workable account. The call is POST /workable/v1/<action>; old POST /ats-jobs/v1/... calls with ats workable keep working unchanged.
Can I search jobs across all companies on Workable?▾
Yes, with search. "python engineer" matched 1,866 jobs on 2026-11-21, each with company name, location, workplace type, posted date and full description. Filter by city with location, by remote, hybrid or on-site with workplace, and by age with posted_within_days.
Which countries are covered?▾
Every country where companies post on Workable. One page of 20 python engineer jobs on 2026-11-21 was in Bulgaria, the United Kingdom, Argentina, Brazil, the United States, Poland, Canada, Malaysia, Portugal and Lithuania. Filter by place with a city name as Workable writes it (London returned 66 of 2,043 on 2026-09-28).
How do I read one company's Workable jobs?▾
Call company_jobs with the account subdomain, the name in apply.workable.com/<account>. workana-premium returned 189 open jobs on 2026-11-21. An account with no open jobs answers total 0; a name that is not a Workable account answers NOT_FOUND.
How do I control the cost of a search?▾
max_pages caps how many pages of 20 jobs one search reads (5 by default, up to 25). The response says pages_read and budget_exhausted, so a result cut short by the budget is not mistaken for the end of the results.
Does it return salaries?▾
No pay field: Workable publishes none, and 0 of 20 python engineer search rows had pay on 2026-11-21. For published salary ranges, the ashby API returns them on Ashby boards.
Why does the same job appear several times?▾
Workable lists a role once per location. Stack Builders' Remote Contractor - Senior Python Engineer came back as 6 rows, 2 cities in Argentina and 4 in Brazil. Group by company and title to count roles.
What is the Workable Jobs API?▾
Workable Jobs API is a ReefAPI endpoint group for search the jobs of every company hiring on workable by keyword, city and remote or hybrid, or read one company's workable board, with full descriptions. It returns live JSON through POST requests under /workable/v1.
Is the Workable Jobs API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Workable Jobs calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Workable Jobs login or account?▾
No login to Workable Jobs is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Workable Jobs data?▾
The page example is captured from a live company_jobs call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Workable Jobs API use?▾
Workable Jobs actions currently cost 1 credit per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Workable Jobs from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call workable actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Workable Jobs API a Workable Jobs scraper?▾
It is the managed alternative to a DIY Workable Jobs scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same search the jobs of every company hiring on workable by keyword, city and remote or hybrid, or read one company's workable board, with full descriptions back as clean JSON.
36 Jobs & Hiring APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Workable Jobs, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 745 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-21.