BambooHR jobs API

The largest board count of the twelve, and the thinnest rows. Both facts matter: this is where small employers are, and this is the endpoint that tells you least about them.

The endpoint

GET https://{company}.bamboohr.com/careers/list

No key, no login. The slug is the subdomain in {company}.bamboohr.com.

curl -s 'https://acme.bamboohr.com/careers/list'

What it returns, measured

Measured across every live BambooHR board in our registry — 50,616 postings from 9,711 boards, not a sample. yes means 99.5% or more; no means the field does not exist on this endpoint.

Field	BambooHR
Posting date	no
Description	no
Pay	no
Marked remote	no

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

What it is good at

9,711 boards, more than any other platform here — heavily small and mid-sized employers who never appear in a large aggregator. Employment type is on every row.

Where it falls short

The listing endpoint carries no date, no description and no compensation. Those live on a separate per-job endpoint, /careers/{id}/detail, which costs one extra request per posting.

Mistakes that cost us time

isRemote exists and is never set.: Across 50,616 postings measured, not one had it populated. A reader who trusts the field will conclude no BambooHR job is remote, which is not what the data says — it says nobody filled it in.
The API is split in two.: One request for the list, one per posting for detail. On a thousand-row sweep that is a thousand extra requests against employers' servers.
Locations are sparse.: City or state is present on 86.4% of rows; the rest carry nothing usable.

So should you use it

Yes, for reach into small employers, and for answering "does this company have an open role" cheaply.

No, for anything needing dates, text or pay without a second request per row.

How BambooHR 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 BambooHR 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

BambooHR has the largest board count here and it came from one sweep: 23,141 candidate subdomains from the Wayback index, of which 9,711 were live — a 42% yield, twice Recruitee's and ten times Greenhouse's. The bottleneck was not rate limiting (zero 429s across the whole sweep) but DNS: dead subdomains time out slowly, so throughput collapses at low concurrency and recovers at ten parallel requests.