API Spec Comparison Tool
Last updated November 4, 2016
| Attribute | API Blueprint | RAML | Swagger | IO Docs | Mashape | WADL |
| Usability | ||||||
| Spec |  |  | | | N/A | |
| Website | | | | | | |
| Language Support | | | | | N/A | |
| Ease of Getting Started | | | | | | |
| Ease of Spec Maintenance | | | | | | |
| Spec Driven | ||||||
| API Design First | | | | | | |
| Visual API Designer | N/A | | | N/A | | |
| Offline IDE | | | N/A | N/A | N/A | N/A |
| Allows Code Reuse | | | | N/A | N/A | N/A |
| Mocking Service | | | | N/A | | N/A |
| Build Support | ||||||
| Frameworks | | | | N/A | N/A | |
| Applications/ Tools | | | | N/A | N/A | |
| Support Tooling | ||||||
| API Console | N/A | | | | | N/A |
| API Documentation | | | | N/A | | |
| API Interaction | N/A | | N/A | N/A | N/A | N/A |
| API SDK Generation | | | | | N/A | |
| Community | ||||||
| Size | | | | | N/A | |
| Engagement | | | | | N/A | |
| Available Resources | | | | | | |
| Industry Backed Workgroup | | | | | | |
| Summary | ||||||
| Avg. Rating | | | | | | |
* note proprietary tools are not taken into account for specification ratings
Share this Page:
What is Spec Driven Development API Resources
10 Responses to “API Spec Comparison Tool”
Leave a Reply
Opensource Spotlight
Very helpful
Thanks a lot …
I need to decide among these tools . It will help me a lot.
Keep up the good work Mike !!!
Really good representation of the rating and also helpful.
Thanks @mike.
Really good representation of the rating and also helpful.
Thanks @mike
Licensing ?
Will add – but all are open to the public for use commercially or non-commercially.
What do these grey stars and the colored stars indicate?
Hey Varun,
If a specification is the top rated for that category it is given gold stars to indicate it is the clear winner. Otherwise it is given grey stars. If two specifications share the top rating, then neither receives gold stars as there is not a “clear winner” and they both receive grey stars.
Thanks,
Mike
Very useful. Any opinion on 1) simplicity (learning curve) and 2) particular issues in using it with Ruby/Rails etc. Thanks
Hey Pito,
Simplicity is very subjective, but for myself I found RAML the easiest to get started with, followed by Swagger, and then API Blueprint.
As for Ruby/ Rails, Swagger is built into Grape (another Ruby framework for APIs), and has several other tools. RAML has several Ruby projects as well, specifically around testing and client generation. API Blueprint on the other hand has support for Dredd and a Ruby Mocking service. To be honest, outside of that I don’t use these Ruby projects enough to really be able to say which one is best or which route to go for Ruby.
Hope that helps!
Thanks! it helped me a lot!