Skip to content
Free API Today

endoflife.date API

Release cycles and end-of-life dates of software products.
Status
Working
API key
Not needed
Browser calls
Runs in the browser
Latency
438 ms
Docs
endoflife.date ↗

Build snapshot, not live. One verifier run on , from the machine that built this site. How we check

Example request

GEThttps://endoflife.date/api/nodejs.json

Sent from your browser straight to endoflife.date. No proxy: this site never sees the request or the answer.

Copy the request

Shell
curl -s 'https://endoflife.date/api/nodejs.json'

Response stored by the verifier

This is what endoflife.date answered when the verifier sent the request above on : HTTP 200, application/json. Arrays are cut to two items and long strings are shortened. It comes from the build snapshot.

application/json · stored
[
  {
    "cycle": "26",
    "releaseDate": "2026-05-05",
    "lts": "2026-10-28",
    "eol": "2029-04-30",
    "latest": "26.10.0",
    "latestReleaseDate": "2026-09-22",
    "support": "2027-10-27",
    "extendedSupport": false
  },
  {
    "cycle": "25",
    "releaseDate": "2025-10-15",
    "eol": "2026-06-01",
    "latest": "25.9.0",
    "latestReleaseDate": "2026-04-01",
    "lts": false,
    "support": "2026-04-01",
    "extendedSupport": false
  }
]

Availability

Up 1 of 1 day checked · 30-day window

What counts as up for this API: an answer within five seconds, a 2xx status, and the body must be a JSON array with at least one item.

Last check: — passed, HTTP 200 in 438 ms.

The check runs from our infrastructure, not from where you are. If you need certainty, send the request yourself above. How the verifier works.

Questions

Does the endoflife.date API need an API key?

No. The sample request on this page was answered without a key, token or account.

Can I call the endoflife.date API from the browser?

Yes. endoflife.date answered our verifier with an Access-Control-Allow-Origin header on Oct 3, 2026, so a fetch call from a web page can read the response.

Is the endoflife.date API working?

At the check on Oct 3, 2026 it returned HTTP 200 with the expected data in 438 ms. The status at the top of this page shows the most recent result we have.