BambooHR Job Scraper | $1.50/1K — Salary Data, No Login

For recruiters, market researchers, and HR tools builders who need bulk job data from mid-market companies — BambooHR is your source.

Pricing: $1.50/1,000 jobs — with descriptions: ~$2.00/1K

BambooHR powers HR for 30,000+ mid-size companies. This actor gives you structured job data — including compensation text when disclosed — without any API key, proxy, or login.

Scrape job postings from any BambooHR-powered company careers page using the public careers JSON API — zero authentication, zero proxy required.

What it does

Fetches open job listings from BambooHR company career pages (e.g. https://flyio.bamboohr.com/careers), normalizes them into a consistent 18-field schema, and optionally fetches per-job details (description, compensation, exact posting date).

BambooHR powers HR for thousands of mid-size companies. This actor gives you structured, enriched job data at scale.

Output schema

Field	Type	Source	Notes
title	string	list	Job title
company	string	input	BambooHR slug
location	string	list/detail	City, state, country
remote_type	string	detail+list	remote/hybrid/onsite/null
seniority	string	title+exp	11 levels: intern→executive
salary	string	detail	Compensation text when provided
department	string	list	Department label
employment_type	string	list	Full-Time/Contractor/etc.
posted_at	string	detail	ISO date (YYYY-MM-DD)
url	string	detail	Job posting URL
apply_url	string	detail	Same as URL (apply on page)
job_id	string	list	BambooHR job opening ID
global_id	string	derived	bamboohr:{slug}:{id}
description_text	string	detail	Plain text (HTML stripped)
description_html	string	detail	Raw HTML
parse_confidence	float	derived	0.0–1.0 data quality score
warnings	list	derived	List of any quality issues
scraped_at	string	runtime	ISO timestamp

Input

Parameter	Type	Default	Description
companies	string[]	["flyio", "posthog", "sendbird"]	BambooHR slugs
titleKeyword	string	—	Filter by title substring
locationKeyword	string	—	Filter by location substring
remoteOnly	boolean	false	Only remote jobs
maxJobsPerCompany	integer	50	Cap per slug (0=unlimited)
includeDescriptions	boolean	true	Fetch description+compensation+datePosted

Finding the slug: The slug is the subdomain in the careers URL. For https://flyio.bamboohr.com/careers, the slug is flyio.

Why this scraper?

• parse_confidence — data quality score per row, not available in any competitor
• Compensation field — BambooHR exposes salary text in detail API; we surface it
• authoritative remote_type — uses BambooHR's structured locationType field (not text guessing)
• seniority enrichment — 11-level classification from title + BambooHR's minimumExperience fallback
• Zero proxy, zero auth — uses the same public JSON endpoints BambooHR's own careers pages use
• Redirect detection — cleanly reports companies not on BambooHR (instead of silent failures)

Pricing example

Run	Jobs returned	Cost
Trial (3 companies, 50-cap default)	~150	~$0.23
1,000 jobs (20 companies)	1,000	$1.50
10,000 jobs (bulk list-only)	10,000	$15.00

With includeDescriptions=true, one extra API call is made per job (still zero-auth — BambooHR's public API). $0.0015 per result.

Output sample

{
  "title": "Senior Backend Engineer",
  "company": "flyio",
  "location": "San Francisco, CA, US",
  "remote_type": "remote",
  "seniority": "senior",
  "salary": "$160,000 - $195,000 / year",
  "department": "Engineering",
  "employment_type": "Full-Time",
  "posted_at": "2026-05-20",
  "url": "https://flyio.bamboohr.com/careers/142",
  "parse_confidence": 1.0,
  "warnings": [],
  "scraped_at": "2026-06-05T10:00:00+00:00"
}

FAQ

Do I need an API key or proxy? No. This actor uses the same public JSON endpoints that BambooHR's own career pages use. Zero credentials needed.

What formats can I export? JSON, CSV, Excel, or JSONL — from the Apify dataset UI or via REST API.

Can I schedule daily monitoring? Yes. Use Apify Schedules to run daily and detect new openings by comparing job_id sets.

What if a company slug is wrong or not on BambooHR? The actor detects redirects and 404s cleanly, logs the failure, and continues — no crash, no charge for that slug.

Integrations

Built for recruiters and HR-tech builders pulling bulk job listings from mid-market company career pages — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Legal

Scrapes publicly accessible job listing endpoints that BambooHR intentionally exposes to the web (the same endpoints used by their own careers pages). No login, no credentials, no personal data. For informational purposes only.

Use with AI agents (MCP)

This actor is available via Apify's MCP server. Connect it to any MCP-compatible agent (Claude, n8n, Make) to pull live BambooHR job data on demand — no code required.

https://mcp.apify.com/?tools=bovi/bamboohr-job-scraper

Vs. competitors

Feature	This actor	Generic job scrapers
Compensation/salary field	Yes (detail API)	Rarely
parse_confidence score	Yes	No
Redirect detection	Yes (clean failure)	Silent failures
Seniority enrichment	Yes (11 levels + minimumExperience)	No
Zero proxy / zero auth	Yes	Often needs proxy
Price	$1.50/1K	$2–5/1K

Each row has parse_confidence (0.0–1.0). A score below 0.8 signals BambooHR API drift — catch it before it breaks your pipeline. No competitor provides this.

Not affiliated with BambooHR.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.