Overview
A high-level view of what the Wrapsfer API is today. It is a deliberately
Getting Started
Run the Wrapsfer API locally and verify it works.
Endpoint Reference
Every endpoint that exists in the Wrapsfer API today. Examples assume the API is running at http8080 (the Docker Compose default). Substitute your own host and port — see Getting Started for the launch-profile defaults.
Business Rules
The Wrapsfer API today implements a single business concept — greetings — used as a sample to demonstrate the layered architecture. This page lists every rule that exists in the codebase, separating them by the layer that enforces them, and is explicit about what is not a business rule today.
Errors & Validation
How the Wrapsfer API responds to invalid requests today, and how unhandled exceptions are translated into HTTP responses. Both flows return RFC 7807 application/problem+json bodies but come from different layers — model validation is provided by ASP.NET Core, and the 500 fallback is provided by ExceptionHandlingMiddleware.
OpenAPI
The Wrapsfer API exposes a generated OpenAPI document via Microsoft.AspNetCore.OpenApi. The document is registered for every environment but only mapped in Development, so it is reachable on local and Compose runs but not from a production deployment.