[VIDEO] Adopting an API-First Approach with OpenAPI 3.0

[VIDEO] Adopting an API-First Approach with OpenAPI 3.0

This month, we hosted a free training: Adopting an API First Approach with OpenAPI 3.0. In this training we  covered 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.

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.

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.

You can watch the full recording of the webinar below. You can also download a copy of the slides here.

 

Here is an overview of what was covered, with details for where we covered each topic in the webinar:

  • What is the API-first approach? [1:30]
  • Benefits of adopting an API-first approach [8:05]
  • Guidelines for adopting an API-first approach [14:20]
  • The role of OpenAPI 3.0 in an API-first approach [24:40]
  • Implementing an API-first approach with OpenAPI [31:50]
  • Designing an API with OpenAPI 3.0 in SwaggerHub [34:30]
  • Q&A and additional resources [53:00]

Start designing and documenting APIs with OpenAPI 3.0 today. Try SwaggerHub.