Workable Jobs
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.
/workable/v1/company_jobs1 creditEvery open job on one company's Workable board → jobs[] (id, title, url, company, location, locations, department, team, employment type, workplace, posted date where Workable publishes it), count and total. `company` = the board's account subdomain (the name in apply.workable.com/<account>).
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| company | required | — | The company's Workable account subdomain (the name in apply.workable.com/<account>), e.g. 'huggingface', 'skroutz'. Aliases: token, board. |
| limit | optional | 1–2000 | Max jobs to return (1-2000). Omit/0 = provider default (all). |
| cursor | optional | — | Opaque pagination cursor from a previous response (provider-specific). |
| page | optional | 1– | Page number for providers that paginate by page (alternative to cursor). |
/workable/v1/job_detail1 creditOne Workable posting in full by `company` + `job_id`: title, location, department, description, requirements and benefits where the posting has them.
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| company | required | — | The company's Workable account subdomain (the name in apply.workable.com/<account>), e.g. 'huggingface', 'skroutz'. Aliases: token, board. |
| job_id | required | — | The job's id on that Workable board (jobs[].id from company_jobs). An id is valid only while the posting is open; call company_jobs for a current one. |
/workable/v1/search1 creditCross-company search over Workable's own job index (jobs.workable.com) → jobs[] with title, url, company, location, workplace type, remote flag and posted date. `workplace` and `location` are applied by Workable; `posted_within_days` is applied by us over the pages `max_pages` allows (20 jobs per page, default 5), and the response reports pages_read and budget_exhausted.
| Parameter | Allowed / range | Description | |
|---|---|---|---|
| query | required | — | Free-text keyword for the Workable cross-company aggregator search. |
| workplace | optional | remote · hybrid · on_site | Restrict to one working arrangement. The aggregator applies this itself, so it costs nothing extra and narrows the result at source rather than after paging. |
| remote | optional | — | Shorthand for workplace=remote. Ignored when `workplace` is given, since that is the same axis stated precisely. |
| location | optional | — | Free-text place, applied by the aggregator itself (so it is cheap). It matches how Workable writes the location, so a city name works; a bare country code does not, because the aggregator has no country parameter. |
| posted_within_days | optional | 1–365 | Keep only jobs first posted within this many days. The aggregator offers NO date filter (postedAfter, createdAfter, since, dayRange and days are all accepted and all ignored), so this is applied on our side across the pages `max_pages` allows. Check `budget_exhausted` before concluding a window is empty. |
| max_pages = 5 | optional | 1–25 | Hard cap on how many aggregator pages one search may read (20 jobs per page; default 5, ceiling 25). This is the cost control: a narrow filter can never walk the whole index. The response returns `pages_read` and `budget_exhausted` so the cost is knowable before the call and visible after it. |
| limit | optional | 1–2000 | Max jobs to return (1-2000). Omit/0 = provider default (all). |
| cursor | optional | — | Opaque pagination cursor from a previous response (provider-specific). |
| page | optional | 1– | Page number for providers that paginate by page (alternative to cursor). |
curl -X POST https://api.reefapi.com/workable/v1/company_jobs \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"company":"huggingface"}'{
"ok": true,
"data": { /* the result */ },
"meta": {
"latency_ms": 240,
"record_count": 12,
"completeness_pct": 100
},
"error": null
}Measured at 60 requests a second across the fleet, with no central bottleneck. Volume pricing is on request, and per-key limits are raised for high-volume accounts.
Tell us a site we do not cover yet and it becomes an engine. A customer asked for bestprice.gr on a Sunday and it was in the catalog the next day.
Median time from a question in the live chat to the first answer, measured across every answered conversation. Setup help included, no support tier to buy.
No per-site plans and no separate subscriptions. One key and one credit pool across the whole catalog, so adding a source costs nothing up front.
Planning something large? Tell us the volume and the sources and we will come back with what it costs and what we would have to build.