eBay Joins the Open API Initiative

By | Blog

The partnership makes it easier for eBay developers to integrate with our RESTful public APIs and evolve their buying and selling experiences on our platforms.

For more than 20 years, eBay has been a leading marketplace, connecting shoppers to their perfect item from more than 1.1 billion listings on our platform and providing opportunities for sellers to grow their businesses. Today, I’m proud to announce our membership in the Open API Initiative (OAI). This partnership will focus on the OpenAPI Specification, making it easier and faster for eBay developers to integrate with eBay’s RESTful public APIs as we evolve the buying and selling experience on eBay. This opportunity leverages technology to make it easier for our developer ecosystem to create new eBay experiences.

The OAI is an open source project under the Linux Foundation. These software projects are independently funded and are geared toward harnessing the power of collaborative development across industries and ecosystems. OAI is the most popular open source framework for defining and creating RESTful APIs, with tens of thousands of developers using the tools.

As a member of OAI, we are continuing to tap into our developer ecosystem and grow eBay’s APIs, by expanding our developer community and encouraging building to creating a more integrated platform and shopping and selling seamless experiences on eBay. Earlier this year, we we kicked off eBay Connect with seven developer events across the world to give external developers insights into our platform and encourage their innovation. And last year, eBay Developers Program revamped our API platform with 13 new standards-based APIs.

This partnership and our new APIs make it simpler for our developers and sellers to quickly integrate with eBay and onboard all their inventory—part of our promise to deliver the most powerful commerce platform to our seller and developer partners so they can build sophisticated integrations to manage all end-to-end selling operations on eBay and easily scale their business.

Gail Frederick
eBay representative on the Business Governing Board
Gail Frederick is Senior Director of Developer Ecosystem and Services at eBay, where she strives to disrupt commerce with innovative ideas to create more powerful buying and selling experiences on eBay.

The OAI Announces the OpenAPI Specification 3.0.0

By | Blog

The Open API Initiative (OAI), a Linux Foundation project created to advance API technology, announced the 3.0.0 release of the OpenAPI Specification. The OAI provides a foundation for developing interoperability of APIs and other technologies.

The OpenAPI Specification (OAS) v3 release is the culmination of nearly two years of collaboration among senior API developers and architects from across multiple industries, such as payment and banking, cloud computing, the Internet of Things, and vendors building API solutions. Under the auspices of the OAI, this collaboration provides a common way to unify how an industry defines and describes APIs—the services fundamental to how applications talk to each other in today’s connected world. The OpenAPI Specification defines the interfaces for RESTful APIs, describing resources and operations in a format that is easily discoverable and understandable by both machines and humans.

“The release of this third-generation format is a significant milestone for our community,” said Ole Lensmar, CTO, SmartBear Software and Chair of the OAI Board. “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.”

Major improvements in the new version 3 release include support for describing callbacks, links to express relationships between operations, webhooks, enhanced examples, improved parameter descriptions, and better multipart document handling. Additional features add support for templated server URLs and semantic versioning. A detailed list is available here: OpenAPI Specification v3

“We’re excited to see growth in adoption and validation for a common OAI Specification, with nearly 4X growth in member companies over the past 18 months alone and increasing interest from governments and the healthcare and fintech sectors,” said Linux Foundation Executive Director Jim Zemlin. “Such growth validates the community’s vision to deliver an open way to share data with APIs.”

APIs have been elevated from a development technique to a driver of business, necessary for technology innovation and modernization. According to ProgrammableWeb, nearly 18,000 public APIs have been published since 2005, up nearly 1,000 in the past quarter of 2017 alone. Founded in 2015, the Open API Initiative has swelled to 27 members in the last 18 months and continues to accelerate beyond API vendors to include leaders in banking, healthcare, and governments worldwide.

Industry Support for OAI

“42Crunch is honoured to be part of the Open API Initiative,” said Philippe Leothaud, Chief Innovation Officer at 42Crunch. “The OpenAPI Specification is open source, platform-agnostic, vendor-agnostic and extensible. Leveraging this de-facto standard will accelerate API adoption across all industry verticals and, in particular, help the automatic consumption of APIs from applications and devices.”

“Healthcare is going through a data revolution right now with APIs at the top of the agenda,” said Mohamed Alkady, President at Hart. “By agreeing on a common API structure that allows anyone to quickly help build this future without having to re-learn a new nomenclature every time. With the release of OAS3 we are getting closer to a more well defined structure that can be more universally usable and deployable. We believe the Open API Initiative and joint technologies will lead to next-generation changes in API development and we’re excited to push this initiative forward in the healthcare space.”

“The OAI has progressed this specification relatively quickly, and the IBM Cognitive Cloud and API Economy teams are set to embrace this new, open specification”, said Todd Moore, VP of Open Technology, Digital Business Group at IBM. “By helping to establish the OAI, IBM joined with other companies who understand that robust, scalable, and secure APIs for enterprise systems form the basis of modern digital ecosystems. In addition, today’s software developers want open tooling to help them quickly and consistently create APIs to accelerate business transformation. Our clients trust IBM to help them manage their entire API management life-cycle.”

Kong (Mashape)
“Kong is the world’s most popular open source API gateway, and we’ve seen incredible growth of OpenAPI Specification usage,” said Marco Palladino, CTO and Co-founder, Kong (Mashape). “API specifications are a critical part of modern API development, publishing, and consumption workflows – and the Open API Initiative has been tirelessly advancing the industry-leading OpenAPI Specification format to its milestone 3.0.0 release. We are excited to keep contributing to the tooling ecosystem around OAS.”

“Microsoft congratulates the Open API Initiative and its developers on the release of version three of the OpenAPI Specification,” said Kamaljit Bath, Principal PM Manager, Azure Developer Experience. “We use OpenAPI across the company including: for description of Azure APIs and generating client libraries using the AutoRest tool, for describing over 150 services integrated with Azure LogicApps / Microsoft Flow, for customers to describe APIs they’re bringing to the Azure API Management service, and for description of APIs for which we generate documentation hosted on and We look forward to the latest release and the improvements it brings for ease of authoring, maintaining, and consuming OpenAPI descriptions.”

“This new version of the OpenAPI Specification (OAS) incorporates important advances in describing APIs more fully, ” says Uri Sarid, CTO, MuleSoft. “API specifications are central to enabling robust, productive, and rapidly growing marketplaces of business capabilities. These marketplaces, in turn, are at the heart of digital transformations in enterprises, in governments, and across entire industries. OAS version 3 provides a broad format for describing APIs, RAML provides a powerful format for modeling APIs, and the API Modeling Framework leverages both to provide reusability and consistency and a universal SDK for building API tooling. We look forward to continuing to invest in these and in advancing OAI standards to create value for the API ecosystem.”

Red Hat
“Red Hat is a strong believer in Open Standards and Open Source,” said Steven Willmott, Senior Director and Head of API Management, Red Hat Inc. “The progress of the Open API Initiative and this release show what the power of community can do and we are pleased to see the industry coalescing around a strong common standard.”

“SmartBear is a strong supporter of open source communities, having donated the original Swagger Specification to the OAI in 2015. The evolution of the spec shows the power of bringing together collaborators across industries, to evolve the specification to meet the needs of API developers and consumers across the world in an open and transparent manner,” said Ron Ratovsky, Swagger Developer Evangelist, SmartBear. “SmartBear is committed to supporting the OAS 3.0 with our open source Swagger tools and our integrated platform, SwaggerHub.”

Tyk Technologies
“An increasing number of our customers are adopting the OpenAPI Specification as the de-facto API description format,” said Martin Buhr, CEO and Founder of Tyk Technologies. “As a leading Open Source API Management platform, Tyk is committed to open source and open standards, and we’re excited to be part of the OAS v3.0 specification launch.”

Current members of the OAI include: 42Crunch, Adobe Systems, Inc., API Evangelist, Atlassian, CA Incorporated, Capital One, Cloud Elements, Finxact, LLC, Google, Inc., Hart, IBM, Intento, Inc., ISA Research Group, Mashape Inc., Microsoft Corporation, MuleSoft, Oracle Apiary, Red Hat, RepreZen, Restlet, Inc., Salesforce, Samsung ARTIK Cloud, SmartBear Software, Software AG, StopLight, and Tyk.

OpenAPI is an evolution of the Swagger specification, which was donated by SmartBear to The Linux Foundation in 2015. To get more information about the OpenAPI Specification and learn about membership and contributions, please visit:


The OpenAPI Specification v3
Follow OAI on Twitter @OpenApiSpec or join the conversation on GitHub

About the Open API Initiative
The Open API Initiative (OAI) was created by a consortium of forward-looking industry experts who recognize the immense value of standardizing on how REST 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. Visit for more information.


The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see its trademark usage page: Linux is a registered trademark of Linus Torvalds.

One Last Call for Comments, so Finish Your Issue or PR

By | Blog

With this blog post, we open a two-week last call for comments period for the OpenAPI Specification v3.

As mentioned last month, the OpenAPI Specification v3 is now entering a last call for comments period. You can find the latest release candidate of the OpenAPI Specification v3 at:

At its meeting on Friday, 16 June, the Technical Developer Community (TDC) confirmed the below dates:

  • 4 weeks from 22 May through 16 June: to resolve remaining pull requests
  • 2 weeks from 19 June through 30 June: Comment period ← You are here
  • 2 weeks from 3 July through 14 July: to resolve remaining comments and issues
  • 1 week from 17 July through 21 July: release window (tentative)

Whether you haven’t looked at the spec since v2.0, or keep a well-worn copy of v3.0.0-rc1 next to your keyboard, this is the single best opportunity you will have to affect the spec draft before it is released.

Here are a few ways you can offer your feedback:

The OpenAPI Specification v3 is at a “release candidate” stage.  A few areas where comments would be particularly helpful are clarity of examples and descriptions of functionality.  Suggestions of new features or large changes to existing features are welcome, but in all likelihood will be considered only for a future release.

NOTE: Members of the TDC have expressed a preference for pull requests, since it makes the intention clearer, and since all changes must eventually pass through that stage. If you’re unable to submit a PR, an issue is the next best choice.

If you’re looking to generally learn more about the OpenAPI Spec v3, check-out:

Now playing: Closing Time by Semisonic


Financial Services Provider Finxact Joins Open API Initiative

By | Blog

This week Finxact announced it has become an official member to the Open API Initiative. Finxact collaborates with the banking industry on an Open Banking API.

Finxact is building upon the OpenAPI Specification – OAS to develop an open banking API with its community. As a virtual core, third party services and banks’ existing systems plug into Finxact’s core processing rules engine and system of record through Finxact’s Open Banking API.

“The OAI and its growing board of members is excited to welcome Finxact to the workgroup. Finxact will be the first core banking provider to officially embrace our workgroup’s mission of openness, transparency and interoperability,” said Ole Lensmar, chairman of the OAI. “Finxact and its partners are making groundbreaking contributions that will enable banks and FinTech companies to interoperate freely and transparently using the OpenAPI Specification (OAS) as the enabler for their interactions.”

Read the full press release here.

RepreZen Joins the Open API Initiative, Announces Early OAS 3.0 Tool Support

By | Blog

The OpenAPI Specification (OAS) version 2.0, formerly known as the Swagger specification, is the current industry standard for API descriptions, supported by thousands of open source projects and all major API technology vendors. And OAS version 3.0, planned for release in July 2017, is the first major update to the specification.

OpenAPI 3.0 can describe a wider range of modern REST APIs with greater precision and detail. It offers improved component reuse, more flexible message schemas, and new API features like hyperlinks and callbacks.

RepreZen is excited to announce experimental editing support for OpenAPI 3.0 in our commercial and open source software, bringing these new capabilities right to the developer desktop. Our first implementation is based on the current draft specification, and uses the Gnostic JSON Schema for OpenAPI, contributed by Tim Burks at Google.

RepreZen Joins the Open API Initiative

We’re also proud to announce that RepreZen is now a member of the Open API Initiative, where we’ll continue to work as part of the Technical Developer Community on the OpenAPI Specification.

Working with the OpenAPI community is a gratifying experience for us, because of the great depth of knowledge and thought leadership from SmartBear, Google, Microsoft and others. They’ve kept their promise of keeping the group open and vendor-neutral. And with Swagger they’ve inherited a wealth of practical knowledge, elaborated in discussion threads on GitHub (and elsewhere), and distilled into the OpenAPI Specification itself.

For the RepreZen team, this puts the official stamp on our participation, which now dates back several years, and our support for OAS as the industry-standard API description language.

And to our customers, joining the OAI is our promise to keep OAS at the center of RepreZen’s products and open source technologies, to keep innovating and building solutions that make OpenAPI work for you.

Thoughts on the OpenAPI, Past and Future

Great software is about meeting in the middle.

If you’re an idea guy like me, you come at it from the abstract viewpoint, describing the essence of the problem and the solution, with maximum insight, and minimal implementation detail. You look for the highest-level, most expressive way to represent that in a machine-readable form, and you drill down to implementation detail, but only as far as you need to.

If you’re a pragmatist, you start with the nuts and bolts, the mechanics, and refactor your way up to a more elegant solution.  But only until the elegance stops paying for itself. Then you stop, leave the rough edges for another day, and move on.

But whichever angle you come from, it’s an ongoing process of reconciliation. Evolving the software means evolving the conceptual framework and code in parallel; and constantly, artfully, weaving them together. You work top-down and bottom-up, and you meet in the middle.

The OpenAPI Specification is a beautiful example of what just the right amount of abstraction can do. It offers a step up in expressive power, allowing developers to think in terms of resources, operations and data models — familiar concepts, gliding at a comfortable altitude just above the canopy of protocols, controllers and classes.  And you don’t have to rethink your API in high-level semantics, esoteric concepts, or religious dogma.

And with a rich ecosystem of commercial and open source tools, developers have a choice of working bottom-up, using code-first annotations, or top-down, using an API description language. Wherever you start, we can all meet in the middle with the OpenAPI Spec.

Let’s Talk APIs!

Want to get involved? Our door’s open, and we love hearing from our users.

  • Talk to us, and let us know what you think about OpenAPI, RepreZen API Studio and KaiZen Editor.

Reprezen API Studio: A Complete IDE for OpenAPI Development 

RepreZen API Studio is our flagship platform for API-first design, documentation and development.

To get started, just register for the free trial, download and install.  See the FAQ article on our support site to get started.

KaiZen OpenAPI Editor: Now on Eclipse Marketplace

KaiZen OpenAPI Editor is RepreZen’s open source, Eclipse-based editor for the industry-standard OpenAPI Specification language. This is the same full-featured editor, formerly known as SwagEdit, used by RepreZen API Studio.  KaiZen OpenAPI Editor is our core editing component for OpenAPI 2.0 and 3.0.

You can try it out today by installing from Eclipse Marketplace into Eclipse Desktop IDE, Mars.2 release or later. Once you’ve installed, see the Getting Started Guide for quick overview.   

Ted Epstein
CEO of RepreZen
Ted Epstein, CEO of RepreZen, has been helping organizations simplify, unify, and harmonize their system interfaces for over 10 years. Ted leads the architecture of RAPID-ML, the first IDL to bring the power of collaborative data modeling to REST API design. Ted is co-organizer of the API-Craft NYC Meetup and has presented at conferences including QCon, EclipseCon, API-Craft, and Data Modeling Zone.

The Open API Initiative Is Sending You a Save the Date Card

By | Blog

We’re getting close to OpenAPI Spec v3.0.0 final. If you’ve been waiting to start kicking the tires on the OpenAPI Specification (OAS) v3.0.0 (f.k.a. Swagger), now is the time to be prototyping or coding. Mark your calendar for a two-week last comment period from Monday, 19 June to Friday, 30 June, and watch for a final release in July.

On March 1st, the Open API Initiative (OAI) announced the publication of the first OpenAPI Specification v3.0.0 Implementer’s Draft. This release was tagged 3.0.0-rc0, and we had a subsequent release tagged 3.0.0-rc1 near the end of April.

At its meeting on Friday, 19 May, the Technical Developer Community (TDC) agreed to target the below timeline for release:

  • 4 weeks from 22 May through 16 June: Resolve remaining pull requests
  • 2 weeks from 19 June through 30 June: Comment period
  • 2 weeks from 3 July through 14 July: Resolve remaining comments and issues
  • 1 week from 17 July through 21 July: TENTATIVE release window

In case you’re not getting push notifications to your mobile device for every change into the OpenAPI Spec repo, here are some useful links:

As mentioned above, if you’re not already doing so, now is a great time to review the latest OpenAPI Spec v3.0.0, consider how your systems and tools can take advantage of the new functionality, and consider if anything could be improved before v3.0.0 final release.

Lastly, if you’re writing any kind of tool that uses the 3.0 draft spec in any way, please let us know by completing this very short survey, because only through implementing code against the draft spec can we gain confidence in its readiness!

Tony Tam
VP of Swagger Products at SmartBear Software
Jeremy Whitlock
Software Engineer at Google
Ron Ratovsky
Swagger Developer Evangelist at SmartBear Software
Darrel Miller
Software Developer at Microsoft
Marsh Gardiner
Product Manager at Google
Jason Harmon
Head of APIs at Typeform

Competitors Join OAI to Lead Convergence of API Landscape

By | Blog
With the recent addition of Mulesoft — founders of RAML; joining Apiary — founders of API Blueprint; and SmartBear — stewards of Swagger, each as  members of the Open API Initiative, Jerome Louvel of Restlet took the opportunity to revisit the history of the OAI and API Specifications.

Instead of keeping direct competition between the three efforts going on, hoping that one would win and replace the two others, a better path became necessary and possible. Being close to the main actors of this story and building tools such as Restlet Studio that support both OAS and RAML and listening to our users, I realized that the ideal would be to have Apiary and MuleSoft join the Open API Initiative and contribute step by step to the convergence, not necessarily the merging, of the three specifications. On the API testing front, there are similar standardization needs, but beside the HAR (HTTP ARchive) format, only proprietary formats are available such as Postman Collections or JMeter Scripts.

Read the full article on the Restlet blog.



Note: Restlet is a founding member of the OAI and has recently joined the RAML workgroup.


Jerome Louvel
CTO & VP of Products at Restlet
Jerome Louvel is the Founder, CTO and VP of Products of Restlet and an expert in REST APIs. Jerome serves on the Open API Initiative Business Governing Board

The Open API Initiative and the Linux Foundation to Produce APIStrat 17

By | Blog

The Open API Initiative along with 3scale by Red Hat and the API Evangelist are pleased to announce that APIStrat has become a Linux Foundation event.

The API Strategy & Practice Conference -taking place October 31 – November 2 in Portland, OR. – will be jointly produced by Linux Foundation Events and the Open API Initiative (OAI)

For the past seven years, APIStrat was organized by 3scale, acquired by Red Hat in June 2016, who has donated the event to The Linux Foundation. The eighth edition of the conference will bring together a variety of attendees, from the API curious to developers and IT teams, business users and executives, to discuss opportunities and challenges in the API space.

“We are pleased to see APIStrat move under The Linux Foundation and the Open API Initiative. Since its inception, the conference has aimed to provide a vendor-neutral, high-quality space for discussion of the latest API topics, and I anticipate that the new organization team will manage it superbly. Like the Open API Initiative, we share a commitment to a standard common format for API definitions and see the transition for the event as a good fit,” said Steven Willmott, co-founder of APIStrat and senior director and head of API Infrastructure, Red Hat.

“After seven events, I am very pleased to see APIStrat maturing as a conference and becoming part of the Open API Initiative (OAI). The event has long been a forum for discussion around Open API (aka Swagger), so The Linux Foundation is a natural fit for hosting the conference,” said Kin Lane, co-founder of APIStrat and the API Evangelist.

The Linux Foundation produces over 100 events worldwide where the world’s leading technologists meet, collaborate and innovate.

API Design and What’s new with Open API? (Google Cloud Next ’17)

By | Presentations | No Comments

In this video, hear what’s new with the Open API Specification (OAS) — the vendor-neutral, portable, and open specification for providing technical metadata for REST APIs as well as latest trends in API design including topics such as Hypermedia and how the evolving OAI spec influences common patterns. Not just trends – this video is filled with real world examples.