{"API Evangelist"}

API Design Tooling From API Blueprint

Swagger is now Open API Definition Format (OADF) -- READ MORE

As part of my research in the world of API design, I’m looking into the different approaches by API Blueprint, RAML and Swagger, to provide API definitions, services and tools that assist developers in better designing APIs. I have already look at the evolving motivations behind API definitions, and some insight into the vision behind Swagger, API Blueprint and RAML, next up is taking a look at the tooling that is emerged around each approach.

I began with a look at the tooling around Swagger, and next up is to look at API Blueprint, from Apiary.io, which is centered around a markdown based API definition language:

To put API Blueprint to use, Apiary provides a parser:

When it comes to tooling around API Blueprint, it is all about the Apiary.io platform:

Apiary.io delivers the features we are seeing emerge around Swagger and RAML, and more:

I did find two other open tools for API Blueprint:

I’d say that Apiary with API Blueprint was the first company dedicated specifically to API design. Swagger was born as a set of tools out of Wordnik, and not designed to be a product, with RAML coming later. While Swagger was pushing API design into new areas beyond just interactive docs, Apiary and API Blueprint was the first API design only startup to emerge.

During 2006-2012, API management was being standardized by pioneers like Mashery, 3Scale and Apigee--now API design is now being defined by providers like Swagger,  API Blueprint, and RAML. It shows that the API space is continueing to expand and mature, increasing the need to refine not just API design, but the overall API lifecycle. 

Updated November 27, 2015: Links were updated as part of switch from Swagger to OADF (READ MORE)