Minimal API
A minimal API is an ASP.NET Core programming model for defining HTTP endpoints with minimal framework ceremony, typically without controller classes.
ASP.NET Core in Action, 3e
A minimal API endpoint is an addressable operation in a minimal API application that handles a request with minimal surrounding framework structure.
- How it is used
- Exposes HTTP operations to clients such as mobile apps and browser-based single-page applications.
- How deep it goes
- Shows route-and-handler mapping and HTTP verb choices, then compares API approaches without detailing endpoint internals here.
- Examples
- Uses a Hello World starter application and a `MapGet` handler that filters people by first name.
- What you can do after
- Apply it via ASP.NET Core mapping methods to define an endpoint and choose a verb suited to its operation.
.NET in Action, Second Edition
Minimal APIs are an ASP.NET Core programming model for defining HTTP endpoints with minimal ceremony and without requiring controller classes.
- How it is used
- Turns C# operations into HTTP endpoints with little boilerplate and no explicit controller class.
- How deep it goes
- Works through project creation, route and query parameters, and response selection; defers controller-based MVC.
- Examples
- Uses an ASCII art service with optional fonts and a barcode endpoint that returns a JPEG image.
- What you can do after
- Build it from scratch as a small ASP.NET Core service and choose content, file, or not-found responses.
Read how .NET in Action, Second Edition explains minimal API →
Building Web APIs with ASP.NET Core
Minimal APIs are an ASP.NET Core style for defining HTTP endpoints with minimal ceremony and without requiring controller classes.
- How it is used
- Defines lightweight HTTP endpoints when reduced ceremony and overhead suit simple APIs or microservices.
- How deep it goes
- Shows route mapping, handler placement, controller trade-offs, and Swagger grouping without explaining framework internals.
- Examples
- Uses sample route mappings, board-game responses, an authorized test endpoint, and explicit Auth Swagger tags.
- What you can do after
- Apply it via ASP.NET Core route mapping, then choose between minimal APIs and controllers as endpoint complexity grows.
Read how Building Web APIs with ASP.NET Core explains minimal API →
Related concepts
- controlleralternative to · A controller is a software component or architectural role that receives inputs or requests and coordinates their handling by other parts of an application.
- endpointused by · An endpoint is a network-accessible address or interface through which a service exposes a resource or operation and handles requests and responses.
- IResultuses · IResult is an ASP.NET Core interface representing the result produced by executing an HTTP endpoint.
- contractalternative to · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
- web servicekind of · A web service is a programmatic software interface that exposes functionality or data through web technologies or network protocols, typically HTTP.
- System.Text.Jsonused by · System.Text.Json is a .NET library providing APIs for serializing, deserializing, reading, writing, and processing JSON data.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.