Last updated
Was this helpful?
Last updated
Was this helpful?
Responds with 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 *
.
Supports If-Match
header, with versionId
as ETAG.
To get 204 No Content
instead of 200 OK
, use the _no-content=true
query parameter.
200
OK - resource successfully deleted
204
No Content - resource already deleted
404
Not Found - resource not found
412
Precondition Failed - requested ETAG doesn't match actual
It's not clear how to perform an ordinary delete
on no matches. That's why 404 Not Found
will be returned in this case.
No matches: The respond with 404 Not Found
One Match: The server performs an ordinary delete
on the matching resource
Multiple matches: Servers respond with 412 Precondition Failed
error indicating the client's criteria were not selective enough
This interaction deletes a resource, responds with 200 OK
on the successful deletion, but when removing an already deleted resource, it responds with 204 No Content
.
To always get 204 No Content
instead of 200 OK
, use _no-content=true
query parameter.
200
OK — resource successfully deleted
204
No Content — resource already deleted
200
OKDelete a patient by id:
204
No ContentAttempt to delete an already deleted resource:
Depending on the number of resources meeting the search criteria, different actions will be performed and response codes will be returned:
No matches: Respond with 404 Not Found
One Match: The server performs an ordinary delete
on the matching resource
Multiple matches: Servers respond with 412 Precondition Failed
error indicating the client's criteria were not selective enough
By default Aidbox refuses to delete resources when there is multiple matches. If you wish to delete all matching resources, set header
Example: