Job Posting RSS Feeds: Greenhouse, Lever and Ashby URLs

A note before we start. The feed URLs below are public vendor endpoints. JobNotify is one alternative if you do not want to run them yourself. About JobNotify.

It is rarely classic RSS

“Job posting RSS feed” is what people search. What Greenhouse, Lever, and Ashby usually publish is a public JSON list of open jobs. You cannot paste that into Feedly and expect a tidy blog. You poll it, you remember which job ids you have seen, and you email yourself when a new id appears.

That is still the company’s own list. Closer to the source than Google Alerts, and free. The cost is your time. If you wanted “Acme job alerts” and you do not want a script, this is the wrong hobby. Job alerts for a specific company has the non-technical routes.

The URLs people actually poll

Greenhouse’s job board API, JSON, including the description if you ask:

https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs?content=true

The board token is often the slug in job-boards.greenhouse.io/{board_token}. You get title, URL, location, department, an id, and an updated time. No native RSS file sitting next to it.

Lever’s postings API:

https://api.lever.co/v0/postings/{company}?mode=json

The company slug matches jobs.lever.co/{company}. The payload is the current openings, unfiltered. Title, team, location, commitment, URL, time. Filtering is your problem, which is what you wanted if you only care about one kind of role.

Ashby’s public job board endpoint follows this shape:

https://api.ashbyhq.com/posting-api/job-board/{JOB_BOARD_NAME}

The name usually matches jobs.ashbyhq.com/{JOB_BOARD_NAME}. Same idea: JSON you poll. Workday, for job seekers, usually has nothing like this. Those career sites expect an account and a saved search, not a feed. Does Workday have job alerts?

How you avoid repeat mail

Fetch the URL. Pull each stable id. Store yesterday’s ids. Mail only the ids you have not stored. Then save today’s set. If you skip the store, every edit or reorder looks like a new job, and you will mute your own script by Thursday.

# Greenhouse
board_token="acme"
curl -s "https://boards-api.greenhouse.io/v1/boards/${board_token}/jobs?content=true"

# Lever
company_slug="acme"
curl -s "https://api.lever.co/v0/postings/${company_slug}?mode=json"

# Ashby
JOB_BOARD_NAME="acme"
curl -s "https://api.ashbyhq.com/posting-api/job-board/${JOB_BOARD_NAME}"

A bridge such as RSS-Bridge can wrap the JSON into XML for a feed reader. Zapier, Make, or n8n can poll and send mail. A tiny scheduled script is the most flexible, and the thing you will forget to fix when the endpoint shifts.

When to skip the project

Skip it when the company is on Workday, when your list spans several kinds of careers sites, or when you do not want a thing that can fail quietly. A dedicated watcher, JobNotify or a peer such as OpenJobRadar or JobBeacon, trades the script for their checks. Generic page tools such as Visualping are a third path, with more noise. The tool roundup compares those shapes. None of them change where you apply: still their site.

If the feed idea was only a way around a missing button, you can also just watch the company. When a company has no job alerts.