API changelog examples: 5 real ones, checked today
Five public changelogs of APIs that were live and current on 18 November 2026, each with what it does well. Then an update FoxPlug wrote from a real repository of the same kind, and a box to write yours from your own repository.
5 real API changelogs
Each line under a name is measured from the page text on 18 November 2026: the number of dated entries counted, whether kind words such as added or fixed appear repeatedly, whether they link their pull requests or issues, whether a feed is linked. It is a count, not an opinion.
1. Stripe API
- 253 dated entries on the page, the newest 28 October 2026
- kind words appear repeatedly in the entries (added, new, improved, improvements)
2. Slack API
- 172 dated entries on the page, the newest 17 November 2026
- kind words appear repeatedly in the entries (added, new, improved, improvements)
3. Cloudflare
- 9 dated entries on the page, the newest 18 November 2026
- kind words appear repeatedly in the entries (added, new, security, performance)
- a feed you can subscribe to is linked in the page
4. GitHub
- 12 dated entries on the page, the newest 17 November 2026
- kind words appear repeatedly in the entries (new, security)
- a feed you can subscribe to is linked in the page
5. Sentry
- 10 dated entries on the page, the newest 12 November 2026
- kind words appear repeatedly in the entries (new, performance)
Read and left out: Shopify developer (robots.txt disallows a plain read); Plaid (robots.txt disallows a plain read); Google Maps Platform (robots.txt disallows a plain read); Mailgun (answered 404); Algolia (only 0 dated entries found in the page).
How a page got on this list
We read the public page once on 18 November 2026, honouring the site's robots.txt. A changelog stays only if the page answered, showed at least three dated entries, and its newest entry is no more than 120 days old. A page that failed any of those is not listed, so every link above was live and kept up on the checked date. Changelogs change; the date on each entry is the day we read it.
An update FoxPlug wrote for a API
FoxPlug read the public repository strapi/strapi on 18 November 2026 and wrote this. The words below are unedited; nothing was posted anywhere.
Strapi 5.63.0: stricter filter validation and applied empty $in filters
Filters that used to drop the condition and return every entry now return a 400 ValidationError. This covers a plain object as an operator's operand on a scalar or JSON field, id or documentId, such as filters[meta][$eq][a]=1, and $or or $and lists longer than the strapi::query middleware's arrayLimit, 100 by default, or with an index of 100 or more such as filters[$or][100]. Raise arrayLimit if you need longer lists. Empty $in and $notIn filters are now applied: { id: { $in: [] } } returns none, and $notIn: [] returns every entry. If your code builds $in lists that can be empty, check the results it now gets.
Try it on your own project
Free: 1 project, no card needed. Nothing is posted anywhere until you approve it.
More changelog examples
Ship the fix with a changelog your users read
Write what changed in plain words once; FoxPlug publishes the page and feed and drafts the posts, so your users hear it from you first.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with