Improve DELETE response consistency by returning HTTP 204 No Content instead of null #3090
Description
🚀 Describe the new functionality needed
Description
Currently, the multiple endpoints return a null body with a 200 OK status code for successful DELETE requests. This behavior is inconsistent with standard RESTful conventions and may cause confusion for API consumers expecting a more semantically appropriate response.
Current Behavior
- HTTP Status: 200 OK
- Response Body: null
Expected Behavior
- HTTP Status: 204 No Content
- Response Body: empty (no body)
Justification
According to RFC 9110, a successful DELETE operation that doesn’t return any resource or metadata should return a 204 No Content status.
Returning null in the response body while using 200 OK can be misleading and may require additional null checks on the client side.
Using 204 No Content aligns with RESTful best practices, improves API clarity, and reduces unnecessary payload processing.
💡 Why is this needed? What if we don't build it?
- Cleaner client-side logic (no need to parse a meaningless null)
- Improved compliance with HTTP standards
- Easier to understand and document API behavior
Other thoughts
No response