Adopting an API First Approach with OpenAPI 3.0

Topics covered in this video include:
What is the API First approach to building applications?
What does it take to adopt API First methodology?
What is the OpenAPI Specification (OAS), and what are the newest features of OAS 3.0?
How can OAS 3.0 accelerate API development, testing, documentation and delivery in the API First approach?
Real world example of design an actual OAS interface for an API

This is why an API-first approach is a refreshing approach to developing products. The API-first approach makes an API the first interface built for an application. The approach forces people to build an API that provides high value to the target audience, before building a product on top of it. It enables developers and organizations to minimize product liability and failure, maximize value and prepare for future product success across different platforms and channels.

A big part of adopting the API-first mindset is also design thinking, and formulating a contract-first, or spec-first strategy for your API development. The OpenAPI Specification (formerly Swagger Specification) goes hand-in-hand with an API-first thinking. The OpenAPI Specification enables teams to design a technology-agnostic API interface that is consumer-centric and not application biased, while simultaneously keeping your internal stakeholders in sync. Your OpenAPI interface defines the API’s functionality, and can grow and evolve along with your product.

Adopting an API First Approach with OpenAPI 3.0
This month, we are hosting a free training: Adopting an API First Approach with OpenAPI 3.0. In this training we will cover what it takes to adopt an API First approach to building products from the API’s design, how to position API design into your development workflow using the latest version of the OpenAPI Specification, OpenAPI 3.0, and effectively collaborate on an actual API design in a real world setting using the OAS and SwaggerHub.