You can use Greenhouse, Lever and Ashby APIs to monitor job postings on companies’ career boards—but they won’t tell you which companies have just started hiring across the web. Start with a list of known employers and their board identifiers, save dated snapshots of each board, and compare records over time. A first appearance means “newly observed by your tracker,” not necessarily a newly created role or a company beginning to hire.
What these APIs can—and cannot—tell you
Each API exposes postings for a known employer board. The reviewed official documentation does not describe a universal endpoint that finds every company using these systems or maps company names to board identifiers. Finding board identifiers is a separate step: maintain an employer list and record each company’s ATS, board token or name, and career-board URL.
As an Amazon Associate I earn from qualifying purchases.
A timestamp is a clue, not proof of hiring intent. A role first seen in your data may have existed before monitoring began. A changed timestamp may reflect an edit to an existing requisition. Reposts, duplicate location listings, changing identifiers, prospect posts, and evergreen roles can also complicate the meaning of “new.” Unless the available evidence establishes more, label results “newly observed” or “recently updated.”
Free tools Windows power users keep installed
One-click scans. No signup required.
How the three APIs differ
| Platform | Board identifier and endpoint | Timestamp and meaning | Visibility and useful fields |
|---|---|---|---|
| Greenhouse | Employer’s Job Board URL token. GET /v1/boards/{board_token}/jobs | updated_at indicates a job post’s update time; it does not prove the role is new. |
Public GET data covers published job-board posts. The post id uniquely identifies the job post; internal_job_id identifies the job and may be null for prospect posts. Records include title, location and absolute_url. Add ?content=true for full content, departments and offices. |
| Lever | Employer’s Lever site identifier. API base: https://api.lever.co/v1; list endpoint: GET /postings. |
Returned fields are createdAt and updatedAt. Filters are named updated_at_start and updated_at_end, using inclusive Unix-millisecond values. |
Filter for published postings and public distribution. Records also expose state, distribution channels, categories and job URLs. Follow urls.show or urls.apply to the employer-hosted listing or application. |
| Ashby | The job-page name at the end of the employer’s hosted board URL. GET /posting-api/job-board/{JOB_BOARD_NAME} | publishedAt is the ISO datetime when the job was last published; it is not necessarily the date a role was first created. |
The public Job Postings API returns currently published postings. Check isListed: a false value means the posting is available only by direct link, not normally listed publicly. Records can include isRemote, workplaceType, locations, team, department, jobUrl and applyUrl. Add includeCompensation=true for compensation data when available. |
These differences matter when you normalize data: preserve each provider’s original fields and semantics rather than treating every timestamp as an interchangeable “posted at” date. Greenhouse’s Job Board API is a public-board export, distinct from authenticated internal-data APIs such as Harvest. Greenhouse Job Board API documentation and Greenhouse API overview describe the public endpoints and fields.
#1 Best Overall
Build a tracker that identifies changes reliably
- Make the company list. For each employer, store the ATS, board token or name, and source career-board URL. The APIs begin with a known board; they do not provide a universal company directory.
- Poll each board and save the response. Choose a schedule appropriate to your use case. The cited documentation does not promise a particular feed update interval or a polling cadence suitable for every implementation.
- Normalize without discarding source data. Map provider, posting identifier, title, location, public URL, visibility or status, and timestamps into a common record. Retain the original provider fields or payload so you can audit what changed.
- Normalize times to UTC. Convert timestamps to a consistent timezone before comparing them. For Lever’s update filters, convert the desired window to Unix milliseconds and use the exact parameter names
updated_at_startandupdated_at_end; both ends are inclusive. - Compare with the last successful snapshot. A record absent from the prior snapshot but present now is newly observed by your tracker. A later timestamp on the same identifier indicates an update. Neither observation alone proves a newly opened requisition.
- Deduplicate carefully. Use stable provider identifiers, not title alone. Greenhouse distinguishes the post
idfrominternal_job_id; a prospect post may not have an internal job ID. Treat changed identifiers and multiple location entries as cases to investigate rather than automatically assuming they are separate new jobs. - Check whether the role is publicly listed now. Use Greenhouse’s public job-board data; for Lever, retain published postings intended for public distribution rather than internal, draft or closed records; for Ashby, exclude
isListed: falsefrom a directory intended to show normally listed jobs. - Link to the employer’s listing. Use Greenhouse’s
absolute_url, Lever’s show or apply URL, or Ashby’sjobUrlorapplyUrl. If freshness matters, recheck that page before describing the role as open.
Platform-specific checks before reporting an opening
Greenhouse: distinguish the post from the job
The public list endpoint returns a simple JSON representation of an organization’s offices, departments and published jobs, and its GET endpoints do not require authentication. Use the employer’s board token from its Job Board URL. The post id is the stable identifier for that job post; internal_job_id refers to the job itself and can be null for prospect posts. An updated_at change tells you the post changed, not that the employer created a new requisition. Use absolute_url for the employer’s page, and request ?content=true only when full description content, departments or offices are needed. Greenhouse Job Board API
Lever: filter by state and distribution
Lever’s posting records can have states including published, internal, closed and draft; organizations using approvals may also encounter pending and rejected. Published does not by itself guarantee public visibility: distribution settings determine whether a posting appears on public and/or internal sites. For public discovery, request published postings and verify public distribution. The list endpoint includes all posting states unless filtered. Returned timestamps use camel case—createdAt and updatedAt—while update-window filter names use underscores and milliseconds: updated_at_start and updated_at_end. Team, department, location, commitment and tag filters are case-sensitive. An update-window query can make incremental polling more efficient, but it is not a definitive detector of newly created jobs. Lever developer documentation
Rank #2
- Professional design: Slim and sleek, luxurious looking portfolio provides more confidence and will lead to more success in the meeting, proposal, presentation, interview, or making a sales. A handy memo pad is included in the portfolio so you will have access to write any notes anywhere as you go.
- High quality material: Made by superior quality of PU leather in a matte finish provides a more professionalism looking.
- Graduation gift: A great gift to the newly graduate students looking for their first job, with this portfolio it will lead them to a more successfully career during their interviews.
- Versatile organize: Looking for a portfolio that would fit everything on the go? A business card, a flyers, a pen / pencil, an employee ID card, a passport, or a document pocket. Our portfolio has all the pockets you need no matter if you running errands, meetings.
- Travel friendly: This padfolio binder is lightweight and compact and it is easily fits into briefcares and bags. Making it the perfect accesorry for on the go professionals.
Ashby: separate published from listed
Ashby labels its public Job Postings API documentation v2026-01-01 and says the API returns currently published postings for an organization’s job board. Its publishedAt field is the ISO datetime when a job was last published. A posting with isListed: false is available only by direct link, so do not present it as a normally listed public opening. Compensation is optional, and other employer data may be empty. For an external careers page, Ashby’s help guidance describes retrieving openings through the lightweight JSON API and linking to the hosted application form. Ashby Job Postings API and Ashby guide to building a careers page
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Describe results without overstating them
- Newly observed: the posting appeared in your current snapshot but not in the prior successful snapshot. This describes your tracker’s observation, not the employer’s creation date.
- Recently updated: the provider’s timestamp is later than in your earlier record. This says the posting changed or was republished according to that field’s semantics, not that hiring just began.
- Currently listed: the provider’s current response and visibility fields indicate the job is publicly listed. For a time-sensitive claim, confirm the employer page as well.
- Newly opened role: use this stronger wording only when you have evidence beyond first observation or an update timestamp that establishes the role was newly opened.
Keep the date and time of each successful snapshot, the provider timestamp, and the employer URL. That makes it possible to explain what you know and how you know it, while leaving uncertain cases qualified.
Quick Recap
Best Value
Rank #4
- 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 #3
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.

