My latest post on TheNewStack is about how to handle those large OpenAPI files without losing your mind: https://thenewstack.io/openapi-how-to-handle-file-management/
Change the fields returned by your API by offering more representations of the resources. This under-appreciated feature of API design can help teams to get the best from their API for multiple use cases, without the need to switch to GraphQL. Continue reading →
API reference documentation changed the way we built integrations, and eventually became part of the driving force for OpenAPI adoption and all the good tooling that flowed from it. As a developer experience specialist, I spend a lot of time … Continue reading →
Back with the PHP Community for the first time in a while at PHPUK! This talk is about OpenAPI specifically for backend developers, and covers some common scenarios that might be familiar to you, along with some suggestions for what … Continue reading →
I’ve been using Optic’s CLI, an OpenAPI tool that does a bunch of things including diffing OpenAPI descriptions and comparing HTTP traffic with OpenAPI. My use case was an established API that didn’t have an OpenAPI file yet – using … Continue reading →
The API DevTools space is alive and well with lots of new and exciting products popping up all the time. I’ve been especially impressed by the new tools in the docs space, but some of the options are less practical … Continue reading →
Returning to the “all the APIs” track at FOSDEM with my talk “OpenAPI Landscape” covering the OpenAPI, Arazzo and Overlay releases from the last year. Video, slides and feedback links are here: https://fosdem.org/2025/schedule/event/fosdem-2025-5233-the-openapi-standards-landscape-a-year-of-innovation/
In a recent project around open source contributors, I wanted to take a look at which projects a particular user (actually a few of them, but I wrote a wrapper to repeat the process for each handle) maintains. GitHub doesn’t … Continue reading →
For teams that generate OpenAPI from their codebase, there’s a tough choice between maintaining rich and extensive content such as Markdown descriptions and examples in codebase annotations, or in making those changes to the generated file – and then losing … Continue reading →