Want to take your API to the next level? Then you should give your API an OpenAPI spec! An OpenAPI spec is more than just documentation — with it, you can leverage your API to generate client code, do automated testing and more! During Kong Summit, Wordnik Founder Erin McKean gave an overview of the universe of OpenAPI tooling and showed how to go from zero to OpenAPI spec in just a few straight-forward steps! Watch the talk recording below to hear about all the amazing things that you can do with an OpenAPI spec.
Hear more talks like this at Kong Summit 2019. [Grab your Super Early Bird tickets before July 31st](https://konghq.com/kong-summit)Grab your Super Early Bird tickets before July 31st!
Sign up to receive updates and watch the presentations on the [Kong Summit page](https://konghq.com/kong-summit)Kong Summit page. We'd love to see you in 2019!
Local-first: your data stays with you: Insomnia stores everything on your machine by default. No forced cloud sync, no account needed just to send a request. This is helpful if privacy or working in a regulated environment is a priority for you Fre
[](https://konghq.com/blog/engineering/migrating-collections-and-requests-from-postman-to-insomnia)
The goal of Integration Platform as a Service (iPaaS) is to simplify how companies connect their applications and data. The promise for the first wave of iPaaS platforms like Mulesoft and Boomi was straightforward: a central platform where APIs, sys
[](https://konghq.com/blog/engineering/kong-and-polyapi)
This is part of a 3-part series on APIs, sustainability, and climate change. Check out part 1 on managing a greener API lifecycle, and part 2 on ways to embed and innovate on top of third-party APIs to make greener products. In this final part
[](https://konghq.com/blog/enterprise/the-environmental-impact-of-common-architecture-patterns)
The API management space is changing - fast. In the past couple of years alone, we've seen huge changes in the deployment patterns that our customers are adopting. In the past, when the use cases were fairly simple, organizations would deploy an
[](https://konghq.com/blog/enterprise/kong-vs-apigee-flexibility)
In our last blog post , we discussed the evolution of APIs from early computing to the PC era. In this post, we'll discuss the evolution of APIs in the early internet age. Along the way, we'll touch upon associated core technologies such as eXtens
[](https://konghq.com/blog/enterprise/evolution-apis-rpc-soap-xml-part-2)To work and live in today's digital world, we are unquestionably dependent on interconnected applications . These applications might be massive and highly complex, but they're also constructed from reusable building blocks, which we call an Applica
[](https://konghq.com/blog/enterprise/evolution-apis-rpc-soap-xml)
Organizations scaling their event streams usually run into the exact same pattern of chaos: Security policies become inconsistent across teams. Data contracts drift or break silently in production. Observability is totally fragmented. Governance bec
[](https://konghq.com/blog/enterprise/practical-guide-to-governing-real-time-data)