Multiple actions were found that match the request in Web Api

Question

I keep getting this error when I try to have 2  Get  methods     Multiple actions were found that match the request   webapi   I been looking around at the other similar questions about this on stack but I don t get it   I have 2 different names and using the  HttpGet  attribute   HttpGet  public HttpResponseMessage Summary MyVm vm        return null      HttpGet  public HttpResponseMessage FullDetails         return null

User · Answer

I know it is an old question  but sometimes  when you use service resources like from AngularJS to connect to WebAPI  make sure you are using the correct route  other wise this error happens

User · Answer

Have you tried like    HttpGet  Summary    public HttpResponseMessage Summary MyVm vm        return null      HttpGet  FullDetails    public HttpResponseMessage FullDetails         return null

User · Answer

I found that that when I have two Get methods  one parameterless and one with a complex type as a parameter that I got the same error  I solved this by adding a dummy parameter of type int  named Id  as my first parameter  followed by my complex type parameter  I then added the complex type parameter to the route template  The following worked for me   First get   public IEnumerable lt SearchItem gt  Get             Second get   public IEnumerable lt SearchItem gt  Get int id   FromUri  List lt string gt  layers            WebApiConfig   config Routes MapHttpRoute      name   DefaultApi       routeTemplate   api  controller   id   layers        defaults  new   id   RouteParameter Optional  layers RouteParameter Optional

User · Answer

In my Case Everything was right  1  Web Config was configured properly 2  Route prefix and Route attributes were proper   Still i was getting the error  In my Case  Route  attribute  by pressing F12  was point to System Web MVc but not System Web Http which caused the issue

User · Answer

Please check you have two methods which has the different name and same parameters    If so please delete any of the method and try

User · Answer

This is the answer for everyone who knows everything is correct and has checked 50 times       Make sure you are not repeatedly looking at RouteConfig cs   The file you want to edit is named WebApiConfig cs  Also  it should probably look exactly like this   using System Web Http   namespace My Epic Website       public static class WebApiConfig               public static void Register HttpConfiguration config                      config MapHttpAttributeRoutes                  api Country WithStates           config Routes MapHttpRoute              name   ControllerAndActionOnly               routeTemplate   api  controller   action                defaults  new                  constraints  new   action       a-zA-Z     s  a-zA-Z                      config Routes MapHttpRoute              name   DefaultActionApi               routeTemplate   api  controller   action   id                defaults  new   id   RouteParameter Optional                                I could have saved myself about 3 hours

User · Answer

It might be possible that your webmethods are being resolved to the same url  Have a look at the following link  -  http   www asp net web-api overview web-api-routing-and-actions routing-in-aspnet-web-api  So  you might need to add your methodname to your routing table

User · Answer

After a lot of searching the web and trying to find the most suitable form for routing map if have found the following   config Routes MapHttpRoute  DefaultApiWithId    Api  controller   id    new   id  RouteParameter Optional    new   id      d       config Routes MapHttpRoute  DefaultApiWithAction    Api  controller   action       These mapping applying to both action name mapping and basic http convention  GET POST PUT DELETE

User · Answer

In Web API  by default  methods are chosen based on a combination of HTTP method and route values    MyVm looks like a complex object  read by formatter from the body so you have two identical methods in terms of route data  since neither of them has any parameters from the route  - which makes it impossible for the dispatcher  IHttpActionSelector  to match the appropriate one   You need to differ them by either querystring or route parameter to resolve ambiguity

User · Answer

I ve stumbled upon this problem while trying to augment my WebAPI controllers with extra actions   Assume you would have  public IEnumerable lt string gt  Get         return this Repository GetAll        HttpGet  public void ReSeed            Your custom action here     There are now two methods that satisfy the request for  api controller which triggers the problem described by TS   I didn t want to add  dummy  parameters to my additional actions so I looked into default actions and came up with    ActionName  builtin    public IEnumerable lt string gt  Get         return this Repository GetAll        for the first method in combination with the  dual  route binding   config Routes MapHttpRoute      name   DefaultApi       routeTemplate   api  controller   id        defaults  new   action    builtin   id   RouteParameter Optional        constraints  new   id      d        config Routes MapHttpRoute      name   CustomActionApi       routeTemplate   api  controller   action       Note that even though there is no  action  parameter in the first route template apparently you can still configure a default action allowing us to separate the routing of the  normal  WebAPI calls and the calls to the extra action

User · Answer

Update as of Web API 2  With this API config in your WebApiConfig cs file  public static void Register HttpConfiguration config             Web API routes     config MapHttpAttributeRoutes      Don t miss this      config Routes MapHttpRoute          name   quot DefaultApi quot           routeTemplate   quot api  controller   id  quot           defaults  new   id   System Web Http RouteParameter Optional             You can route our controller like this   Route  quot api ControllerName Summary quot     HttpGet  public HttpResponseMessage Summary MyVm vm        return null      Route  quot api ControllerName FullDetails quot     HttpGet  public HttpResponseMessage FullDetails         return null     Where ControllerName is the name of your controller  without  quot controller quot    This will allow you to get each action with the route detailed above  For further reading  http   www asp net web-api overview web-api-routing-and-actions attribute-routing-in-web-api-2

User · Answer

You can add  Route  api  controller   action     to your controller class    Route  api  controller   action      ApiController  public class MySuperController   ControllerBase

User · Answer

Make sure you do NOT decorate your Controller methods for the default GET PUT POST DELETE actions with  HttpPost Put Get Delete  attribute  I had added this attibute to my vanilla Post controller action and it caused a 404    Hope this helps someone as it can be very frustrating and bring progress to a halt

User · Answer

Without using actions the options would be    move one of the methods to a different controller  so that they don t clash  use just one method that takes the param  and if it s null call the other method from your code

User · Answer

For example     TestController           HttpGet          public string TestMethod int arg0                        return                         HttpGet          public string TestMethod2 string arg0                        return                         HttpGet          public string TestMethod3 int arg0 string arg1                        return                 If you can only change WebApiConfig cs file    config Routes MapHttpRoute                  name   DefaultApi                   routeTemplate   api  controller   action                     defaults  null                  Thats it     And Result

User · Answer

It is possible due to using MVC controller instead of Web API controller  Check the namespace in Web API controller it should be as following  using System Net  using System Net Http  using System Web Http    If the namespace are as following then it is give above error in web api controller method calling  using System Web  using System Web Mvc

User · Answer

This solution worked for me   Please place Route2 first in WebApiConfig  Also Add HttpGet and HttpPost before each method and include controller name and method name in the url   WebApiConfig     config Routes MapHttpRoute             name   MapByAction              routeTemplate   api  controller   action   id    defaults  new   id   RouteParameter Optional             config Routes MapHttpRoute              name   DefaultApi               routeTemplate   api  controller   id                defaults  new   id   RouteParameter Optional       Controller      public class ValuesController   ApiController         HttpPost      public string GetCustomer  FromBody  RequestModel req                return  Customer               HttpPost      public string GetCustomerList  FromBody  RequestModel req                return  Customer List             Url      http   localhost 7050 api Values GetCustomer  http   localhost 7050 api Values GetCustomerList

User · Answer

Your route map is probably something like this   routes MapHttpRoute  name   API Default   routeTemplate   api  controller   id    defaults  new   id   RouteParameter Optional       But in order to have multiple actions with the same http method you need to provide webapi with more information via the route like so   routes MapHttpRoute  name   API Default   routeTemplate   api  controller   action   id    defaults  new   id   RouteParameter Optional       Notice that the routeTemplate now includes an action  Lots more info here  http   www asp net web-api overview web-api-routing-and-actions routing-in-aspnet-web-api  Update   Alright  now that I think I understand what you are after here is another take at this   Perhaps you don t need the action url parameter and should describe the contents that you are after in another way  Since you are saying that the methods are returning data from the same entity then just let the parameters do the describing for you   For example your two methods could be turned into   public HttpResponseMessage Get         return null     public HttpResponseMessage Get MyVm vm        return null      What kind of data are you passing in the MyVm object  If you are able to just pass variables through the URI  I would suggest going that route  Otherwise  you ll need to send the object in the body of the request and that isn t very HTTP of you when doing a GET  it works though  just use  FromBody  infront of MyVm    Hopefully this illustrates that you can have multiple GET methods in a single controller without using the action name or even the  HttpGet  attribute

[c#] Multiple actions were found that match the request in Web Api

Examples related to c#

Examples related to .net

Examples related to asp.net-web-api

Examples related to asp.net-web-api-routing