HOME > BLOG > CAREER & JOB SEARCH
CAREER & JOB SEARCH

Job Posting Date: Greenhouse first_published vs updated_at, Ashby publishedAt

11/16/2026
9 min read
Open notebook and pen beside a laptop on a desk
Photo by Nick Morrison on Unsplash

The date on a job ad built on Greenhouse or Ashby isn’t always the date the job was first opened. Greenhouse gives you two date fields, first_published and updated_at. Ashby gives you one, publishedAt. The raw date fields can point to very different moments.

TL;DR:

  • Greenhouse’s docs show first_published and updated_at but define neither (per the Greenhouse Job Board API docs, retrieved 15 November 2026)
  • Ashby documents a single date, publishedAt, as the time the job was last published (per the Ashby Job Postings API docs, retrieved 15 November 2026)
  • On one of the three Greenhouse boards I queried, 435 of 785 jobs had updated_at 30 days or more after first_published (my query, 15 November 2026)
  • In my snapshot, some jobs carried several posts: the docs give them different identifiers, id for the post and internal_job_id for the job
  • My reading: an old date means the posting is at least that old; a recent Ashby date tells you nothing yet

Where the dates come from: two job board feeds

Both vendors serve their dates from JSON feeds that they document for building careers pages. Greenhouse’s Job Board API covers a company’s offices, departments and published jobs, and the docs state: “Job Board data is publicly available, so authentication is not required for any GET endpoints.” Two endpoints matter here. GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs lists all job posts on a board, and GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs/{job_id} retrieves a single post. The docs call board_token a “Job Board URL token” and leave it at that.

Ashby’s Job Postings API is the equivalent. The docs say: “This API allows you to get data for all currently published Job Postings for your organization.” You hit GET https://api.ashbyhq.com/posting-api/job-board/{JOB_BOARD_NAME}, and the docs are explicit: “Your request must include your organization’s Ashby jobs page name in the URL path.” For a board at jobs.ashbyhq.com/Ashby, the name is “Ashby”, the final path segment. Add includeCompensation=true as a query parameter and the response carries compensation data too. The documented request carries no key.

The board with token “greenhouse” is a live example you can hit to see the structure.

Greenhouse: first_published and updated_at

The docs define neither field. The docs’ list-jobs example includes updated_at but not first_published. The retrieve-a-job response includes both, plus company_name and application_deadline. Its prose opens with “Returns a job post.” and then covers only the questions parameter and custom fields. Nothing explains what makes updated_at change.

I queried the live list endpoint on 15 November 2026 across three boards: greenhouse (20 jobs), stripe (785) and airbnb (214). first_published was present on every job. This is my observation, not documented behaviour.

My reading: first_published is the first publish, updated_at some later update. The name does support one inference, though. An old first_published means the post has been out at least that long, which is the number that separates a fresh opening from a listing that’s been sitting.

What updated_at looked like on three live boards

In that snapshot, 1,019 job posts in total, updated_at was never earlier than first_published.

Board (total)< 24 h after first_published≥ 30 days after first_published≥ 180 days after first_published
greenhouse (20)671
stripe (785)13843577
airbnb (214)289724

The 30+ days column is where your decision lives, because it counts posts whose updated_at is a month or more after first_published. On stripe, 435 of 785 is more than half, and it is a large share on the other two boards too (see the table). updated_at isn’t the posting date.

My advice: when the question is when the role opened, read first_published. Treat updated_at as a separate signal, not the date you anchor a decision on.

One job, several posts: id versus internal_job_id

Greenhouse gives you two identifiers per post. “The id field contains the unique identifier for the job post, while internal_job_id contains the unique identifier for the job itself.” You pass the id to the retrieve endpoint to pull a single post. The internal_job_id is shared by posts that belong to the same job.

In my snapshot, internal_job_id was shared by several posts in 2 groups on greenhouse, 22 on stripe and 14 on airbnb. I can’t read those as reposts. Every post in a group had first_published on the same day in 2 of 2 groups on greenhouse, 4 of 22 on stripe and 11 of 14 on airbnb. Groups differed by location in 1, 13 and 6 groups (greenhouse, stripe, airbnb) and by language in 0, 0 and 8. My reading: a group can be parallel posts for other locations or languages.

The gh_jid query parameter in absolute_url equalled the post id on every job: 20 of 20, 785 of 785, 214 of 214. The docs example shows a company careers page with a gh_jid parameter. The match is my observation, not documented behaviour, so don’t build a pipeline on it.

My reading and advice: when a posting looks new, pull the board’s job list, filter by the same internal_job_id and compare first_published across those posts. An older date among them is a lower bound on how long the job has been out, as above. One caveat: the docs say prospect posts have a null internal_job_id, so grouping by it would lump prospect posts together. All three snapshots had zero nulls.

Ashby: what publishedAt means

The docs describe publishedAt as “ISO DateTime when the job was last published”. There’s no created, first-published or updated field; publishedAt is the only date in the documented field table. The example value in the docs is 2021-04-30T16:21:55.393+00:00. The docs don’t say what counts as publishing again.

My reading: if publishedAt is old, the job has been out at least that long. A job can’t be first published later than its last publish, so the date is a lower bound on how long the posting has existed.

The problem runs the other way. A recent publishedAt doesn’t tell you the posting is new. A job published once and a job published more than once produce the same shape of value, and there’s no counter, sequence number or flag to separate them. You get one timestamp and no context for what came before.

When it’s recent, you’re back to the rendered page and whatever else you can find.

A short routine for one posting

To check whether a posting is stale, read the raw JSON straight from the ATS. This is the order I’d follow for a single job before deciding whether to spend time on it.

  1. Find the board token. On Ashby, see the jobs page name above. On the greenhouse board I checked, the token was the first path segment. On the stripe and airbnb pages I checked, the link carried only gh_jid and no token. Trying the company name as the token matched on all three boards; that’s my guess, not a documented rule.

  2. Fetch the list endpoint and pull out first_published and updated_at for that posting and, if first_published is recent, for the other posts with the same internal_job_id. On Ashby, pull publishedAt from the board response instead. Keep the raw values exactly as returned, offset included.

  3. Read the UTC offset before you compare dates. One job on the greenhouse board carried updated_at 2026-11-13T19:00:06-05:00, which equals 2026-11-14T00:00:06Z. That’s already 14 November in UTC and in Lisbon (UTC+0 in November), and 01:00:06 on 14 November in Berlin (UTC+1). Strip the offset and compare the date part naively, and you’ll log 13 November, a full day off.

  4. Read the result against the lower-bound rule in the Greenhouse and Ashby sections above.

  5. Note the date you found and the day you checked. A posting’s age only means something relative to when you looked.

FAQ

Do I need an account or API key to read these feeds?

Greenhouse states that no authentication is required for GET endpoints, and Ashby’s documented request carries no key.

Does a recent updated_at mean the job is new?

No: on the three boards I queried it often landed a month or more after first_published, so read first_published for the opening date (see the table).

What does Ashby’s publishedAt tell me if the date is recent?

Not much: the docs describe the last publish, so a recent value can’t separate a new job from one published again (see the Ashby section).

What if the careers page is hosted by the company and not by Greenhouse?

On the stripe and airbnb pages I checked, the link carried only gh_jid and no board token, so step 1 of the routine suggests a first guess.

Do these dates tell me whether a job is a ghost job?

No. They tell you how long a posting has been out, not whether anyone is hiring. For the wider signals, read our guide to spotting ghost job postings.

Sources

All pages and API responses retrieved on 15 November 2026. The three board responses are live data and change as jobs open and close.

Try Xeito

Save the posting in Xeito and keep the checked date in the job’s notes.


This article is for informational purposes only and does not constitute legal or tax advice. Greenhouse and Ashby can change their APIs and field behaviour at any time; confirm the current behaviour in their documentation before you rely on it.

XT
Xeito Team The team building Xeito

Xeito is built and operated by the team at Abellan Labs, S.L.U., an EU-incorporated software studio. The team builds remote-job tooling for developers in the EU/EEA, drawing on hands-on experience with EU remote-work and self-employment regimes, EU consumer-rights compliance (CRD / LSSI-CE / GDPR), the cross-border tax and social-security paths most relocation guides paper over, and the AI-agent-driven engineering practice — CI/CD, content pipelines, and direct platform integrations — behind Xeito itself.

AMPLIFY

Know a friend job-hunting in the EU?

Xeito filters out the "remote — US only" traps. Share it with anyone who's tired of finding fake-remote jobs in the EU.

SHARE_THE_WEDGE →
READY_TO_START

FIND_YOUR_DREAM_JOB

Join developers across the EU/EEA using AI-powered tools to find remote opportunities