.Net Core 3.1 API Routing not working as expected

Question

I have a fairly simple controller for my API. One method returns all devices, and another method returns information on just one. Both of them are HttpGet.

My route definition:

[Route("api/device/list/{Id}")]
[ApiController]
public class DeviceController : ControllerBase

This method is always called when I pass in an ID:

[HttpGet]
public ActionResult<poiDevices> GetDeviceList()

The PostMan URL looks like this:

https://localhost:5001/api/device/list/mycoolid

When the call above is made I want it to call this method below, defined as such with an Id parameter:

    public ActionResult<DeviceDto> GetDeviceDetails(
    [FromRoute] string Id)

The code above has a placeholder for an Id, so my expectation is for this method to be called, instead the generic method is called which returns all. If I take the Id out of the URL the API returns 404 not found, meaning I messed up the routing piece of this.

What am I missing here?

Venkata Dorisala · Accepted Answer · 2020-06-16 19:04:00Z

4

You should change your controller like this.

[Route("api/device")]
[ApiController]
public class DeviceController : ControllerBase
{

  [HttpGet]
  [Route("list")]
  public ActionResult<poiDevices> GetDeviceList()  {

  }

  [Route("list/{id}")]
  public ActionResult<DeviceDto> GetDeviceDetails(
    [FromRoute] string Id)   {

  }

}

answered Jun 16, 2020 at 19:04

Venkata Dorisala

5,09510 gold badges58 silver badges93 bronze badges

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

1 Comment

Neo Over a year ago

Damn it, I knew it was simple....decorate the method.....

Collectives™ on Stack Overflow

.Net Core 3.1 API Routing not working as expected

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related