BambooHR Jobs Scraper & API — Any BambooHR Board
Pricing
from $4.00 / 1,000 jobs
BambooHR jobs API. Paste a BambooHR board slug, board URL or company domain and get every open role on that board, read live when you run it. One normalized schema with parsed salary, seniority, remote flag and direct apply URLs. Pay per job; boards we cannot reach are free.
The BambooHR boards to pull open roles from — one per line. Paste a board slug (bamboohr:basdensteel), a board URL, or a plain company domain and the Actor finds the board itself. It is the subdomain of the careers page: <company>.bamboohr.com/careers. A company whose board cannot be found returns a free row explaining why.
[ "bamboohr:basdensteel"]Curated company bundles you can run without researching a single slug. Every company in these lists is verified against its live board. Merged with anything in Companies above and de-duplicated.
[]Return only postings that are new, or whose title, department, location, salary, employment type or workplace type changed since a previous run of this feed. Description edits do not count as a change, so a re-worded posting is never re-charged. This is what makes a daily or hourly schedule cheap: the first run returns the full board, and every run after it returns — and charges for — only what genuinely moved. Leave it off for a one-off full export.
Keep only postings published within this many days. Leave empty for all open roles. Postings whose board publishes no date are excluded when this is set, because they cannot be proven fresh.
Keep only jobs whose title contains one of these words (case-insensitive). For example: engineer, designer, account executive. Leave empty for every open role.
[]Drop jobs whose title contains any of these words. Applied after the include filter above. Useful for stripping intern, contract, or non-English duplicates out of a feed.
[]Keep only jobs matching one of these locations. Every location on a multi-site posting is checked, not just the first one, so a role open in both Berlin and Lisbon matches either.
[]Keep only roles the board marks as remote. Hybrid roles are excluded, and so are roles where nothing on the posting says either way — 'remote only' should not return maybes.
Keep only these seniority levels. Seniority is inferred from the job title, because almost no ATS publishes it as a field. Entry level means genuinely junior and graduate roles — not a '0-2 years' bucket that returns experienced ones.
[]Keep only these employment types, normalized across every platform's own vocabulary (Lever's 'Full-time', Ashby's 'FullTime' and Personio's 'permanent' all become fullTime).
[]Keep only jobs whose department matches one of these, for example: engineering, sales, marketing.
[]Keep only postings where a real salary range could be parsed into numbers. Boards differ a lot here — Ashby publishes structured pay, most others only mention it in prose, and some never do.
Hard cap on billable jobs for the entire run. The Actor stops at exactly this number — never over, and it tells you in the log when a cap is the reason results were truncated. Leave empty for no cap.
Cap per company, applied after filtering and newest-first sorting, so a handful of very large boards cannot dominate a run. Leave empty for every matching role.
Add the complete job description as both HTML and plain text. Off by default because descriptions are large and most feeds do not need them. On Workday and SmartRecruiters this needs one extra request per job, so those boards get noticeably slower — the price per job does not change.
Defaults to BambooHR only, which is what this Actor is for. The same engine covers 14 platforms — add more here, or use the multi-ATS version if you routinely mix them.
[ "bamboohr"]How many company boards to fetch in parallel. The default is deliberately polite to the career sites being read; raise it for very large lists.
Names the memory used by 'Only new or changed jobs'. Leave empty and it is derived from your company list, so two different lists automatically keep separate memories. Set it explicitly when you run several schedules over overlapping companies and want each to track changes independently — or set the same name on two tasks to share one memory.