It’s doable by a custom model binder as mentioned in the comment. Here is a few code snippets to wire everything up, with the example you can send a http request with the following JSON body to an API /api/cats?From=james&Days=20 { “Name”:””, “EyeColor”:”Red” } A few classes, you can find them here as well: https://github.com/atwayne/so-51316269 … Read more
Try this. You can put a common route prefix on the controller. [Route(“api/[controller]”)] public class BXLogsController : Controller { //GET api/BXlogs/id/blah [HttpGet(“ID/{id}”, Name = “GetL”)] public IActionResult GetById(string id) { … } //GET api/BXlogs/api/blahapi [HttpGet(“API/{apiname}”, Name = “GetLAPI”)] public IActionResult GetByAPI(string apiname) { … } } read up on attribute routing here Routing to Controller … Read more
What you’re trying to do is impossible because the actions are dynamically activated. The request data (such as a query string) cannot be bound until the framework knows the action signature. It can’t know the action signature until it follows the route. Therefore, you can’t make routing dependent on things the framework doesn’t even know … Read more
For ASP.NET Core: Add one of the following lines to the ConfigureServices method of the Startup class: services.AddRouting(options => options.LowercaseUrls = true); or services.Configure<RouteOptions>(options => options.LowercaseUrls = true); Thanks to Skorunka for the answer as a comment. I thought it was worth promoting to an actual answer.
You also can use this: // GET api/user/firstname/lastname/address [HttpGet(“{firstName}/{lastName}/{address}”)] public string GetQuery(string id, string firstName, string lastName, string address) { return $”{firstName}:{lastName}:{address}”; } Note: Please refer to the answers from metalheart and Mark Hughes for a possibly better approach.