One of the most confusing aspect of MVC and Web API is the subject of routing. MVC routing looks and feels more logical to most developers as compared to the Web API routing. The reason behind this is that Web API depends on the HTTP verb to match the action being called. It follows a set of conventions which automatically fires a particular action based on the endpoint being hit. This throws of most of us because we are in the habit of calling methods by name.
Hopefully this post will give you a head start at what is the simplest or the default way in which Web API manages its routing based on conventions. I will show all the concepts using simple boiler plate code, don’t focus on the logic inside the Action(method).