What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can check public openings across Greenhouse, Lever, and Ashby by querying each provider’s job-board endpoint—but you need the correct board token or name for every company, and an empty response does not prove that the company is not hiring. The exact “47-line script” in the title cannot be verified from the available evidence, so this guide explains the documented endpoints and a reliable way to interpret their results without claiming that a particular script was tested.
What you need before checking companies
First identify which applicant-tracking system hosts each company’s careers page. The company’s hosted board URL usually supplies the identifier needed for its endpoint: a Greenhouse board token or an Ashby board name. Lever’s postings API likewise needs the account-specific site identifier. A company may use a different platform, or change platforms, so a list of identifiers is not a permanent directory of all employers.
Use the public job-board interfaces when the goal is to find roles candidates can see. The three providers do not expose identical fields or use identical response formats, so a multi-company checker needs provider-specific requests and parsing rather than one assumed universal response.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Which public endpoint to use
| Provider | Public route and identifier | What the documented result represents | Useful fields and caveats |
|---|---|---|---|
| Greenhouse | Job Board API: GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs. The token comes from the company’s Job Board URL. |
Public job-board data. Greenhouse says authentication is not required for GET endpoints. | Add ?content=true to include descriptions, department, and office data. The application-submission POST route is separate and is not needed to read listings. |
| Lever | Postings API: request the account’s postings endpoint and handle its posting state. | Results filtered to published are postings that appear on the public job site. Other states include internal, closed, draft, pending, and rejected. |
Request content if descriptions are needed, and intentionally restrict or handle states; internal or unpublished records should not be counted as public openings. |
| Ashby | Public Job Postings API: GET https://api.ashbyhq.com/posting-api/job-board/{JOB_BOARD_NAME}. Use the final segment of the hosted jobs.ashbyhq.com board URL. |
Currently published postings on that public job board. | Can return title, location, employment type, job URL, and apply URL. Add ?includeCompensation=true to request compensation; compensation fields may be absent when the underlying data is missing. |
Ashby also offers an authenticated jobPosting.list endpoint requiring the jobsRead permission. It is not the same as the public GET endpoint: by default it may include unlisted postings, so a public-facing integration should set listedOnly=true. Ashby describes that authenticated route as part of custom careers integrations, not as a substitute for the straightforward public-board check.
#1 Best Overall
How to build a multi-company checker
- Record each board identifier. For every company, save its name, provider, and provider-specific token or board name. Derive the identifier from the hosted careers-board URL and verify it against that company’s board; do not assume the company name itself is the identifier.
- Fetch through the matching provider route. Make a separate request for Greenhouse, Lever, or Ashby. For Lever, ensure the request returns or filters to
publishedpostings if your goal is public vacancies. - Check the response before parsing it. Treat an HTTP error, unexpected response shape, or failed request as an inspection error—not as an empty list of jobs. Keep enough provider and response detail to diagnose a bad identifier or an endpoint change.
- Normalize only fields that exist. A useful shared record can contain company, provider, title, location, department or team when supplied, posting URL, and apply URL. Preserve the original posting or diagnostic data where practical; fields such as compensation, descriptions, departments, and office information are not uniformly available.
- Report visibility and freshness honestly. Label results as public postings returned by the board and include when the check ran. Do not present them as every role the company may be recruiting for.
This design follows the providers’ documented differences; it is implementation guidance, not a description of verified code in a particular 47-line script. Greenhouse’s support overview distinguishes its public Job Board API from Harvest, whose endpoints require authentication; for public listing monitoring, the Job Board API is the relevant route.
Why an empty result does not mean “not hiring”
- The identifier may be wrong. An incorrect or outdated token or slug can point nowhere useful even when the company has public openings.
- The company may use another ATS. Checking only these three providers cannot establish that a company has no jobs.
- The request may have failed. Network errors, changed response formats, or server errors must be distinguished from a successful response containing no postings.
- The role may not be public or listed. Public job-board routes focus on published postings. Ashby’s authenticated endpoint can include unlisted postings unless
listedOnly=trueis set; Lever also distinguishes public published postings from other states. - Timing can matter. A listing can be added, removed, or updated after a check. A result describes what the endpoint returned at the time of the request.
Greenhouse’s official support page was last updated August 26, 2026, and describes the Job Board API as the public route for board data and custom career sites. Its Harvest API is a separate authenticated product; the support page said Harvest API v1 and v2 were to be deprecated and unavailable after August 31, 2026. That distinction is another reason not to base a public monitor on Harvest.
Rank #2
How representative is a cross-provider comparison?
A third-party repository by GregoryBolshakov reported a snapshot of 5,122 job adverts across 16 companies, measured August 29, 2026. It compared field availability across Greenhouse, Lever, Ashby, and SmartRecruiters. That is a limited sample, not a measure of all employers or current global coverage; it supports the practical point that returned fields vary, but it cannot establish universal field-completion rates or hiring trends. See the comparison repository for its dated sample.
Quick Recap
Best Value
- Jobsite Tool: this offering includes 1 black construction planner, 184 sheets in total, use for 6 months; Record your thoughts, make sketches, keep track of progress in one place; It is of quality and a staple in your daily jobsite schedule
- Versatile Uses: a construction notebook seeks to cater to every individual who requires a systematic and reliable way to note, draft or sketch; Its size and design make it suitable for multiple person use
- Quality Materials: crafted from quality PU leather and paper, the construction site book withstands everyday use and wear and tear, smooth to write; The pure black, sturdy cover provides both style and longevity, maintaining its fresh look
- Efficient for Enhanced Productivity: experience boosted productivity with our construction log book's clear and efficient layout; The layout is designed to help you note important details without hassle, specific to jobsite activities and tasks
- Easy Documentation: the construction journal, which is the tool for efficient onsite documentation; With its convenient size of about 7 x 10 inches, fitting into your work bag or briefcase is easy; It's the accessory for architects
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

