liveBook · Manning

Minimal API

A minimal API is an ASP.NET Core programming model for defining HTTP endpoints with minimal framework ceremony, without requiring controller classes.

How 3 Manning books explain it

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
Uses minimal APIs to build HTTP backends for mobile and single-page applications while introducing ASP.NET Core mechanics.
How deep it goes
Explains template setup, endpoint mapping, HTTP verb semantics, and controller tradeoffs with a small endpoint example.
Examples
Uses a Hello World application and a GET endpoint that filters people by first name.
What you can do after
Apply minimal APIs via ASP.NET Core to create a small HTTP application and map endpoints to appropriate verbs.

Read how ASP.NET Core in Action, 3e explains minimal API →

.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 →

Also covered in

What to know first

Related concepts

Questions about minimal API

What is minimal API?

A minimal API is an ASP.NET Core programming model for defining HTTP endpoints with minimal framework ceremony, without requiring controller classes.

Which Manning books explain minimal API?

ASP.NET Core in Action, 3e, .NET in Action, Second Edition and Building Web APIs with ASP.NET Core.

What should I know before learning minimal API?

Manning books that teach minimal API usually introduce JSON, web application, lambda and gRPC first.

What is the difference between minimal API and controller?

A minimal API is an ASP.NET Core programming model for defining HTTP endpoints with minimal framework ceremony, without requiring controller classes. A controller is a software component that receives input or requests and coordinates other components or operations to produce a response or change application state.

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.