{"API Evangelist"}

Quantifying The Community Around The Swagger API Specification

This post is extracted from a deep dive I've been doing into the Swagger ecosystem, as part of regular conversations I have been having with Tony Tam (@fehguy), trying to understand how we can better tell stories about Swagger. I've been tuned into things for a while now around the Swagger community, and there is a lot going on, but from the outside, some of this can be hard to see. Seeking a better understand what is the Swagger community, I wanted to take a walk through the sites, forum, and Github repositories.

First let’s start with the basics, what is Swagger? Merriam Webster defines Swaggers as: : to walk in a very confident way : to walk with a swagger. ;-) Seriously though, Swagger is a machine readable format (either JSON or YAML), for describing an API, providing a description of API operations, in a way that other applications can read, and understand. Even though Swagger is machine readable, and designed for other applications, it has also become a language for humans to describe and collaborate, around a shared, quantifiable, vision of what an API can do, throughout all stages of the API life cycle. 

If you want to learn about Swagger yourself, you can tune into these channels to learn more:

My goal with this post is evolve my understanding and awareness of what Swagger is, and hopefully along the way I can help increase yours as well. In my experience, many people have a very distorted, and limited understanding of what Swagger is, and I’d like to take some time to evolve that. When I started this research, my objective was to help Tony deliver a new website, and on-boarding materials for Swagger, assisting people of all skill levels in finding all things Swagger. I am just taking this moment to walk through what at I have so far, and craft a more robust version 1.0 narrative about what Swagger is, something that blogging helps me work through.

One of the biggest misconceptions I find when I talk with folks about Swagger, is that it is interactive documentation, when that is actually Swagger UI--when it comes to Swagger all roads start with the Swagger specification:

You can find version 2.0 of the spec here, which is the current active version in use. The Swagger spec lets you describe all the essential aspects of API operations, with information about the operator, the host and basePath for the API, details about what type of content it produces or consumes, like JSON or XML. Most importantly it lets you describe each of the paths for an API, with details on parameters, responses, and other details of each specific API path. Swagger also provides you with the ability to describe the underlying data model definitions, describing the valuable resources being served up via APIs.

To grasp the last paragraph, you have to have a pretty solid understanding of the moving parts of an API, but in short the Swagger spec gives us a language to potentially map out all of the common parts of an API. It also allows me to describe the security for each API, and tag to organize APIs into specific buckets. I use Swagger to describe the almost 20 APIs my business uses daily, with varying amount of detail about each resource, and the information it serves up. All the 20 of the Swagger definitions provide me with a machine readable map of my own IT infrastructure—as well as a common language that almost any other developer, or potentially not developer can learn to read, and work with.

With Swagger we now have a common way to communication around the APIs we develop, and also map out the public APIs we also depend on like Twilio, SendGrid, or even Twitter. Now what? Why do we do this? There are an increasing number of incentives emerging for why you generate machine readable API definitions like Swagger, which is part of the reason I’m looking to further quantify the Swagger community, so I can add to the master list.

Let’s start with what I’d consider to be the primary building blocks of Swagger, developed by the Swagger team, as part of the core offering:

Those six repositories represent the core tooling that the Swagger team has evolved around the specification, providing what I’d consider to be three stops along the API life cycle:

Swagger is often known for its interactive API documentation (aka Swagger UI), but there has also been a lot of work done on the codegen platform, and editor, taking things well beyond just API documentation. This is just the beginning of what is possible with Swagger. In an effort to find out what else is being done with Swagger, and what is being built with the specification, I wanted to see what the community is up to, which platforms they are integrating it into, and what other standalone tooling is being built using Swagger.

I want a better understanding of the core group of companies who have embraced the Swagger specification, and baked it into their own platform. I know there are hundreds of them out there, but finding them can be easier said than done, especially when I'm looking some sort of public announcement, blog post, press release, service description, to use as my reference. So far I have 49 companies that I’m tracking on, who have pulled the Swagger spec, and incorporated into their own platform and infrastructure.

3scale (reference)

Akana (reference)

Apache Apollo (reference)

Apache Camel (reference)

Apigee (reference)

Apigility (reference)

APIMATIC (reference)

apis.io (reference)

APIs.json (reference)

APItools (reference)

AppNow (reference)

Ardoq (reference)

Axway (reference)

Beego (reference)

Catch Software (reference)

Cloud Elements (reference)

Django REST (reference)

DreamFactory (reference)

elastic.io (reference)

Espresso Logic (reference)

Gluu (reference)

IBM (reference)

Magnolia CMS (reference)

Microsoft Azure (reference)

Neo4J (reference)

Netflix (reference)

Nomos Software (reference)

Open311 (reference)

OpenDaylight Project (reference)

OPENi (reference)

OpenShift by Red Hat (reference)

Pivotal (reference)

Postman REST Client (reference)

Quandl (reference)

REST United (reference)

RESTBase (reference)

RESTFiddle (reference)

Restlet / APISpark (reference)

Sandbox (reference)

Service Stack (reference)

SmartBear Software (reference)

SnapLogic (reference)

StrongLoop (reference)

Synapp.io (reference)

TIBCO Software (reference)

Visual Studio (reference)

WaveMaker, Inc. (reference)

WSO2 (reference)

Yelp (reference)

This list represents a pretty interesting mix of folks who understand the potential of Swagger, and have invested in the community by making it a core part of their operations. I know there are more of these out there (a lot more), but they haven’t talked publicly about what they are up to. This is just what I’ve aggregated from going through the Swagger site, group, and Github repositories, and from what I already know of the API space, from my monitoring.

After looking at the platforms who have pulled the Swagger specification into their operations, I wanted to see if I could also begin to quantify the community of APIs who have deployed Swagger UI, providing interactive API documentation for their own API platform. Since this is what Swagger is known for, I knew I would find quite a few to showcase. So far I have found 62:

World Population Project (reference)

3scale (reference)

ACI Blog Index (reference)

API Evangelist (reference)

API2Cart (reference)

AppSpin (reference)

Banckle (reference)

BetISN (reference)

Bitdango (reference)

BitTitan (reference)

CallFire (reference)

Carnival Mobile (reference)

CDScience (reference)

CityGro (reference)

CitySDK (reference)

Clarify API (reference)

Climate Change Costs (reference)

Cloudify (reference)

CommaFeed (reference)

Concur (reference)

DataValidation API (reference)

Datumbox (reference)

DreamFactory (reference)

DroneKit (reference)

Evercam (reference)

Expedia (reference)

fanart.tv (reference)

Formagg.io (reference)

GeoTrellis (reference)

Getty Images (reference)

GroupDocs (reference)

Guru (reference)

HabitRPG (reference)

hapi.js (reference)

Kubernetes (reference)

League of Legends (reference)

League of Legends eSports (reference)

Likibu (reference)

Mobovivo (reference)

Mozilla Open Badges (reference)

MuckRock (reference)

MyFox (reference)

MyNeighbor (reference)

MySMS (reference)

Pingup (reference)

Pop Up Archive (reference)

Project Chronos (reference)

PTisp (reference)

Puppet Labs (reference)

QI Bench (reference)

Rackspace (reference)

ReliefWeb (reference)

Sensr.net (reference)

Shoeboxed (reference)

Skimlinks (reference)

Subledger (reference)

TaDaweb (reference)

taxamo (reference)

The Resumator (reference)

UK Commission for Employment and Skills (reference)

Wordnik (reference)

YunoHost (reference)

Finding websites that have implemented Swagger UI is harder than you think. There are only three search engines I could find that let you search the source code of websites for JavaScript files and code. Ultimately I ended up mostly depending on my own ability to find new APIs, and manually uncover whether or not Swagger was actually in use. I’m working on a stack of Swagger and API Blueprint discovery search engines, but they aren’t quite ready for this dive.

Next I wanted to look through some of the tooling that has evolved as part of the Swagger community, which Github is definitely the place to begin this journey. When you search Github for the word Swagger, you get almost 1000 repositories. I was going to programmatically explore these results, but found that manually browsing through them was the best path to take, allowing me to make a decision on what each developer was up to.

The one thing I learned doing through this process—Swagger means many different things, to many different people. Most refer to Swagger, and mean Swagger UI, while others refer to it as generating server side code, or maybe client side code. Moving forward, there needs to be a lot of work done helped educate people about first, what Swagger is, a specification, and what are  each of the areas of tooling that are built on top of the Swagger specification.

Even after looking through the almost 1000 Swagger related Github projects, things are still very hazy for me, but I did learn a lot along the way, about what languages, frameworks and platforms developers are using Swagger, and the types of tools and integrations they are developing.

The best way to look at all of these projects is by language—here is the Github breakdown.

This isn’t accurate, because many of the JavaScript repositories are actually other languages. I forget to make sure Github knows what language a repo is sometimes too. Regardless, it gives you an idea of which programming languages developers are using to work with Swagger—one layer to look consider.

Beyond the programming languages I want to know which platforms and frameworks developers are applying Swagger. Here are 36 frameworks and platforms I’ve identified so far.

AngularJS (reference)

Apache Ant (reference)

Apache Camel (reference)

Apache Maven (reference)

Apache Wink (reference)

ArangoDB Foxx (reference)

BackboneREST (reference)

CakePHP (reference)

CKAN (reference)

Django REST (reference)

Django Tastypie (reference)

elasticsearch (reference)

Express (reference)

Feathers (reference)

Flask (reference)

Flask MongoRest (reference)

Flask Restful (reference)

Gradle (reference)

Grails (reference)

Grape (reference)

Grunt (reference)

Guzzle (reference)

Jersey (reference)

Laravel (reference)

LINQPad (reference)

MongDB (reference)

Nancy (reference)

Pyramid (reference)

Salesforce (reference)

Sequelize (reference)

Silex (reference)

Sinatra (reference)

Spring (reference)

Symfony (reference)

Tornado-JSON (reference)

Veneer (reference)

Beyond the programming languages, frameworks, and platform integrations I’m looking to also understand the types of tools developers are actually building, and take Swagger beyond what the core development team, and working group could do. It is hard to understand the objectives of each of the developer projects I came across, but here are the X areas I’ve identified so far:

This added a couple stops along the API life cycle for me, that Swagger is serving. I hadn’t envisioned a Swagger powered CLI or Powershell tool. I’ve only lightly thought about proxies, and aggregators driven by Swagger. When you bundle this with the platforms above who have integrated Swagger into their products and services, it starts to paint an even bigger picture of what is possible with Swagger.

I think I’m going to wrap up this dive into the Swagger ecosystem here. I still have all of the contributors, watchers, and people who have forked the core Swagger products, and well as many of the people involved in Swagger discussions via the Swagger Google Group and Twitter account to consider. Plus I think this article will flush out some other projects that are out there, being executed by my readers. Storytelling along the way is the best way to flush out hidden details in my opinion, and is one of the main reasons I’m so transparent--I depend on people emailing and tweeting at me about stuff.

This exercise has given me a new perspective on the Swagger community, and introduced me to some new companies, and tools. If you are doing anything cool with Swagger, please let me know, and I’ll add it to my research. Remember, if you don’t tell the story about what your are doing with APIs, nobody knows, including me—API evangelism 101. This is just my first attempt to better quantify the Swagger community, and I’m happy to include what you are up to in future updates.