are we at with OpenAPI • Current usages and tools • What’s up with OpenAPI at runtime • Use cases • API Gateway support • What can we do better • Live demo • Takeaways and questions
Specification (OAS) defines a standard, programming language-agnostic interface description for REST APIs, which allows both humans and computers to discover and understand the capabilities of a service Use cases for machine-readable API definition documents include, but are not limited to: interactive documentation; code generation for documentation, clients, and servers; and automation of test cases. — OpenAPI Official Repository
source for verification client.pets.list() GET /api/pets HOST: petstore.com Accept: application/json • Most used endpoints • Most failing endpoints • Most common scenarios
questions • Tooling hasn’t caught up yet with OpenAPI 3.0 • Implementations difficulties • OAS3 is not yet spread • OAS2 is good enough • OpenAPI aren’t a first class citizens for API Gateways • They just do not care of its support • Not the right tool for the job • OpenAPI documents alone aren’t enough to describe all the aspects of an API • OpenAPI specifications need to be expanded