DEVELOPER API
Read lifecycle records with their uncertainty
The v1 API exposes published records, variant identifiers, separate OS/security dates, precision and evidence metadata. It is a read interface, not a safety-certification feed.
List and search
GET /api/v1/devices?q=Pixel%208&limit=25&cursor=…
Results are ordered by the same exact-name-first search used by the site. Limits are 1–100. Follow meta.nextCursor until it is null.
Single record and evidence
GET /api/v1/devices/google-pixel-8
GET /api/v1/devices/google-pixel-8/evidence
The evidence endpoint separates lifecycle assertions from sources, recall review, repairability and revision history so consumers do not have to infer provenance.
Public dataset
Download the device support dataset (CSV)
Download records with a 2026 security-support date (CSV)
Downloads the published catalog, or one support-ending year, as UTF-8 CSV. Attribution is required, and source-page rights remain with their publishers; the export contains links, not copied source content.
Year filters include explicit dated minimum commitments as well as other recorded support dates. Minimum values remain in their separate columns; they are not converted into final update dates.
Each row includes the model and region, security and OS support dates, date precision, evidence level, source link and checked date. Support-date meaning and minimum-support fields preserve the scope of each commitment.
Public dataset license v1 · effective 6 September 2026. You may reuse the exported factual fields with visible DevLifeCheck attribution and a link to the canonical device record. This license does not transfer rights in linked source pages, publisher text, product images or trademarks. Preserve model, region, evidence, date-precision and source context; do not imply that DevLifeCheck or a cited authority certifies your product or service.
The canonical CSV and API links above are the public distribution endpoints. A source-code repository is not listed until a stable public repository is available.
Embeddable status badge
GET /api/v1/badge/google-pixel-8
The SVG badge reflects the current lifecycle verdict. Link the badge to the canonical device page so readers can inspect scope, evidence and uncertainty.
<a href="https://devlifecheck.com/devices/google-pixel-8"><img src="https://devlifecheck.com/api/v1/badge/google-pixel-8" alt="Google Pixel 8 support status on DevLifeCheck"></a>Rate limits, caching and attribution
Public endpoints allow 20 requests per minute per client. JSON responses include an ETag and accept If-None-Match. Cache headers allow five minutes plus stale revalidation. Consumers must retain DevLifeCheck attribution and the source URLs, checked dates, scope and precision needed to interpret each claim.
Feeds and legacy endpoint
Subscribe to record changes with GET /feed.xml or upcoming documented support endings with GET /support-calendar.ics.
GET /api/devices is a deprecated compatibility wrapper. New integrations must use the bounded, cursor-paginated /api/v1/devices endpoint and follow its metadata.
Responsible use
Do not translate “supported” into “secure,” remove regional caveats, or describe a dated non-match as proof that no recall exists. Cache the last valid result through temporary failures and provide a correction path.