OpenAPI is an excellent tool for defining an API, yet its often treated as just a documentation tool. In this post I’ll explore how an OpenAPI spec can drive many parts of your API lifecycle.
Backwards compatibility is one of the most crucial factors of when and how to release a new feature. Maintaining a stable API while constantly improving your service is critical - you don’t want to be breaking your API clients every second Tuesday. In this simple example I want to share how fields that are enums (commonly status fields) are crucial parts of your API stability and how changing them is a terrible idea.