Attribute routing with optional parameters in ASP.NET Web API

Question

I'm trying to use Web API 2 attribute routing to set up a custom API. I've got my route working such that my function gets called, but for some reason I need to pass in my first parameter for everything to work properly. The following are the URLs I want to support:

http://mysite/api/servicename/parameter1 http://mysite/api/servicename/parameter1?parameter2=value2 http://mysite/api/servicename/parameter1?parameter2=value2&parameter3=value3 http://mysite/api/servicename/parameter1?parameter2=value2&parameter3=value3&p4=v4

The last 3 URLs work but the first one says "No action was found on the controller 'controller name' that matches the request."

My controller looks like this:

public class MyServiceController : ApiController { [Route("api/servicename/{parameter1}")] [HttpGet] public async Task<ReturnType> Get(string parameter1, DateTime? parameter2, string parameter3 = "", string p4 = "") { // process } }

mbomb007 · Accepted Answer · 2015-12-29 15:49:21Z

67

Web API requires to explicitly set optional values even for nullable types...so you can try setting the following and you should see your 1st request succeed

DateTime? parameter2 = null

edited Dec 29, 2015 at 15:49

mbomb007

4,3913 gold badges51 silver badges79 bronze badges

answered Mar 14, 2014 at 6:27

Kiran

58.1k16 gold badges179 silver badges163 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Colin Over a year ago

What did your RouteAttribute end up looking like to support the optional parameters (or what does the request URL look like if your route is simply like the original post)?

Collectives™ on Stack Overflow

Attribute routing with optional parameters in ASP.NET Web API

1 Answer 1

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Linked

Related