A Year After OpenAPI 3.2, Most API Tooling Cannot Read It

Earlier this week I wrote that one in ten API providers still publish Swagger, and that OpenAPI 3.2 shows up for five companies out of 2,281. I ended that post saying versions are mostly set by defaults, and that if the community wants 3.2 adopted, the place to win it is the tooling, not the provider’s roadmap. So I went and looked at the tooling.