Endoflife Date Scraper
Pricing
from $2.99 / 1,000 results
Track software lifecycle and end-of-support dates instantly. Filter by product, version, or upcoming EOL windows and export clean JSON, CSV, or Excel dat
all_products loads every product on endoflife.date with its full release-cycle data (cycle, releaseDate, eol, latest, support) so rows are populated, not blank. product_cycles loads release cycles for only the slugs you list. single_cycle loads one cycle per product. eol_soon keeps cycles whose EOL date falls within eolWithinDays.
Product slugs from endoflife.date, one per line. Used by product_cycles, single_cycle, and eol_soon. Ignored for all_products. Example: python.
Release cycle names for single_cycle, one per line. Each product is requested with each cycle. Example: 3.12.
For eol_soon, keep a cycle when its EOL date is today or at most this many days ahead. Past dates and boolean EOL flags are left out. Default 180.
Maximum data rows to save this run. Hard cap is 1000. Error rows do not count toward this limit.
Seconds to wait between API calls. Default is 1 so the run stays near one request per second. The public API does not publish a rate limit.
User-Agent sent on every request. Keep an app name and a contact address so the host can tell who is calling.
Stop starting new requests after this many seconds and keep rows already collected. Default 300. Maximum 3600.
How long to wait for one endoflife.date response before treating that call as failed. Default 30 seconds.
