I have an ASP.NET Web API project with an ApiController
that provides a User
endpoint with the following actions:
GET /api/User
POST /a
If you are using Web API 2, I would suggest to use attribute routing which makes the experience easier for scenarios like these.
You can continue using the default conventional route for majority of your scenarios, but can use attribute routing in places where you are required to, like in your current scenario.
Following sample demonstrates a similar scenario:
http://aspnet.codeplex.com/SourceControl/latest#Samples/WebApi/WebApiAttributeRoutingSample/WebApiAttributeRoutingSample/Controllers/Api/CustomersController.cs