Skip to main content
search
All Posts By

OpenAPI Initiative

May 24
Love0

Karate Labs, Testing Automation Framework, is Joining the OpenAPI Initiative

By Blog

The OpenAPI Initiative, the consortium of forward-looking industry experts focused on evolving and implementing the OpenAPI Specification (OAS), is announcing that Karate Labs has joined as a new member.

5900 GitHub stars | Used by Fortune 500 companies worldwide 

Karate Labs is an open-source solution unifying API & UI test automation including mock-servers and performance testing. Karate’s core of API testing includes sophisticated payload data and schema validation, and a unique capability to re-use API tests as performance tests.

Karate Labs API data importer enables teams to import all leading sources of API data and to preview, edit and export the API sequence using an intuitive no-code user experience.

“With more teams adopting the OpenAPI Specification as a standard, we see the opportunity to align test automation efforts and further accelerate adoption. We are excited to join the OpenAPI Initiative to deliver even more value to our customers,” said Kapil Bakshi, co-founder, and CEO of Karate Labs. “With software products depending more than ever on APIs, the OpenAPI specification has injected more rigor and collaboration into how APIs are designed, implemented, and consumed. Karate Labs aims to simplify test automation for business stakeholders, product owners, and QA specialists.” 

OpenAPI Initiative is always welcoming NEW MEMBERS, find more information about becoming an OpenAPI member here!

Karate Labs Resources:

OpenAPI Resources

To learn more about participating in the evolution of the OpenAPI Specification: https://www.openapis.org/participate/how-to-contribute

About the OpenAPI Initiative

The OpenAPI Initiative (OAI) was created by a consortium of forward-looking industry experts who recognize the immense value of standardizing on how APIs are described. As an open governance structure under the Linux Foundation, the OAI is focused on creating, evolving, and promoting a vendor-neutral description format. The OpenAPI Specification was originally based on the Swagger Specification, donated by SmartBear Software. To get involved with the OpenAPI Initiative, please visit https://www.openapis.org

About Linux Foundation

Founded in 2000, the Linux Foundation is supported by more than 1,000 members and is the world’s leading home for collaboration on open-source software, open standards, open data, and open hardware. Linux Foundation projects like Linux, Kubernetes, Node.js and more are considered critical to the development of the world’s most important infrastructure. Its development methodology leverages established best practices and addresses the needs of contributors, users, and solution providers to create sustainable models for open collaboration. For more information, please visit us at linuxfoundation.org.

May 11
Love0

OpenAPI v3.1 Resources for Tooling Developers 

By Blog

This post is authored by Phil Sturgeon, Green Tech consultant at Green Turtle, and Chairperson, Protect Earth. If you’d like to donate to Phil’s charity of choice, please see Protect Earth which is reforesting the U.K. one field at a time.

OpenAPI v3.1.0 has a bunch of great changes, solving problems like the subtle differences between JSON Schema objects and OpenAPI Schema objects, and adds support for Webhooks.

Upgrading tooling can be tricky, but this should be a lot easier than the jump from v2 to v3.0. To reduce the workload we’ve put together some convenient resources for tooling developers, to provide test cases, examples, and guidance in general.

First of all, these articles will show the differences between v3.0 and v3.1 from a user perspective:

Do you need to support everything?

Some of that content is aimed more at end users and what they will need to do, but what do tooling vendors need to do?

For new features like webhooks, you can think to yourself: does this tool need to support webhooks? If it’s a documentation tool, probably! If the tool is validating incoming web requests to your server, then probably not.

Some tools have gone with a definition of 3.1.0 support which is “a 3.1.0 document will work equally well as a 3.0.0 does in the same tool”, which is a good first step. Then support for other new keywords can be added later.

It’s my opinion that getting 3.1.0 documents to work at a basic level is more important than supporting every single feature in 3.1.0. End-users will create feature requests for the bits they’re most excited about as you go.

JSON Schema consolidation

For the bulk of the other changes, the difference is that instead of using a schema object that is very similar to JSON Schema, the OpenAPI Schema object is now literally JSON Schema. There’s some technicalities involved here and technically OpenAPI Schema has defined it’s own JSON Schema vocabulary, which extends the main JSON Schema vocabulary and adds support for discriminator. As the usage of discriminator in 3.1.0 was clarified to be purely a “hint” or shortcut for an existing oneOf, anyOf, allOf, this can be safely ignored by the vast majority of tooling.

tl;dr: you can use any valid JSON Schema tooling to work with the contents of a schema: object in OpenAPI, which means a lot of tools can phase out reliance on hand-crafted schema inspection code, and leverage any of the existing JSON Schema tooling instead.

For example, if a tool you maintain was manually validating OpenAPI Schemas in JavaScript before, it might be an idea to wrap that in an if ($version == "3.0") statement, use that old logic, deprecate it, then if the version is 3.1 you could leverage powerful tools like AJV or HyperJump to do all the heavy lifting. This immediately benefits your tooling from them doing all the work supporting modern JSON Schema / OAS3.1 keywords for you, like if/then/else.

It also means they can do the heavy lifting for other changes that come as JSON Schema matures into a stable release (although it would be brilliant if you could help them out a too).

Test Cases

To make sure your tooling works with OpenAPI v3.1, you’ll need some OpenAPI v3.1 documents to test against. There is no official list of OpenAPI v3.1 documents around, but there are some example files written by the community which can be used in a test suite to show pass or fail scenarios:

Validation Schema

Many tools use a JSON Schema document that describes valid OpenAPI documents. Yes that is a very meta sentence, but if you know what I mean then you are wondering if there is a new one for OpenAPI v3.1? Good news, there is!

Find Other v3.1 Tooling

To see how other OpenAPI tools are doing take a look at OpenAPI.Tools. Perhaps there is some other tooling you could leverage, or some developers you could team up with, or ask questions to, or hire to work on your thing too, etc.

Don’t forget to send a pull request to OpenAPI.Tools to say when you’re supporting v3.1, by adding v3_1: true to _data/tools.yml. You can also pop a openapi31 tag on GitHub so that other tooling aggregators can find you too!

Expand allBack to topGo to bottom

May 04
Love0

OpenAPI Welcomes New Member Optic

By Blog

The OpenAPI Initiative, the consortium of forward-looking industry experts focused on evolving and implementing the OpenAPI Specifications (OAS), is welcoming Optic as a new member!

Optic’s open source tools help make the OpenAPI Specification and API-first practices adoptable. Keeping up-to-date OpenAPI descriptions is an important part of any API-first workflow and Optic’s tools are intended to make it easy for every developer to work with OpenAPI without having to write it manually. 

“Optic has been one of the most popular open source tools for maintaining accurate API docs. We always had our own spec under the hood, but some of our largest customers and most influential community members started a project to adopt OpenAPI,” said Aidan Cunniffe, CEO and Founder, Optic. “Coming home to OpenAPI has been really great, and we’re excited to take all the learnings and use them to make OpenAPI more adoptable for teams.”

Once teams are planning and tracking their API changes in OpenAPI, they are well on their way to working API-first. Optic’s API Review tool (in beta) can plug into Pull Requests and CI and shows Code Reviewers the API changes under consideration and their impact. Teams can set up CI to test API changes against their company’s API guidelines. This helps developers think about the impact of problematic changes before they get deployed to consumers. 

Optic Resources

OpenAPI Resources

To learn more about participate in the evolution of the OpenAPI Specification: https://www.openapis.org/participate/how-to-contribute

About the OpenAPI Initiative

The OpenAPI Initiative (OAI) was created by a consortium of forward-looking industry experts who recognize the immense value of standardizing on how APIs are described. As an open governance structure under the Linux Foundation, the OAI is focused on creating, evolving, and promoting a vendor neutral description format. The OpenAPI Specification was originally based on the Swagger Specification, donated by SmartBear Software. To get involved with the OpenAPI Initiative, please visit https://www.openapis.org

About Linux Foundation

Founded in 2000, the Linux Foundation is supported by more than 1,000 members and is the world’s leading home for collaboration on open-source software, open standards, open data, and open hardware. Linux Foundation projects like Linux, Kubernetes, Node.js and more are considered critical to the development of the world’s most important infrastructure. Its development methodology leverages established best practices and addresses the needs of contributors, users, and solution providers to create sustainable models for open collaboration. For more information, please visit us at linuxfoundation.org.

Mar 28
Love0

Flotiq, API-First Content Management Platform, Joins OpenAPI Initiative

By Blog

The OpenAPI Initiative, the consortium of forward-looking industry experts focused on evolving and implementing the OpenAPI Specification (OAS), is announcing that Flotiq has joined as a new member.

Flotiq is a content management platform that is focused on APIs. It enables users to create custom content types. It generates supporting APIs, documentation, SDKs, and Postman collections. The Content Types created in Flotiq are automatically translated into a set of RESTful endpoints. Flotiq provides an OpenAPI schema that updates automatically after every change made to data models. That schema is then used for generating SDKs and API docs. Tapping into the OpenAPI ecosystem – Flotiq takes the developer experience to the next level and facilitates system intregration and publishing content through standard-compliant APIs.

“At Flotiq we strongly believe in open standards to enable development of well-engineered systems. We support the OpenAPI Specification extensively in our product, and by joining the OpenAPI Initiative we see a real opportunity to help shape the future of OpenAPI,” said Andrew Wytyczak-Partyka, CEO, Flotiq. “Now, more than ever, it’s time for us to engage with the community. We’re excited to be a member of the OpenAPI Initiative.”

Flotiq Resources

OpenAPI Resources

To learn more about participate in the evolution of the OpenAPI Specification: https://www.openapis.org/participate/how-to-contribute

About the OpenAPI Initiative

The OpenAPI Initiative (OAI) was created by a consortium of forward-looking industry experts who recognize the immense value of standardizing on how APIs are described. As an open governance structure under the Linux Foundation, the OAI is focused on creating, evolving, and promoting a vendor neutral description format. The OpenAPI Specification was originally based on the Swagger Specification, donated by SmartBear Software. To get involved with the OpenAPI Initiative, please visit https://www.openapis.org

About Linux Foundation

Founded in 2000, the Linux Foundation is supported by more than 1,000 members and is the world’s leading home for collaboration on open-source software, open standards, open data, and open hardware. Linux Foundation projects like Linux, Kubernetes, Node.js and more are considered critical to the development of the world’s most important infrastructure. Its development methodology leverages established best practices and addresses the needs of contributors, users, and solution providers to create sustainable models for open collaboration. For more information, please visit us at linuxfoundation.org.

Feb 10
Love0

Treblle, API Monitoring and Analytics, Is OpenAPI’s Newest Member

By Blog

The OpenAPI Initiative, the consortium of forward-looking industry experts focused on evolving and implementing the OpenAPI Specification (OAS), is announcing today that Treblle has joined as a new member. 

Treblle provides API monitoring and analytics solutions, and makes it “easy to understand what’s going on with your APIs and the apps that use them.” Treblle was established to solve problems the founders themselves, Vedran Cindrić and Darko Blaževic, had experienced. 

Based in Zagreb, Croatia, Treblle announced €1.2 million in via Nauta Capital in July 2021. 

“I wanted Treblle to join the OpenAPI specification because I strongly believe that we need to have some kind of standard, guide or north star when it comes to API docs,” said Vedran Cindrić, Founder, Treblle. “I’ve spent the past 10 years building products, platforms, apps and APIs. I saw some amazing APIs with superb documentation, but I also saw a lot of terrible APIs that were documented horribly. I think the OpenAPI specification is a great way of pushing documentation forward and, more importantly, pushing developers forward to not just write docs but build better APIs.”

Full Treblle API Monitoring and Analytics information available here: https://treblle.com/ 

More from Treblle

Free Treblle ebook for building great REST APIs: https://treblle.com/ebooks/the-10-rest-commandments 

Treblle for PHP, Python, Node, Laraval and more: https://github.com/Treblle 

Treblle on Reddit: https://www.reddit.com/r/DevelopingAPIs/ 

OpenAPI Resources

To learn more about participate in the evolution of the OpenAPI Specification: https://www.openapis.org/participate/how-to-contribute

About the OpenAPI Initiative

The OpenAPI Initiative (OAI) was created by a consortium of forward-looking industry experts who recognize the immense value of standardizing on how APIs are described. As an open governance structure under the Linux Foundation, the OAI is focused on creating, evolving and promoting a vendor neutral description format. The OpenAPI Specification was originally based on the Swagger Specification, donated by SmartBear Software. To get involved with the OpenAPI Initiative, please visit https://www.openapis.org

About Linux Foundation

Founded in 2000, the Linux Foundation is supported by more than 1,000 members and is the world’s leading home for collaboration on open source software, open standards, open data, and open hardware. Linux Foundation projects like Linux, Kubernetes, Node.js and more are considered critical to the development of the world’s most important infrastructure. Its development methodology leverages established best practices and addresses the needs of contributors, users and solution providers to create sustainable models for open collaboration. For more information, please visit us at linuxfoundation.org.

Dec 16
Love0

This Year’s API Specification Conference (ASC 2021) by the Numbers

By Blog

This year’s API Specifications Conference (ASC) organized by the OpenAPI initiative was held virtually from September 28 through 29, 2021. The conference continues to grow by leaps and bounds and is gaining the attention of people interested in API technology. It was a real thrill hearing from industry experts discussing topics such as OpenAPI Specifications, RAML, Blueprint, gRPC, OData, JSON, Schema, GraphQL, AsyncAPI and other formats. For example, the keynote presentation Leading API efforts at scale by Mandy Whaley & Yina Arenas, Microsoft, So you think you understand JSON Schema? By Ben Hutton, Postman/JSON Schema. Or AsyncAPI 2.0: Enabling the Event-Driven World by Someshekhar Banerjee, Ebay.The discussions helped attendees get acquainted with the different formats and also learn how to practically use them.

The full Linux Foundation report on ASC 2021, “Transparency Report: API Specifications Conference (ASC) 2021” is available now (PDF).

2021 ASC Transparency Report_FinalDownload

We had attendance from 319 people from 37 countries—with a majority of them attending up to 10 sessions. 

The survey conducted after the conference showed that 89% of the attendees rated the content delivered at the conference as “Great” or “Excellent.”

The charge for the entire conference was $39 and 10 community scholarships were given to active members of the open source community. OpenAPI donated $10 from each registration fee and a total of $2,500 was donated to Code2040 in support of their mission. Code2040 is growing racial equity lens in the tech industry through their Fellows Program with technology companies. The conference received a Gold badge with the highest rating from the CHAOSS D&I Event Badging Program, showing that we promote healthy D&I practices.

Online events have created an opportunity for us to reach new audiences and expand our reach. For those that missed the conference or would like to watch the event again, the keynote and session recordings are available on our YouTube Channel. Speaker presentations are also available for download under each talk here.

 

Download the full Linux Foundation report on ASC 2021, “Transparency Report: API Specifications Conference (ASC) 2021” (PDF).

2021 ASC Transparency Report_FinalDownload
Dec 09
Love0

ReadMe, API Documentation Hub, Joins OpenAPI Initiative

By Blog

The OpenAPI Initiative, the consortium of forward-looking industry experts focused on evolving and implementing the OpenAPI Specification (OAS), is announcing today that ReadMe has joined as a new member. 

With ReadMe, teams create interactive developer hubs that help users learn, build, and debug API issues. Access to real-time API request history can improve developer support and visibility into how APIs are being used to prioritize improvements. 

Backed by Accel, ReadMe supports developer hubs for more than 10,000 API teams like Notion, Scale AI, Lyft, and Intercom. 

Focus on Easier to Use APIs

“ReadMe’s mission is to make documentation and APIs better for everybody. The goal of making every API easier and more fun to use guides everything we do — from big product updates like our recent API Reference redesign or ReadMe Recipes to little details like code samples generated by the api SDK and schema-based tooltips,” said Gregory Koberger, ReadMe Founder and CEO. “The OpenAPI Specification has helped us better understand the complexity of APIs, so we can better abstract that complexity away for our customers. We’re looking forward to bringing our perspective on developer experience to the group!”

Supporting OpenAPI v3.1

Along with joining the OAI, today ReadMe is announcing full upload support for OpenAPI v3.1. After uploading an OpenAPI 3.1 file in ReadMe, users can take advantage of a growing set of OpenAPI functionality in their API Reference, including recently added support for tag and callback objects.

If you’d like to contact ReadMe directly, send email to support@readme.io or on Twitter at @readme.

OpenAPI Resources

To learn more about participate in the evolution of the OpenAPI Specification: https://www.openapis.org/participate/how-to-contribute

About the OpenAPI Initiative

The OpenAPI Initiative (OAI) was created by a consortium of forward-looking industry experts who recognize the immense value of standardizing on how APIs are described. As an open governance structure under the Linux Foundation, the OAI is focused on creating, evolving and promoting a vendor neutral description format. The OpenAPI Specification was originally based on the Swagger Specification, donated by SmartBear Software. To get involved with the OpenAPI Initiative, please visit https://www.openapis.org

About Linux Foundation

Founded in 2000, the Linux Foundation is supported by more than 1,000 members and is the world’s leading home for collaboration on open source software, open standards, open data, and open hardware. Linux Foundation projects like Linux, Kubernetes, Node.js and more are considered critical to the development of the world’s most important infrastructure. Its development methodology leverages established best practices and addresses the needs of contributors, users and solution providers to create sustainable models for open collaboration. For more information, please visit us at linuxfoundation.org.

Nov 03
Love0

Announcing Open Finance, a New OpenAPI Special Interest Group

By Blog

OpenAPI has formed a Special Interest Group (SIG) for the purpose of identifying the API use cases and behaviors to empower Open Finance solutions in the near future.

Open Finance is the evolution of Open Banking, a relatively new innovation in the field of financial technology. This has been largely spurred by laws and regulations centered around customer data and transactions respectively in the UK and EU in 2016 and 2018-19. Other markets the world over are also beginning to develop solutions based on Open Finance… or at least have started following the developments closely.

With all this in mind, the OpenAPI Initiative (OAI) has created an SIG to support the adoption of APIs and help grow the digital infrastructure for this next evolution of banking and finance. The initial focus will be on serving financial organizations and their customers within the EU and European Economic Area as they rapidly develop solutions to comply with Payment Services Directive 2. As solutions are developed for Europe, they will become immediately applicable to other markets.

The OAI has named Refael Botbol Weiss (LinkedIn/Github) as the POC for the group. Email him at refael@up9.com for information and inquiries about joining.

The initial steps will be to form a forum of experts in the world of development and finance to discuss the issues surrounding open finance implementation as well as the API behaviors necessary to facilitate Open Finance solutions. Additionally, the primary use cases of Open Finance technology will be discussed, which may include banks, credit unions, insurance companies, credit bureaus, real estate groups, financial planners, and/or others.

Participation in this SIG will be open to any member of the OAI. To sign up for the OAI, visit here.

For updates and more information about getting involved, click here.

Oct 25
Love0

A Good Travel Experience Begins with One Single Booking Portal – How Open APIs Are Leading the Way

By Blog

For more information on the OpenAPI Initiative and #sig-travel, join the conversation on Slack. https://open-api.slack.com/archives/C0122NPKUR2

Today’s traveler is increasingly shopping for an experience, not just a seat on a plane or bed in a hotel. In fact, the travel experience begins from the booking environment itself where consumers expect a single portal to connect across travel providers and travel retailers. People are looking for the convenience and value of the delivery and ride sharing apps that they use in their day-to-day lives and want that applied to the travel experience.

The reason the travel industry has lagged behind modern expectations is because it has lagged behind the latest technological trends. It’s that simple.

Creating an End-to-End Journey is Hard

The process and protocols largely used today between providers have their base in travel standards agreed to in the 1960s and modified over time. Initially created to address airline interlining, allowing a single ticket to include flights on multiple air carriers, they have been pressed into service across the travel verticals.

As time has gone on the once workable solution has begun to show its limitations. There are multiple efforts in the industry to break with the past and pursue an approach where a travel offer may be handled much like any other retail offering in the digital space.

Travel, however, has some unique needs as products are transient (an empty seat is worthless after departure time) and in most cases specific to location (airplanes must land at an airport). Also, in most cases a travel product must be combined with another travel product to satisfy a request to create a trip.

Creating an end-to-end journey implies a combined offer from multiple offers proposed and/or serviced by multiple providers. This adds a level of complexity, maintaining relationships between offers, other retail categories avoid.

Key Takeaway: Focusing on the experience as a new approach to travel retail requires a new level of interoperability among participants in the travel market.

Addressing Interoperability Will Open Up Broad Opportunities

Solving the issues to support experience based, total trip, retail at scale could unlock massive economic opportunities for many of the current distribution channels operating today or create new ones. Mainstream distribution channels focus mainly on air which in the US had a total operating revenue of $120[1] billion. However, the total US travel revenue for 2019 was $1.1[2] trillion.

Much of that figure is consumers figuring out for themselves how to make arrangements, a huge, missed opportunity to leverage automation. To build the experiences people are looking for, outside of immediate travel and lodging portals like Expedia, consumers are bouncing between websites and calendars to find restaurants, museum passes and jet ski rentals.

The reason we aren’t seeing a wider variety of offerings is not hard to understand: For the mainline distributors it’s not worth the effort to connect, maintain and monitor small suppliers thru bespoke APIs.

By unlocking interoperability, providers of travel products and services would have access to channels they are currently shut out of due to costs and complexity. The public is eager to get out of the house and experience the world again but would like to avoid the odious task of DIY travel orchestration and management. They want experience led retailing which industries like hospitality are investing in but only at the property level, not at the full trip level.

The travel industry cannot afford to allow API chaos to continue to be a barrier to more effective retailing.

Getting Alignment on the Solution is Critical

In response, the OpenTravel Alliance (OTA) and the OpenAPI Initiative (OAI) will work together to focus on API conventions and standards, not just messages. Within OAI, there is now a special interest group to focus on travel issues (#sig-travel).

The Travel SIG will be the conduit for the needs of the travel industry that pertain to the Open API Specification (OAS). The OAS is a broad specification intended to help developers solve real world business issues with as much flexibility as possible.

What is needed for interoperability and to reduce API chaos and hence distribution costs in travel is more consistency in API behaviors. OpenTravel will take the lead on providing open-source tooling and publishing reference architectures with refence implementations that adhere to the OAS. OTA 2.0 with its model driven approach will form the basis of this more comprehensive approach that supports all travel verticals. This will be in cooperation with existing travel standards bodies and trade associations.

The overriding goal will be to lower the cost of connectivity to publish, acquire, distribute, and market digital travel products.

What Can I do?

Join the conversation and help build a more modern and seamless travel industry! For more information on the OpenAPI Initiative and #sig-travel, join the conversation on Slack. https://open-api.slack.com/archives/C0122NPKUR2

For more information on OTA 2.0, including becoming an Open Travel member, go to www.opentravel.org or contact Jeff ErnstFriedman at jeff.ernstfriedman@opentravel.org.

[1] Source: Phocuswright White Paper, Air Sales and the Travel Agency Distribution Channel April 2019

[2] Source: U.S. TRAVEL AND TOURISM OVERVIEW (2019), US Travel Association.

Sep 23
Love0

Kubeshop, Accelerator/Incubator for Kubernetes, Joins OpenAPI Initiative

By Announcement, Blog

The OpenAPI Initiative, the consortium of forward-looking industry experts focused on evolving and implementing the OpenAPI Specification (OAS), is announcing today that Kubeshop.io has joined as a new member. Kubeshop’s CTO, Ole Lensmar, served as the chairman of the OpenAPI Initiative from its inception in 2016 until 2020. We welcome back the familiar face! 

Kubeshop is an open-source accelerator/incubator focused on Kubernetes (“K8s”). Kubeshop identifies needs and offers resources and guidance to projects within the k8s space, specifically focusing on helping Developers, Testers, and DevOPS engineers with tooling that strives to make complex workflows simpler and more productive. Currently, Kubeshop is home to Kusk, Kubtest, and Monokle:

  • Kusk allows users to work with an OpenAPI specification as the source of truth for Kubernetes manifests, simplifying cluster configuration and management across a number of popular Kubernetes Ingress Controllers
  • Kubtest provides a framework for testing of applications and APIs running under Kubernetes, allowing teams to decouple test orchestration and execution from ci/cd tooling and centralize test-result management and analysis
  • Monokle simplifies everyday tasks and workflows related to management and debugging of k8s manifests 

“Joining and supporting the OAI was an obvious step for us; the OAI is central to the continued adoption and evolution of the OpenAPI Specification, and we are excited about the prospect of housing projects targeting OpenAPI specific needs and Kubernetes workflows,” said Ole Lensmar, CTO, Kubeshop.

We look forward to watching Kubeshop grow and evolve, and help out k8s developers! 

OpenAPI Resources

To learn more about participate in the evolution of the OpenAPI Specification: https://www.openapis.org/participate/how-to-contribute

About the OpenAPI Initiative

The OpenAPI Initiative (OAI) was created by a consortium of forward-looking industry experts who recognize the immense value of standardizing on how APIs are described. As an open governance structure under the Linux Foundation, the OAI is focused on creating, evolving and promoting a vendor neutral description format. The OpenAPI Specification was originally based on the Swagger Specification, donated by SmartBear Software. To get involved with the OpenAPI Initiative, please visit https://www.openapis.org

About Linux Foundation

Founded in 2000, the Linux Foundation is supported by more than 1,000 members and is the world’s leading home for collaboration on open source software, open standards, open data, and open hardware. Linux Foundation projects like Linux, Kubernetes, Node.js and more are considered critical to the development of the world’s most important infrastructure. Its development methodology leverages established best practices and addresses the needs of contributors, users and solution providers to create sustainable models for open collaboration. For more information, please visit us at linuxfoundation.org.

Close Menu