From the Deleting resources of the JSON:api spec topic (emphasis mine):
A server MUST return a
200 OKstatus code if a deletion request is successful and the server responds with only top-level meta data.
We are using a “soft delete” pattern, so this makes our
DELETE implementation feel more like a
PATCH, e.g., from the JSON:api
If a server accepts an update but also changes the resource(s) in ways other than those specified by the request (for example, updating the
updated-atattribute or a computed
sha), it MUST return a
200 OKresponse. The response document MUST include a representation of the updated resource(s) as if a
GETrequest was made to the request URL.
DELETE spec reads, without an example, that the representation of the updated resource would not be returned. However, I’m thinking it should be, versus a single top-level
meta object (as I read the spec, the only permitted response content is a top level
Thoughts on including the updated resource in the
200 OK for a
DELETE where a soft delete is the implementation?