Greenhouse Jobs Scraper & API - All Companies, Last 24 Hours

Greenhouse Jobs Scraper & API - All Companies, Last 24 Hours

Greenhouse jobs scraper and API: search every company's job board on Greenhouse (boards.greenhouse.io and job-boards.greenhouse.io) at once, live, and get each job's title, company, location, remote or onsite, job type, salary range, first-published date, deadline and link, newest first. Turn on full details for the description, the department, the company's reference number and pay as numbers.

Use it as a Greenhouse jobs API with no Greenhouse API key, a Greenhouse job board scraper or a daily job feed from the Apify Console, the Apify API, Python, JavaScript, n8n, Make or an AI agent, and export JSON, CSV or Excel. It is the site:boards.greenhouse.io Google dork done at the source, with the fields a search result cannot give you. Available as an Apify Actor. $0.0018 per job, $0.0019 with full details, no start fee, no login, no API key.

What does it do?

• Searches 8,357 Greenhouse job boards of 8,317 companies at once. On 2026-11-02 they held 216,033 open jobs at 7,201 companies, at employers such as SpaceX, Anduril, Databricks, Stripe, Anthropic, Cloudflare, Datadog, Coinbase, GitLab, Airbnb, Reddit and Figma.
• Pay on the plain row. When a company publishes pay, 22% of the jobs, it comes with every row at no extra price, every pay zone included.
• One keyword is enough. Type a job title and press Start. Leave the form empty for the newest jobs of every kind.
• Newest first, read live. Every job comes from Greenhouse at the moment of your run, sorted by the date the company first published it.
• Filters that take what people type. London, Germany, EMEA, Remote, contract, last 24 hours, or a pasted Google dork such as site:boards.greenhouse.io intext:engineer.
• Checks job links. Paste links, including the career pages of companies on the list with ?gh_jid=, and each comes back open, closed or not found.

How is it different from other Greenhouse scrapers?

• Every company, read live. Greenhouse publishes no list of its customers, so a live reader normally needs a board name or link from you, and most actors that search every company read a stored copy. This one carries a list of 8,357 boards built from public job APIs, Common Crawl, the Wayback Machine and GitHub lists, and reads all of them at the moment of your run. Of the 13 most used actors that cover Greenhouse (the table below), 4 need board names, links or a curated preset list, 8 search a stored copy, and one other reads live: yugenox/ats-jobs-search, across Greenhouse, Lever and Ashby.
• The real posting date. Greenhouse keeps two dates for a job: when it was first published and when it was last edited, and most jobs are edited long after they go up. In the 24 hours before 14:25 UTC on 2026-11-02, 952 jobs were first published, while 6,692 carried an edit from that day, so a last-24-hours filter on the edit date lists five to seven times the jobs that are really new (5.6 times in a sample of 2,000 boards at 18:29 UTC the same day). This actor uses the first-published date, the one Greenhouse's own board pages use for their New tag (1,482 of 1,482 jobs checked).
• Every pay range. Companies that pay by place publish one range per zone or country, and the row keeps all of them, in each currency (1,986 jobs show more than one).
• Links from anywhere on Greenhouse. Old and new board addresses, the EU boards, embed links, the API's own links and the career pages of companies on the list with ?gh_jid= all read as the same job.
• A failed read costs nothing. You pay per delivered row.

When should I use it?

• Job seekers and job boards: new jobs by title, country and date across thousands of tech companies, with pay where it is published, on a daily schedule.
• Recruiters and sourcing teams: see who is hiring for a role right now, anywhere on Greenhouse, and at what pay.
• Sales and market research: companies hiring for a function, by country and date, as a buying signal, and a list of the companies that hire through Greenhouse.
• Data teams and AI agents: one clean, stable feed of Greenhouse jobs through the API or MCP.

How much does it cost to scrape Greenhouse jobs?

Pay per event. Platform usage is included, and there is no start fee or monthly fee.

On paid Apify plans these are 10% less on Scale ($0.00162 and $0.00171) and 20% less on Business and above ($0.00144 and $0.00152).

Apify's free $5 monthly credit covers about 2,800 jobs. Number of jobs (maxJobs) sets the most a run can cost, and a run stops at its spending limit with a message saying so.

How does the price compare with other Greenhouse scrapers?

Every actor on the Apify Store that names Greenhouse in its title, slug or description and had 60 or more users in the last 30 days, found by searching the Store for 13 Greenhouse terms and 33 job terms on 2026-11-02 (4,956 actors read), ordered by users. Free-plan prices from each actor's current pricing.

Where others are cheaper: bovi costs $0.0015 a job, and a little less on paid plans, when you already know the companies or use its curated preset lists. On paid plans several drop below this actor's $0.00162 on Scale and $0.00144 on Business: fantastic-jobs/greenhouse-jobs-api costs $0.0012 on both, bytepulselabs/greenhouse-job-scraper $0.0016 and $0.0014 (and $0.0018 on Starter, the same as here), jobo.world/ats-jobs-api $0.0013 on Business, and fantastic-jobs/career-site-job-listing-feed $0.0012 and $0.0008 plus a $0.001 start fee. Where others do more: the database actors add fields extracted by AI and LinkedIn company data, and the multi-ATS ones cover many platforms in one run.

Which inputs does it take?

Nothing is required. Type a job title and press Start, or press Start with the form empty.

Example input:

{
  "searchTerms": ["software engineer"],
  "location": ["London", "Germany"],
  "postedWithin": "7 days",
  "maxJobs": 100
}

What does the output look like?

One row per job, newest first. These rows are from a local run of the actor's engine (v0.4.0) on 2026-11-03, searching every board for software engineer: 8,782 jobs at 1,554 companies, the 100 newest saved. TODO_DEPLOYED: the rows, build number and seconds of the deployed build's example run go here.

One row as JSON:

{
  "title": "Staff Software Engineer, Tech Foundations",
  "company": "Airbnb",
  "location": "United States",
  "otherLocations": [],
  "workType": "remote",
  "employmentType": null,
  "department": null,
  "salary": "USD 212,000 - 265,000",
  "postedAt": "2026-11-02T19:03:07Z",
  "expiresAt": null,
  "jobUrl": "https://careers.airbnb.com/positions/8334372?gh_jid=8334372",
  "applyUrl": "https://careers.airbnb.com/positions/8334372?gh_jid=8334372",
  "status": "open",
  "platform": "greenhouse",
  "companySlug": "airbnb",
  "companyWebsite": "https://careers.airbnb.com",
  "jobId": "8334372",
  "checkedAt": "2026-11-03T08:42:31+00:00"
}

Full details fill department and add description, descriptionHtml, reference, salaryMin, salaryMax and salaryCurrency. A checked link that is closed or not found comes back with its status, company and link, and the other fields empty. A run also writes an OUTPUT record: how many job boards were read, how many jobs matched and were saved, the boards that could not be read, and any notes on how your input was read.

How fast is it?

TODO_DEPLOYED: the seconds of the empty form and of a keyword search at the default memory on the deployed build, with their run ids, go here. Greenhouse has no search, paging or order, so every search reads all 8,357 boards, one call each, and a keyword takes about as long as the empty form. Naming companies or checking links reads only those boards. Matching descriptions downloads every description, so it is slower.

Common questions

Which posting date does it use?

The moment the company first published the job. Greenhouse also keeps the time of the last edit, which moves whenever a job is touched: on 2026-11-02, 70% of open jobs had been edited more than a week after they went up. This actor sorts and filters by the first-published date, the date Greenhouse's own board pages use for their New tag, so last 24 hours means new jobs, not old ones that were edited.

Why does a keyword search take as long as an empty form?

Greenhouse's job board API answers with every open job of one board, with no search, paging or order. So every search reads all 8,357 boards, one call each, and matches your words itself. Naming companies in Only these companies reads only those boards, which is much faster.

Why does United States miss some US jobs?

Greenhouse keeps a job's location as the text the company typed, with no country field. On 2026-11-02, 59,614 jobs (28%) gave a US city and state code, such as Austin, TX, and no country, and United States found only 47 of them. Add the city or the state code to the places you type: TX also finds Texas. Two-letter codes that are also countries, such as CA, IN and GA, find both the state and the country (Canada, India, Gabon).

Why do some jobs show several pay ranges?

Companies that pay by location publish one range per zone or country, and the row keeps all of them, joined with a semicolon: EUR 70,000 - 110,000; EUR 85,000 - 110,000; PLN 250,000 - 480,000 is one real row. Greenhouse stores amounts and a currency with no period, and hourly and yearly pay both occur, so read the amount with the job. With full details on, salaryMin and salaryMax are the lowest and highest amounts in the first range's currency.

How does it find every company?

Greenhouse has no public list of its customers, so the list is built the way the site:boards.greenhouse.io dork works, from the web's own memory: freehire's public job API, Common Crawl's index, the Wayback Machine, and public company and job lists on GitHub gave 15,747 candidate names, and 23,941 names from other job platforms' company lists were tried as well. 32,663 of the 39,688 were checked live with Greenhouse's API; the other 7,025 guessed names were refused while Greenhouse blocked the address, and 54 of them checked later were all missing. 8,357 boards answered on 2026-11-02, 7,233 of them with open jobs, after 21 sandbox and test boards were left out. An estimate from how often the sources overlap puts the hiring boards on Greenhouse at 8,477 or more, so the list holds at most about 85% of them. To search a company that is not on the list, paste its link or type its name into Only these companies.

Does it need a login or an API key?

No. Greenhouse's Job Board API is public: it serves what each company's job board shows any visitor. Greenhouse's other APIs need a customer's own key and read only that customer's data. You need only an Apify account.

How do I run it from Python or an AI agent?

Through the Apify API, with your Apify token:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("anshumanatrey/greenhouse-jobs-search").call(run_input={"searchTerms": ["software engineer"]})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(row["title"], row["company"], row["location"], row["salary"], row["jobUrl"])

AI agents can call it through the Apify MCP server at https://mcp.apify.com, and n8n and Make have Apify nodes.

Am I charged for closed jobs?

A search returns open jobs only. A pasted link that turns out closed or not found is one Job row, because it was checked and answered.

Is it legal to use?

It reads public job postings. You are responsible for how you use the data, including each site's terms and the privacy laws that apply to you.

Limitations

• Locations are free text with no country field: 28% of jobs give only a US city and state, which a United States filter misses (see above).
• Work type and job type exist only when a company states them: in its own job fields, or for work type in the location (Remote, Hybrid, On-site) or the title (Remote, Hybrid). On 2026-11-02, 18.9% of jobs had a work type and 18.0% a job type, and a filter on either leaves out the rest.
• Pay is on 22% of jobs, has no period, and several zones are joined in one text.
• The department comes with full details, a checked link or a description search; the reference number and the description come only with full details, which reads each saved job once more.
• Greenhouse answers a closed job and a job ID that never existed the same way, so both come back closed.
• Company career-site links (?gh_jid=) are read for the 990 companies on the list whose jobs link to their own site; other career sites and grnh.se short links are not.
• Every search reads every board, so a keyword takes about as long as the empty form.
• Greenhouse blocks an address that makes too many calls for a while. If it refuses the run's address, the run waits up to 3 minutes per board for the block to lift, says in its message how many boards could not be read and lists them in the OUTPUT record; when no board could be read, the run fails with that reason.
• A job a company posts twice at the same place is delivered once (7,477 such copies on 2026-11-02).
• 45 boards are named as a company's internal or referral-only board (Coupang Internal, Referrals Only), meant for its own staff or for referred candidates: their 1,203 jobs on 2026-11-02 come back like any other.
• Titles and descriptions come in the company's own language, most of them (95%) in English.
• The list of boards was built on 2026-11-02. A company that joined later is searched only when you name it.

Who maintains it?

Built and maintained by Anshuman Atrey (@AnshumanAtrey), who publishes a portfolio of data and OSINT actors on Apify Store. For a feature request or a bug, message LinkedIn (fastest), open an issue on the GitHub repo, or write through atrey.dev.

Sibling actors

Documentation

• Apify Store: https://apify.com/anshumanatrey/greenhouse-jobs-search
• GitHub repo: https://github.com/AnshumanAtrey/greenhouse-jobs-search (MIT license, see LICENSE)
• The engine behind it: https://github.com/AnshumanAtrey/ats-jobs-engine

Last updated

2026-11-03 (version 1.0)