title: Multi-Level Routing in ASP.NET web API without Areas
body: <p>I'm trying to use the new ASP.NET Web API to do the following:</p>
  
  <p>A GET to <code>/api/business/{id}</code> gets the business's directory information. A PUT to the same URL updates the information, etc. That part works fine. The problem I'm having comes when I want to add what would formerly have been an action, to view reviews of that business. Ideally I want to be reachable at <code>/api/business/{id}/reviews</code>, where a GET returns the reviews, a POST submits a new review, and so forth. </p>
  
  <p>In a normal ASP.NET MVC application, I could define two action methods (Reviews and PostReview) then used attributes to change the action name and accepted HTTP method of the second function. I would expect there's some way to do this with classes in the new system, but I can't figure out what it is and I'm not seeing anything about the issue in the documentation.</p>
  
  <p>Using areas does <em>not</em> work, as best I can tell: I need the <code>/business/{id}</code> URL to work and with areas that breaks.</p>