Topic
Two hundred routes, an Express and two FastAPI services, and a Postman collection from 2023. An AST scan reconstructs the real contract, marks honest gaps instead of guessing, and stays repeatable through rescans.
Read articleA curl command captures one request perfectly and everything else not at all. Postman collections capture folders and auth but lose response schemas. Here is a field-by-field mapping, what every converter drops, and a workflow that ends with a maintained spec.
Read articleThe 3.1/3.2 line aligned OpenAPI with JSON Schema 2020-12, made null a real type, and cleared the way for proper content negotiation. Here is what to change in existing specs and how streaming endpoints (SSE) fit into a 3.2 document.
Read articleThree ways to recover a spec from a running codebase: annotations, traffic recording, and AST scanning. We compare what each extracts across eight languages and 28 frameworks, and why honest gaps beat confident guesses on request bodies.
Read articleMost breaking API changes ship silently: a removed enum value, a field turned nullable, a new required parameter, a tightened status code. OpenAPI diffing in CI classifies changes as breaking or non-breaking, blocks the dangerous ones, and turns API review from memory into a checklist.
Read articleModern API docs are a rendered OpenAPI document with search, try-it requests, dark mode, and crawlable HTML. Here is how the hosting options actually compare, from self-hosted renderers to managed portals, and what SEO requires.
Read articleAn OpenAPI document is already a tool catalog. Here is how operations become MCP tools, how auth and streaming map across, and what breaks when you point a generic converter at a real spec.
Read articleTypeScript clients from OpenAPI split into three camps: types-only, fetch wrappers, and full SDK generators. They differ in runtime weight, enum handling, and how they break on spec changes. Here is how to choose and wire the winner into CI without generated-code sprawl.
Read articleWebhooks are reverse APIs: your server is the client, so the documentation has to cover payloads, delivery ordering, retries, signature verification, and endpoint registration. OpenAPI 3.1 made webhooks top-level citizens — here is a complete, consumer-ready webhook definition.
Read articleEvery API invents an error envelope once; integrations then handle a bespoke format per vendor. RFC 9457 Problem Details is the machine-readable standard, and it extends cleanly to validation and multi-error responses.
Read articleThe field changed in code, in chat, and in the HTTP client while the docs waited for someone to care. A local OpenAPI file in version control gives the whole team one contract to diff, review, and trust.
Read articlePostman collections, mock servers, docs generators and MCP glue all drift the moment the spec stops being the source of truth. Powerduck keeps one local OpenAPI file at the center.
Read article