404 when calling ASP.Net Core API

Question

I have an ASP.Net Core MVC app with a Web API controller, I believe i provided the right routes and everything but i still get a 404 error when calling the any API of the controller in Postman

here is how the controller looks:

[Route("api/[controller]")]
    [ApiController]
    public class PetsController : Controller
    {
        private readonly IPetService _petService;

        public PetsController(IPetService _petService)
        {
            this._petService = _petService;
        }

        [HttpPost("Activation")]
        public async Task<IActionResult> Activation(Guid id)
        {
            var serviceResult = await _petService.DeletePet(id);
            return Ok(serviceResult);
        }

        [HttpGet("GetPet/{id}")]
        public async Task<IActionResult> GetPet(Guid id)
        {
            var serviceResult = await _petService.GetPetDetails(id);
            return Ok(serviceResult);
        }

        [HttpGet("GetPets/{pageSize}/{pageIndex}/{keyWord}")]
        public async Task<IActionResult> GetPets(int pageSize, int pageIndex, string keyWord)
        {
            var serviceResult = await _petService.GetPets(pageSize, pageIndex, keyWord);
            return Ok(serviceResult);
        }

        [HttpPost("SavePet")]
        public async Task<IActionResult> SavePet(PetDTO pet)
        {
            var serviceResult = (Object)null;

            if (!pet.Id.HasValue)
                serviceResult = await _petService.CreatePet(pet);
            else
                serviceResult = await _petService.EditPet(pet);

            return Ok(serviceResult);
        }

        [HttpGet("GetPetDues/{id}")]
        public async Task<IActionResult> GetPetDues(Guid id)
        {
            var serviceResult = await _petService.GetPetDues(id);
            return Ok(serviceResult);
        }

        [HttpGet("GetPetAppointments/{id}")]
        public async Task<IActionResult> GetPetAppointments(Guid id)
        {
            var serviceResult = await _petService.GetPetAppointments(id);
            return Ok(serviceResult);
        }

        [HttpGet("GetPetDiseases/{petId}")]
        public async Task<IActionResult> GetPetDiseases(Guid petId)
        {
            var serviceResult = await _petService.GetPetDiseases(petId);
            return Ok(serviceResult);
        }
    }

Launch settings:

"iisSettings": {
    "windowsAuthentication": false, 
    "anonymousAuthentication": true, 
    "iisExpress": {
      "applicationUrl": "http://localhost:50521",
      "sslPort": 44310
    }

and this is an examply on how i call an API in Postman: http://localhost:50521/api/pets/GetPets/10/0/

I believe I should get a 200 OK but still im getting a 404 error! How can i fix this??

How do you start the application?

Nicola
– Nicola

2019-10-03 15:36:29 +00:00
Commented Oct 3, 2019 at 15:36 — Nicola
– Nicola, Commented Oct 3, 2019 at 15:36
@Nicola I press on IIS Express

Khaled
– Khaled

2019-10-03 16:41:06 +00:00
Commented Oct 3, 2019 at 16:41 — Khaled
– Khaled, Commented Oct 3, 2019 at 16:41

Community · Accepted Answer · 2020-06-20 09:12:55Z

1

Route template was not used correctly

[HttpGet("GetPets/{pageSize}/{pageIndex}/{keyWord?}")]
public async Task<IActionResult> GetPets(int pageSize, int pageIndex, string keyWord = null)
{
    var serviceResult = await _petService.GetPets(pageSize, pageIndex, keyWord);
    return Ok(serviceResult);
}

The original route used was missing the template parameters.

In fact all of the shown routes are missing their parameters in the route template.

Route template reference

Tokens within curly braces ({ ... }) define route parameters that are bound if the route is matched. You can define more than one route parameter in a route segment, but they must be separated by a literal value. For example, {controller=Home}{action=Index} isn't a valid route, since there's no literal value between {controller} and {action}. These route parameters must have a name and may have additional attributes specified.

Literal text other than route parameters (for example, {id}) and the path separator / must match the text in the URL. Text matching is case-insensitive and based on the decoded representation of the URLs path. To match a literal route parameter delimiter ({ or }), escape the delimiter by repeating the character ({{ or }}).

Reference Routing in ASP.NET Core

Reference Routing to controller actions in ASP.NET Core

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered Oct 3, 2019 at 1:15

Nkosi

249k38 gold badges472 silver badges506 bronze badges

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

1 Comment

Khaled Over a year ago

Thank you for pointing it out and I fixed it immediately but still i'm getting a 404 error

Collectives™ on Stack Overflow

404 when calling ASP.Net Core API

1 Answer 1

Route template reference

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Route template reference

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related