haskell-servant

What problem does it solve?

Building scalable, type-safe REST APIs in Haskell with Servant can be verbose and error-prone; NamedRoutes patterns reduce boilerplate and enforce a consistent structure across resources.

Core Features & Use Cases

• Enforces NamedRoutes records per resource, with Generic derivation for API composition
• Supports nested routing, per-resource handlers, and service-layer separation
• Includes authentication, error handling, and OpenAPI documentation integration
• Use Case: Design multi-resource APIs (e.g., User, Product) with consistent routes and handlers

Quick Start

Define your API with NamedRoutes records, implement handlers mirroring those records, and wire them into a Servant application.