11
20 Comments

Which tool do you use to document APIs?

Exploring options to document APIs that can be exposed to third parties for their use. Which tool do you recommend?

Evaluation parameters are -

  1. Ease of use
  2. Good design
  3. Good pricing
  4. Ability to have custom domains/sub-domains
  1. 6

    Maybe Swagger could fit your needs.

    1. 3

      +1 to swagger for REST APIs . It's free, it's open source and it can be packaged into your project. Make sure that it is integrating into your codebase strictly. There are tons of solution for specific frameworks you are based on.
      Maintaining API documentation and codebase separately could cause headache.

    2. 1

      +1 for swagger. We use .NET and Swagger for our api documentation.

    3. 1

      Swagger is by far the best UI for Restful services

  2. 3

    I would recommend Codegiant.io to created good documents. Example - https://docs.codegiant.io/codegiant/api

    PS - I am the founder of Codegiant (:wink)

  3. 2

    RAML, it's much more concise and abstracted at a higher level than swagger.

    1. 2

      Looks very clean and super-simple pricing.

      Thanks for introducing this :)

  4. 1

    Our engineers constantly create documentation for customers and, from our experience, the best and most maintainable were those not making use of any service, probably just using node or a simple static site generator.

  5. 1

    We use swagger combined with https://github.com/sourcey/spectacle hosted on s3 as a static site.

  6. 1

    Currently using this http://apidocjs.com
    However swagger looks good too

    1. 1

      This seems decent. But, the design does not impress.

  7. 1

    Hi, take a look at https://vuepress.vuejs.org/ . Maybe it works for your purpose.
    It is not specific to APIs but is a great tool.

    1. 1

      This deviates from my requirement right now. But, overall a good site.