The culmination of nearly two years of work

OpenAPI 3.0 is here — Important milestone in the growth of the API economy

Gabriela Motroc

© Shutterstock / Lightspring

The Open API Initiative, a Linux Foundation project created to advance API technology has reached a new milestone. After nearly two years of work, version 3.0 finally saw the light of day. One of the highlights of this release is “its ability to drive the full API lifecycle” but there are a lot of new updates and capabilities that deserve your attention.

The Open API Initiative (OAI) was announced in November 2015. Tony Tam, VP of Swagger Products at SmartBear wrote in a blog post announcing the project that “Swagger’s parent SmartBear Software has organized the Open API Initiative under the Linux Foundation,” and was donating the Swagger Specification to the group.

From here, the OAI group will help evolve the specification in an open and collaborative fashion, adhering to a short but important set of core values. Open, Collaborative, contribution-driven, pragmatic, extendable, stable and neutral.

OpenAPI Specification 3.0

“OAS 3.0, which is based on the original Swagger 2.0 specification, is meant to provide a standard format to unify how an industry defines and describes RESTful APIs,” Swagger revealed in a post announcing the release. “The release of OAS 3.0 marks a significant milestone in the growth of the API economy — bringing together collaborators from across industries, to evolve the specification to meet the needs of API developers and consumers across the world in an open and transparent manner.”

Here are some of the updates and capabilities included in this release:

  • The overall structure of the specification was refactored for better reusability
  • Added Support for describing callbacks
  • Links to express relationships between operations
  • The JSON schema includes support for: oneOf, anyOf and not
  • Improved parameter descriptions, including the ability to use a schema
  • Better support for multipart document handling
  • Cookie parameters are in; dataForm parameters are out
  • Body parameters have their own entity
  • Better support for content-type negotiation
  • The security definitions have been simplified and enhanced

The release of this third-generation format is a significant milestone for our community. The updates made are entirely user and usage driven and that plays a huge role in the success of the specification. One of the most powerful things about this release is its ability to drive the full API lifecycle.

Ole Lensmar, CTO, SmartBear Software and Chair of the OAI Board  

New resources, training, and documentation on OpenAPI 3.0 will become available in the coming weeks.

Lensmar will be co-presenting a free Swagger training on August 9. If you want to hear more about Swagger and its future, don’t miss it.

To see what’s new in OAS 3.0, check out the OAI 3.0 documentation on GitHub.

Gabriela Motroc
Gabriela Motroc was editor of and JAX Magazine. Before working at Software & Support Media Group, she studied International Communication Management at the Hague University of Applied Sciences.

Inline Feedbacks
View all comments