Web API Route Design for Non-CRUD Routes

added by DotNetKicks
12/14/2016 3:03:56 PM

1 Kicks, 420 Views

I've been finding myself thinking a lot about route design for the web APIs I've been building lately. For your basic CRUD (Create, Read, Update, Delete) controllers, everyone knows that the POST HTTP verb maps to create/insert; GET maps to read/select; PUT maps to update; and DELETE maps to-brace yourself-delete.