The issue? When updating the schema, users were required to recreate their collections (and any associated mocks and monitors). We noticed a recurring workflow in which many of our users would import their OAS documents into Postman, convert them to collections, and proceed to use Postman for mocking, monitoring, and publishing documentation. Use case #1: Validating and syncing during development In particular, we addressed challenges in four specific workflow use cases that involve OAS and have made a big difference for our users. APIs are a big part of how software is built today, and we’ve been closely following the trends around the API ecosystem-including the OpenAPI Specification (OAS)-for the last six years to help us pursue this mission.Īs part of this pursuit, we’ve been keenly listening to our customers and making regular improvements to our support for various schema formats: We started with Swagger 2.0 in 2015, and we recently added support for OAS because we noticed increasing adoption of the specification and how it unlocks new possibilities. Īt Postman, our mission is to encourage creativity by providing user-friendly tools that help people create innovative software. This is a follow-up to our recent post about Postman joining the OpenAPI Initiative (OAI).
0 kommentar(er)
