Lever: 'Hired' not exposed in the API response when fetching archive reasons using GET /archive_reasons endpoint
Timeline of updates
- resolved
This issue has been resolved.
From Lever’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.lever.co (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Lever, started 2020-12-08 23:18 UTC, resolved after 3.8 h, 1 update(s).
- Title
- 'Hired' not exposed in the API response when fetching archive reasons using GET /archive_reasons endpoint
- Vendor
- Lever
- Date
- URL
- https://rewindex.com/company/lever/incidents/kv5g34jcxpl2
Lever profileRecent Lever incidentsAll outages on December 8, 2020Lever in December 2020MarkdownJSON