Get Blocklist Schedule
Changed onWhen the blocklists are regenerated: the configured interval, the last run of the generation job, the newest list's lastUpdated, and when the next run is expected. The job runs on an interval placed relative to its last run, not at a fixed hour of the day.
expectedNextRunAt is startedAt + intervalHours after a success, and intervalHours after the end of a failed or timeout run. It is null — the next run cannot be dated from outside the worker — while a run is running, after an interrupted one (the worker retries it shortly after its next start), with no run history, or with the scheduler off. overdue is true once now is more than an hour past expectedNextRunAt.
No authentication required. Not metered.
Per-IP ceiling. 120 requests a minute per IP (per /64 for IPv6), shared by /stats, /blocklist/stats, /blocklist/schedule, /analytics, /cve/stats/epss, /cve/stats/timeseries and /license, with or without a key. Over it, 429 with Retry-After. Computed on each call.
Request
- Base URLhttps://api.ismalicious.com
- Authnone required
Response
The regeneration schedule
Example response
{
"expectedNextRunAt": "2026-11-08T15:12:04Z",
"expectedNextRunBasis": "armedTick",
"intervalHours": 12,
"lastRegeneratedAt": "2026-11-08T03:41:19Z",
"lastRun": {
"completedAt": "2026-11-08T03:41:19Z",
"initiator": "interval-scheduler",
"startedAt": "2026-11-08T03:12:04Z",
"status": "success"
}
}Changes
- info
endpoint added
- info