The API Digest

Last reviewed on 4 May 2026.

A monthly editorial digest of what's happening in the web API world. Curated, opinionated, dated. The aim is to surface the substantive changes that working API developers should know about, with enough context to skip what doesn't apply and dig into what does.

What goes in

Each issue covers, roughly:

  • Standards activity. What's moving in the IETF, W3C, OAuth, OpenAPI, and GraphQL working groups. Drafts that are progressing, RFCs that have published, debates worth following.
  • Major vendor releases and deprecations. Significant API changes from the cloud providers, identity providers, payment processors, and SaaS platforms that working developers integrate against. Filtered for substance, not just announcements.
  • Notable incidents. Public postmortems published in the past month that are worth reading, with a short summary of why.
  • Tooling and ecosystem. New or substantially-changed open-source tools in the API space — testing tools, gateways, OpenAPI tooling, mocking libraries.
  • Worth-reading. Pieces published in the past month that we'd recommend, with a paragraph on each.

What we skip: routine product announcements, conference recap blog posts that don't add new information, vendor marketing dressed up as engineering content.

Issues

Issue May 2026

May 2026 — The first issue

The structural framing for this digest, plus a few notes on currently-active standards work and recently-published API tooling.

How this differs from "API news" sites

There are several aggregator-style API news sites and newsletters. They serve a different purpose: they aim for breadth, listing as many announcements as possible. This digest aims for the opposite — to filter aggressively. The unit of value is "I can skip every other API news source for the month and still know the things that matter."

The cost is that we miss things. Some readers will find an item missing that they considered important. The mechanism for that is the contact page; missing items get folded into the next issue if they meet the bar.

Why monthly

Weekly digests of API news mostly contain noise. The substantive changes — RFCs publishing, major vendor migrations, notable incidents — happen at a rate of a few per month, not a few per day. A monthly cadence is long enough to filter out the noise, short enough that the items haven't already been digested everywhere else.

Where to go next

For the long-form pieces that the digest sometimes points toward, see the blog. For the deeper reading list of foundational pieces in API design, see the canon. For the public-incident analyses that some digest items will reference, see the postmortem readings.