Skip to main content
Version: 1.0.0

The OAS is more than documentation

Building the API and SDK together gave me a new appreciation for the role of the OAS file.

Before this project, I mostly thought of an OAS file as something used to generate API reference documentation. But I learned that it can connect multiple parts of the developer experience. The same specification can power:

  • API documentation
  • SDK generation
  • Validation tools
  • Code examples

It also made the idea of a source of truth more concrete for me. When multiple developer tools depend on the same specification, keeping that specification accurate and complete becomes part of maintaining the overall developer experience.