aspnet-minimal-api-openapi

To generate OpenAPI documentation for ASP.NET Minimal APIs, define typed request and response DTOs and apply endpoint metadata enrichment like WithName, summaries, tags, and status codes to produce automatic, strongly typed contracts.

The best way to organize Minimal API endpoints by feature is using MapGroup() to create route groups. This structures endpoints logically while maintaining strongly typed bindings and comprehensive OpenAPI metadata across services.

To migrate from controllers to minimal APIs with typed contracts, define explicit DTOs with validation attributes for requests and responses, use MapGroup-based routing, and apply endpoint filters to preserve and enrich your API behavior.

Yes, you can use typed DTOs with validation attributes in ASP.NET Minimal APIs. This Skill automates strongly typed request and response bindings, ensuring clear contracts and consistent metadata generation for your endpoints.

To add OpenAPI summaries and status codes to Minimal API endpoints, apply OpenAPI metadata enrichment methods directly to your endpoint definitions. This Skill supports metadata generation and transformers to document status codes and descriptions accurately.

Yes, this approach supports endpoint filters in ASP.NET Minimal APIs. You can apply endpoint filters alongside MapGroup-based routing and typed DTO contracts to handle cross-cutting concerns while generating comprehensive OpenAPI documentation.