What You Need to Know About OAS 3.0

cloud elements officially joined the open api initiative in november last year to continue the momentum behind organizing the world of apis into easy-to-consume api hubs with standardized, machine-readable documentation .

over the past few months, the members of the oai technical developer community (tdc) have been hard at work to make the next version of the openapi specification a reality: oas 3.0.

this week sees the release of the first implementer’s draft of oas v3.0 — officially released as 3.0.0-rc0 — and is a big step forward for the specification.

some of the key changes you’ll see from v2.0 to v3.0 include:

• the overall structure has been rearranged for easier and extended reusability.
• json schema support has been extended to include oneof , anyof and not support.
• the structure of parameters has changed to allow the use of schema in them.
• support for cookie parameters has been added and dataform parameters have been eliminated.
• body parameters were extracted to their own entity.
• support for content type negotiation has been added.
• a new format to allow static linking between responses and future requests has been added.
• simplified and enhanced security definitions of apis.
• a callback mechanism to describe webhooks has been added.

at this point, the specification is feature-complete, and the implementer’s draft is intended to help work through any outstanding issues. we encourage you to get involved by starting to build against oas 3.0 and submit feedback here .