200 OK
on the successful deletion, but when removing a resource deleted earlier, responds with 204 No Content
(conforming FHIR specification). This feature was added to make deletion work the same way as in SQL DELETE RETURNING *
.If-Match
header, with versionId
as ETAG.204 No Content
instead of 200 OK
, use the _no-content=true
query parameter. 200
OK - resource successfully deleted204
No Content - resource already deleted404
Not Found - resource not found412
Precondition Failed - requested ETAG doesn't match actualdelete
on no matches. That's why 404 Not Found
will be returned in this case.404 Not Found
delete
on the matching resource412 Precondition Failed
error indicating the client's criteria were not selective enough200 OK
on the successful deletion, but when removing an already deleted resource, it responds with 204 No Content
. 204 No Content
instead of 200 OK
, use _no-content=true
query parameter.200
OK — resource successfully deleted204
No Content — resource already deleted200
OK200
204
No Content204
404 Not Found
delete
on the matching resource412 Precondition Failed
error indicating the client's criteria were not selective enough