the claudemon api
release notes from five ai developer tools, in one consistent feed.
your first request
get the three newest releases. each record keeps its original notes, source link and date provenance.
base URL https://claudemon.com/api/v1
curl "https://claudemon.com/api/v1/releases?limit=3"JSON over HTTPS. newest first. no setup required.
build your feed
choose what you follow, then run a real request. your filters are saved in this page’s URL.
ready when you are. no request has been run.
response
source freshness
last successful ingestion, separate from each release’s publication date.
four endpoints. one feed.
| method / path | returns |
|---|---|
GET /api/v1/releases | paginated releases: { releases, cursor } |
GET /api/v1/releases/latest | the latest release per source |
GET /api/v1/sources | source metadata and ingestion status |
GET /api/health | service health |
know what you’re getting
| source ID | coverage |
|---|---|
claude-code | Claude Code changelog |
codex | stable Codex CLI releases |
cursor | Cursor changelog |
gemini | stable Gemini CLI releases |
grok | Grok API release notes |
coverage follows official exposed history, with gaps where upstream dates or records are unavailable. Gemini and Grok coverage does not include their consumer chat apps.
pagination
pass the returned cursor unchanged, keeping the same source and since filters. repeat source to include multiple sources. stop at cursor: null. older undated historical imports follow the live feed.
dates with context
date_kind distinguishes publication from first seen. calendar-only dates use UTC midnight, not a precise release time. since filters publication dates; it is not a complete sync mechanism for edits or late discoveries.
poll politely
public API responses cache for five minutes. poll no more often than that, and send the previous ETag in If-None-Match to reuse an unchanged response on 304. cache age is not upstream freshness; check source ingestion timestamps separately.
keep the original
link back using url. body_md is untrusted upstream text: escape it or sanitize rendered Markdown before displaying it.
errors you can handle
check the HTTP status before reading data. invalid filters or cursors return 400; errors use one JSON envelope.
{ "error": { "code": "invalid_source", "message": "Unknown source." } }illustrative error response; see the reference for exact messages.
api changes
· v1 documentation
interactive explorer, OpenAPI reference and conditional requests. existing v1 paths and response fields stay compatible. clients should tolerate new fields; breaking contract changes require a new API version.