"..swagger repeats itself a lot with redundant annotations, it also leads to having more annotations than actual code." (Shameless plug) For this exact problem

"..swagger repeats itself a lot with redundant annotations, it also leads to having more annotations than actual code." (Shameless plug) For this exact problem, we developed a Java library that makes easy to create RESTFul services that's highly integrated with Swagger. Here it is: https://github.com/buremba/netty-rest https://github.com/buremba/netty-rest We also tried hard to stick with Swagger-codegen but it's far from being stable so eventually we ended up creating a Slate documentation that demonstrates the usage of API with high level HTTP libraries for various programming languages. We convert Swagger spec to HAR representation, create the example usage of the endpoint with httpsnippet from the HAR (https://www.npmjs.com/package/httpsnippet https://www.npmjs.com/package/httpsnippet) and embed it in our Slate documentation using our Slate documentation generator. (https://github.com/buremba/swagger-slate https://github.com/buremba/swagger-slate) Here is an example: http://api.rakam.io/ http://api.rakam.io/