When comparing Apiary vs Servant, the Slant community recommends Servant for most people. In the question“What are the best Haskell web frameworks for building RESTful web services?” Servant is ranked 7th while Apiary is ranked 11th. The most important reason people chose Servant is:
Ranked in these QuestionsQuestion Ranking
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 Automatic documentation and Haskell/JS query generation
servant-client for Haskell.
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 Route definitions are more verbose and complicated than other options
You are required to define a number of separate complicated types and their implementations which are usually spread out over a number of files. This makes it hard to figure out the API.
Con Route specifications and implementations are only connected by their position in a large type list
You actually have to count the index of the entry where you changed the specification, and then go and change the entry at the same index in the list of implementation methods. There is no other indication that the two are connected. This along with complex and verbose route definitions, makes it very hard to safely make changes to an API.
Con No built-in authorization handling
Currently, authorization must be handled through some other package (or custom code). Managing authorization directly within Servant, including OAuth and other tokens, is under development.