Tools to generate beautiful web API documentation

February 15, 2013 // Programming

Edit 6/16/2013: It’s been a few months, and we finally ended up going with the Swagger-based documentation built into  Want to see how it looks?  Head over to

— Begin original post —

As demand for our Nutritionix API is starting to grow rapidly, we have been working on finding an API documentation engine to meet our needs for the long-term.  I was not able to find any comprehensive list of existing API documentation solutions, so I am compiling what I have found so far. Please leave feedback on your own experience in the comments.

Web API Documentation Tools

We are still exploring each solution, but I will update this post as we learn more about each option.

  • Swagger – A specification and complete framework implementation for describing, producing, consuming, and visualizing RESTful web services. [Demo]
    • Note: We already use for our API management solution, and they have an ActiveDocs feature based on Swagger.
  • I/O Docs – By defining APIs at the resource, method and parameter levels in a JSON schema, I/O Docs will generate a JavaScript client interface [Demo].  I/O docs was created by the API management platform Mashery.
  • – Provides very quick way to get your documentation up and running, includes GitHub integration and I/O validation. – Suggested by Siyfion via Reddit.
  • Docco – Docco is a quick-and-dirty, hundred-line-long, literate-programming-style documentation generator. It produces HTML that displays your comments alongside your code.
  • Dexy – Flexible documentation tool that supports any language, for any API.
  • Doxygen – Generate an on-line documentation browser (in HTML) and/or an off-line reference manual, and you can configure doxygen to extract the code structure from undocumented source files.  Seems more technical than the other options, but a powerful option nonetheless.  Suggested by gkumar007 via Reddit.
  • TurnAPI – Paid service.  Intelligent WIKI-editor, markdown based standards, documentation branching, sync with Git, SVN, Mercurial, clean looking themes. [Features]
    • Note: As of writing I was unable to create an account at TurnAPI.

Edit 6/16/2013: It’s been a few months, and we finally ended up going with the Swagger-based documentation built into  Want to see how it looks?  Head over to

About the author

Co-founder, Managing Partner,


  1. I was certainly finding the one of tool to generate documentation for an web map API, i recently developed. Thanx for the list.

  2. I create some time ago a small open source tool “apiDoc”
    It creates a documentation from the inline code of an application.

    It run with nodejs, but it can be used for every programming language, not only JS.

  3. Yves Vandewoude May 20, 2013 at 11:48 am

    Hey Matt,

    If you’re documenting Rest APIs, and you’re using Java/JaxRS, you might take a look at MireDot ( It grew from a tool we initially developped within our company, to document rest interfaces for our clients. We have recently decided to make this tool publically available (free for open source projects). It’s distributed as a Maven plugin, and uses existing JaxRS annotations and javadoc tags to generate the documentation.


  4. Hi Matt,

    Nice article. We have recently launched Simulty, a website combinator where you can navigate multiple sites simultaneously. I have created an example list taking your selection on this article (giving you, of course, full credit).

    I would ask you for your opinion on how useful can Simulty be for you to promote articles like this one.

    Thanks and regards

  5. I have personally used doxygen some 5 years ago on my Java code base. And it was fantastic documentation tool.

  6. Originally, on our site, we decided to write free form and then present API Console from Apigee. Definitely room for improvement. Currently evaluating transition to Apiary. Apigee Console is awesome, but free version is not fully integrated with documentation.
    Matt, I recommend you mistake distinction between free and paid tools.

  7. Great list, Matt!

    We’re still developing our API, but we’ll be needing to ramp up our documentation efforts as well. I’d love your thoughts on the “interactive link relationship tree diagram”

    We’re doing a Hypermedia API and most of the documentation systems out there I’ve seen focus on the URL which I think is fundamentally flawed as it encourages client developers to code to the URL instead navigating the link relationships.

Leave a Comment