add-api-endpoints

To add new API endpoints in .NET, you extend existing controllers with new routes and actions. This process follows clean architecture principles by mapping new routes to established controller structures, use cases, interfaces, and facades.

The best way to extend Query.Api and Upload.Api is to follow their established patterns. You implement new Upload.Api routes using an Interface plus UseCase pattern, and new Query.Api routes using a Controller plus Facade pattern.

Adding new controller actions in .NET requires adherence to existing clean architecture patterns to ensure consistency. You must align new endpoints with established use cases, interfaces, and controller structures already present in the application.

To create a GET endpoint retrieving user data in .NET, you build the necessary DTOs, implement facade methods, and add controller actions. This ensures the new API endpoint integrates cleanly with the existing Query.Api architecture.

You can implement new controller actions without disrupting existing API interfaces by adhering to clean architecture principles. The Skill ensures new routes follow established use case and facade patterns, maintaining architectural consistency.

A key limitation when extending Web API endpoints is the strict dependency on existing clean architecture patterns. You must conform to the specific Interface, UseCase, Controller, and Facade structures already defined within the Query.Api and Upload.Api projects.