RESTful - What should a DELETE response body contain

Question

Let's say I have an API where you can get users:

GET /RESTAPI/user/ 

And you can delete users by:

DELETE /RESTAPI/user/123 

What is the RESTful convention on what the DELETE's response body should contain? I expected it should be the new list of all users which now doesn't contain the user with id 123 anymore.

Googling around didn't get me any satisfying answers. I only found opinions on how to do that, but isn't there a strict definition of RESTful Services?

This is NOT a duplicate of What should a RESTful API POST/DELETE return in the body? and What REST PUT/POST/DELETE calls should return by a convention? since this questions asks for a strict definition regarding DELETE. Those questions were only answered by loose opinions only.

Answer 1

The reason you get no hard answers is because there is no hard RESTful standard. So I can only suggest that you create a hard standard and stick to it within your own APIs

I used this as a guide for RESTful services http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api

It says respond with a 204 status and an empty body

I stick to those standards and document them well for anyone who wants to use my APIs

Answer 2

What is the RESTful convention on what the DELETE's response body should contain?

REST is an architectural style defined by Fielding in the chapter 5 of his dissertation and it describes a set of contraints for applications built with this architecture. REST is designed to be protocol indenpendent but the chapter 6 of the same dissertation describes how REST is applied over HTTP.

Once your REST application is designed on the top of the HTTP protocol, you should be aware of the HTTP semantics. And the semantis of the HTTP/1.1 protocol are currently described in the RFC 7231.

---

The response payload of a DELETE request that has succeeded may:

• Be empty or;
• Include a representation of the status of the action.

And the following response status codes are suitable for a DELETE request that has succeeded:

• 202: The request has been accepted for processing, but the processing has not been completed.
• 204: The server has successfully fulfilled the request and that there is no additional content to send in the response payload body.
• 200: The request has succeeded and the request payload includes a representation of the status of the action.

See the following quote from the RFC 7231:

If a DELETE method is successfully applied, the origin server SHOULD send a 202 (Accepted) status code if the action will likely succeed but has not yet been enacted, a 204 (No Content) status code if the action has been enacted and no further information is to be supplied, or a 200 (OK) status code if the action has been enacted and the response message includes a representation describing the status.