15

There are a variety of good tools out there for source code and API documentation (doxygen, Headerdoc, Sphinx, to name but a few). However, none of them appear especially good at producing documentation for APIs that are provided via an RPC interface (if you have recommendations on how to synthesize RPC API documentation with these tools, by all means suggest it).

I am specifically interested in documentation tools which have at least some support for JSON and AMQP, but the question would also stand for things like Protobuf, Thrift, and XML-RPC and any tool suggestions that work with those technologies would at least give me a place to start.

I honestly have yet to see quality documentation for any RPC interface (either produced by hand or by a tool), and I'm just hoping that's because developers are lazy and not because the tools don't exist.

albert
  • 8,285
  • 3
  • 19
  • 32
Nick Bastin
  • 30,415
  • 7
  • 59
  • 78
  • similar question? http://stackoverflow.com/questions/6254171/what-is-the-best-tool-for-documenting-generate-reference-for-a-restful-http-rpc – Pranalee Jun 11 '12 at 07:56

1 Answers1

1

Take a look at Swagger (http://swagger.wordnik.com) - this is what we use for all our apis at 3scale (http://www.3scale.net). Basically it'll take a JSON spec and do various things including create interactive API docs for you. RPC style docs should be fine (we amended it to take / receive XML). There are also tools for generating the specs from code for various languages.

Lastly, there's a simple code extractor tool which can create the JSON: https://github.com/solso/source2swagger. All this is less formalised than Doxygen etc. but might be useful to check out.

steve
  • 1,978
  • 13
  • 23
  • +1 Very nice. We implemented something by hand that essentially does the same thing. But, this is much better. Great job! – Homer6 Jul 16 '13 at 19:32