api-endpoint

To create a CRUD API endpoint with Clean Architecture, provide a feature name and data model to generate a complete endpoint skeleton. The output includes RESTful routes, validation hooks, and MediatR request handling aligned with .NET 10 conventions.

The best way to structure a REST API endpoint using MediatR is to separate Application and API layers. This approach scaffolds request handlers and standard validation hooks, ensuring consistent architecture across new endpoints.

Yes, this Clean Architecture scaffolding supports .NET 10 and C# 14 conventions. It applies these standards to streamline adding new controllers, routing configurations, and CRUD operations with a consistent project structure.

To add standard validation hooks to a dotnet API controller, generate the endpoint using a Clean Architecture pattern. This automatically includes validation guidance and scaffolds MediatR-based request handling for the new feature.

To scaffold a new API endpoint skeleton, you need to provide a feature name and a data model. The system then generates a complete CRUD API with Application and API layers following Clean Architecture.