The following code example demonstrates how you can implement an Web ApiController. You can inject a parameter in the controller's constructor leveraging the Ninject bindings. For more information, see Implement the service layer with Ninject.
RECOMMENDATION: To make sure you can easily differentiate between the Classic MVC controllers and widget controllers, we recommend that you place the ApiController in the <root>/ApiControllers folder.
Once you build the project, the controller gets the service as a parameter to its constructor. When you request the domain/api/<ControllerName>/get route, the controller is executed by the ASP.NET pipeline and returns the corresponding string.
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
The free standalone Web Security lesson teaches administrators how to protect your websites and Sitefinity instance from external threats. Learn to configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important