API DOCUMENTATION / CURRENTNESS, STATUS, AND CHANGES
Currentness, status, and changes
Separate currentness, stale state, source posting status, application checks, and change-feed events.
Three different status fields
| Field | Interpretation |
|---|---|
currentness | Published projection value: current, uncertain, or not_current. Default filter is current. |
stale | Separately published boolean. This API source does not calculate or define a staleness threshold. |
posting_status | Source-posting presence such as listed or no_longer_listed; it does not prove that applications are open. |
latest_application_check | Nullable observation field when included in the posting shape; it is not a guaranteed availability signal. |
The changes endpoint
GET /v1/jobs/changes returns created, updated, and expired event pages from a timestamp or resume cursor. It may return 503 if its projection is unavailable or changes during a request.
Timestamps are distinct
source_posted_at, first_seen_at, job_first_seen_at, curated_at, job_updated_at, and last_completed_fetch_at describe different records or events. Use the freshness guide to avoid treating them as interchangeable.
Preserve state for review
When building a client, keep currentness and source posting status as separate values. Make uncertain or missing states visible, and retain the source link so an operator can verify the record. The API source does not establish the upstream algorithm that assigned a published currentness flag.
Continue in the reference
Check related request behavior before you build.
View route status and methods Discuss API requirements