Workable jobs API

Descriptions on every row and a real remote flag on a third of them — an unusually complete listing endpoint for small and mid-sized employers.

The endpoint

GET https://apply.workable.com/api/v1/widget/accounts/{company}?details=true

No key, no login. The slug is the path segment in apply.workable.com/{company}.

curl -s 'https://apply.workable.com/api/v1/widget/accounts/acme?details=true'

What it returns, measured

Measured across every live Workable board in our registry — 68,849 postings from 1,710 boards, not a sample. yes means 99.5% or more; no means the field does not exist on this endpoint.

Field	Workable
Posting date	yes
Description	yes
Pay	no
Marked remote	36.3%

Title, company, location and an apply URL come back on every row.

What it is good at

Dates on 100%, descriptions on 100%, and work arrangement stated on every row with 36.3% marked remote — second only to Ashby.

Where it falls short

No compensation field. Department is present on 85.1%, which is good but not universal.

Mistakes that cost us time

details=true is what brings the description.: Without it the widget endpoint is titles only.
It rate-limits harder than the others.: Workable returned 429 to our machine persistently enough that we validate its boards from a different network. Back off rather than parallelising.
A 429 is not a dead board.: We once discarded 1,644 Workable boards as dead when the only problem was our own request rate.

So should you use it

Yes, for description-rich data from smaller employers, with a usable remote flag.

No, for fast bulk sweeps. Its rate limiting sets the pace.

How Workable compares with the other eleven on the same four fields is on the comparison page. If you would rather not write and maintain a client, this Actor reads Workable and emits the same row shape as the other eleven, and ATS Database is a free lookup for finding which platform a given company is on.

Finding the boards

Workable boards are easy to find and hard to verify. Harvesting the slugs is straightforward, but the platform rate-limits validation hard enough that our first sweep marked 1,644 live boards as dead — the only problem was our own request rate. We now validate Workable from a different network and at a fraction of the concurrency used elsewhere. The registry holds 1,710 boards, and that number is conservative.