Time fields
All times are UTC, written as ISO 8601 (2026-10-12T14:31:07Z). Filters accept the same format; a time without a zone is read as UTC, and a bare date means midnight UTC.
| Field | Set by | Meaning |
|---|---|---|
| date_posted | Employer | The posting date the employer published. Null when the source doesn't give one. Some sources publish only a date, shown as midnight. Filter with date_posted_gte / date_posted_lt. |
| date_created | Us | When we first collected the job. Always set and never changes. The feed windows and date_created_gte / date_created_lt use it. |
| date_valid_through | Employer | The closing date, when the employer published one. |
| date_modified | Us | On /v1/modified-ats only: when we detected the latest change to the job's published content. |
Which one to filter on
- Syncing a copy: use
date_created. Jobs arrive indate_createdorder, so a window you have read never gains jobs later. - Showing "posted this week" to people: use
date_posted, which matches what the employer's site shows.
The two can be far apart. When we add a new employer, all its open jobs are collected at once: their date_created is that day, while date_posted may be weeks earlier. Some employers also re-date postings to keep them looking fresh.
How fresh is the data?
Most boards are checked every hour, so a new posting usually reaches the catalogue within an hour or two of being published. The 1h and 24h windows end at the last full UTC hour (available two minutes after it closes). The search API and changes feed have no such delay.