WebAPI2中正确的RESTful实现是什么？

Question

Essentially I have found a waste number of opinions on this topic, but none that convinces me what is correct. More specifically I have the following questions:

Singular or Plural or both

• Is there even a correct and a wrong way?

  Standards and conventions exists for a reason, I don´t believe I will ever settle for - it´s just a matter of taste . Isn´t there any guideline or standard? No authority completing Fieldings work?

What IHttpActionResults to return? And what should they contain?

• Get - return Ok();
• Post - return Created();
• Put - return (Put? Ok?)
• Delete - return (Deleted? Ok?)

What to return in Created( location )?

Assuming the Controller route is 'api/v1/model', should it be

• '/{id}'?
• 'api/v1/model/{id}'?
• ' http://www.mywebapi.com/api/v1/model/ {id}'?

I ask these questions because I frequently run into conflicts about how to best implement APIs.

Answer 1

Q: Singular or Plural or both

Never use both. Use either one. Use noun but not verbs.

Do not use verbs:

/getAllCars
/createNewCar
/deleteAllRedCars

Do not mix up singular and plural nouns. Keep it simple and use only plural nouns for all resources.

/cars instead of /car
/users instead of /user
/products instead of /product

Now if you see below, it will make more sense:

GET /tickets - Retrieves a list of tickets
GET /tickets/12 - Retrieves a specific ticket
POST /tickets - Creates a new ticket
PUT /tickets/12 - Updates ticket #12
PATCH /tickets/12 - Partially updates ticket #12
DELETE /tickets/12 - Deletes ticket #12

If a resource is related to another resource use subresources.

GET /cars/711/drivers/ Returns a list of drivers for car 711

Q: What to return in Created(location)?

200 OK - Response to a successful GET, PUT, PATCH or DELETE. Can also be used for a POST that doesn't result in a creation.

201 Created - Response to a POST that results in a creation. Should be combined with a Location header pointing to the location of the new resource

Provide clarity on your last question and I'll update my answer accordingly.

There're no defined standards for REST and everyone uses best practices as per their need. However I would suggest you to go through this PDF from apigee.com which lists down the best practices for REST API and what each of the big player ie Facebook, twitter etc uses.