cloudparts

OpenAPI Initiative

The Linux Foundation project that owns the OpenAPI Specification, formerly Swagger, and its companions Arazzo and Overlay: members pay for it, and a small steering committee of maintainers writes the specs.

1 projects in this catalogPart of the Linux FoundationWebsite

What it is

The OpenAPI Initiative (OAI) is a collaborative project of the non-profit Linux Foundation. The LF announced it on November 5, 2015, as the Open API Initiative, with 3Scale, Apigee, Capital One, Google, IBM, Intuit, Microsoft, PayPal, Restlet and SmartBear, which donated the Swagger Specification it had bought that March. On January 1, 2016 the specification was renamed OpenAPI. The OAI now publishes three specifications: OpenAPI, for describing HTTP APIs; Arazzo, for workflows that chain API calls; and Overlay, for patching an OpenAPI description from a separate file. All three are under the Apache 2.0 licence.

Companies join as Participating Members, whose yearly fee depends on headcount and LF membership, from $500 for one with fewer than 10 employees that already belongs to the LF to $45,000 for one with 5,000 or more that doesn’t; open-source projects, non-profits and universities can join free as Associate Members. Each member appoints a representative to the Business Governing Board (BGB), which manages the trademarks and budget. In October 2026 the OAI’s landscape listed 17 Participating Members, among them Google, IBM, Microsoft, SAP, SmartBear, Kong, Tyk, Bloomberg, eBay and the API tool makers 42Crunch, bump.sh, Redocly and Scalar, and 11 Associate Members, including the UK government and the OpenTravel Alliance.

For someone choosing a technology, the badge covers the specification documents and their JSON Schemas, not the tools that read them. Swagger UI and Swagger Editor belong to SmartBear, OpenAPI Generator is an independent community project, and Kiota, Spectral and Redocly each belong to their companies. There are no maturity stages: the OAI has its three specifications plus special interest groups (SIGs), and anyone can join the weekly calls where changes are discussed.

Its projects in this catalog

In depth

Who decides#

The charter, published on the OAI’s governance page, splits the work in three. The BGB, one representative per member, handles trademarks, any certification programme, the budget and its own chair; it aims for consensus and otherwise votes one member, one vote, with Associate Members left out of budget votes. Unresolved BGB disputes go to the Linux Foundation.

The Technical Steering Committee (TSC) creates and maintains the specifications and approves releases, and membership of an OAI member company is not required. All TSC members are maintainers, and its rules cap it at nine: a nominee joins if no more than a quarter of the TSC votes against, then serves six provisional months before a second vote. In October 2026 the maintainers file listed six active members, Jeremy Whitlock, Marsh Gardiner, Lorna Mitchell, Mike Kistler, Miguel Quintero and Ralf Handl, and six emeritus, including Swagger’s creator Tony Tam. A Technical Oversight Board settles conflicts the TSC can’t, with members serving staggered two-year terms.

SIGs do much of the newer work. Since May 2021 they have been informal: a champion, often a Slack channel and a repository, and regular calls. Overlay and Arazzo began in SIGs, and the Moonwalk SIG is designing OpenAPI 4.0; others work on security, code generation, formats and lifecycle, and on OpenAPI in travel and finance.

The three specifications#

OpenAPI

3.2.1, September 2026

Describes an HTTP API’s paths, operations, parameters, payloads and security in one JSON or YAML document. The 3.x line has had three minor versions: 3.0 in 2017, 3.1 in 2021 and 3.2 in 2025.

Arazzo

1.1.0, May 2026

Describes sequences of calls across one or more APIs, and the dependencies between them, so docs, tests and AI agents can follow a workflow deterministically. Version 1.0.0 was published in September 2024.

Overlay

1.2.0, September 2026

A separate document of changes to apply to an OpenAPI description, for translations, per-environment settings or gateway metadata, without editing the source. Version 1.0.0 was published in October 2024.

Where it came from2015–2026

Swagger was started by Tony Tam at the dictionary company Wordnik in 2010, as a way to describe an HTTP API that tools could read; version 2.0 came out in September 2014. In March 2015 SmartBear Software bought it from Reverb Technologies, Wordnik’s parent company.

On November 5, 2015 the Linux Foundation announced the Open API Initiative with ten founding members and SmartBear’s donation of the specification, to create a “vendor neutral, portable and open specification for providing metadata for RESTful APIs”. Apigee called independent governance “the necessary next step”. The specification was renamed OpenAPI on January 1, 2016, and the first version made under the new governance, 3.0, came out in July 2017.

Since then the OAI has moved OpenAPI onto JSON Schema with 3.1 in 2021, set up informal SIGs in 2021 and published two more specifications, Arazzo and Overlay, in 2024. OpenAPI 3.2 followed in September 2025, while the Moonwalk SIG works on a 4.0 with no planned end date.

Why it’s built this way

A vendor-neutral home instead of one company’s format
SmartBear owned Swagger. Putting the specification under the Linux Foundation, with competitors among the founding members, let them build on one format; Restlet said the community should “unite around a common API language”.
Members fund, maintainers decide
The charter gives the board trademarks and money, and the specifications to a TSC that anyone can join regardless of membership, so influence over the text comes from contributing rather than paying.
New specifications next to OpenAPI, not inside it
Workflows and patching came up again and again but did not belong in every API description, so the OAI published them as Arazzo and Overlay, which point into OpenAPI documents and are versioned on their own.

Timeline

  1. 2015

    SmartBear buys Swagger in March; Open API Initiative announced on November 5

  2. 2016

    Swagger Specification renamed OpenAPI on January 1

  3. 2017

    OpenAPI 3.0.0 released in July

  4. 2021

    OpenAPI 3.1.0 released in February; informal SIGs agreed in May

  5. 2024

    Arazzo 1.0.0 published in September and Overlay 1.0.0 in October

  6. 2025

    OpenAPI 3.2.0 released in September

  7. 2026

    Arazzo 1.1.0 in May; OpenAPI 3.2.1 and Overlay 1.2.0 in September

Sources · facts checked 2026-10-28

Improve this page on GitHub