When comparing Apiary vs Scotty, the Slant community recommends Scotty for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” Scotty is ranked 5th while Apiary is ranked 11th. The most important reason people chose Scotty is:
A simple framework cuts development time and costs. To get started, developers only need to understand how to write routing and actions.
Ranked in these QuestionsQuestion Ranking
Pros

Pro Automatically generates API documentation
Apiary generates comprehensive HTML documentation based on your API routes.


Pro Type-level routes
Apiary provides type modeling, down to URL parameters, ensuring type safety.

Pro Easy to pick up and use
A simple framework cuts development time and costs. To get started, developers only need to understand how to write routing and actions.

Pro Available on gitHub
Having the source code on gitHub means developers can easily suggest improvements and error reports. They also have a community that can help with any problems that come up.
Cons

Con Mediocre documentation
Users must rely primarily on the example project and auto-generated API documentation (Haddocks). The author of Apiary is not a native English speaker and openly acknowledges this issue.
Con Lacks features due to its small size
Since Scotty is small, it does not contain some features that a complex web application may need. Anything that Scotty can't provide must be either found or written, costing developers.
Alternative Products
