effect-http-api

Generate OpenAPI documentation and derive type-safe clients from a single Effect HttpApi definition. This schema-first approach eliminates manual translation, reducing drift between server handlers, generated API docs, and typed client interfaces.

Define security middleware and schema validations for params, query, headers, and payloads within your HttpApiGroup. The Effect HttpApi module wraps these codecs and applies security layers to ensure correct handling of encodings, status codes, and multipart responses.

The best way to prevent schema drift is using a schema-first HTTP API definition. By defining endpoint schemas once in Effect Schema, runtime validation, OpenAPI generation, and type-safe client derivation all share the exact same source of truth.

Yes, the Effect HttpApi module supports correct handling of multipart and no-content responses. It manages encodings, status codes, and optional security middleware layers within the schema-first endpoint definitions.

Add security and middleware layers to an Effect HTTP API by applying them within your HttpApiGroup definition. This ensures that schema validation, security protocols, and handler logic are integrated and tested together using HttpApiBuilder.