Use 201 Created (not 200) when a POST request successfully creates a resource — it is semantically correct?

Use 201 Created (not 200) when a POST request successfully creates a resource — it is semantically correct.

Return 204 No Content for successful DELETE operations instead of 200 with an empty body?

Return 204 No Content for successful DELETE operations instead of 200 with an empty body.

Use 422 Unprocessable Entity for validation errors and 400 Bad Request for malformed requests.

Interactive reference for all HTTP status codes with descriptions, real-world use cases, and live endpoint tester

Interactive reference for all HTTP status codes with descriptions, real-world use cases, and a live endpoint tester — all in your browser.

1Browse all HTTP status codes organized by category (1xx, 2xx, 3xx, 4xx, 5xx).
2Search by code number, name, or description to find a specific status.
3Click any status code to see its description and when to use it.
4Use the live endpoint tester to send a request and see the actual status code returned.
5Copy the status code for documentation or API specs.

Use 201 Created (not 200) when a POST request successfully creates a resource — it is semantically correct.
Return 204 No Content for successful DELETE operations instead of 200 with an empty body.
Use 422 Unprocessable Entity for validation errors and 400 Bad Request for malformed requests.

OneKitTools TeamUpdated 2.21.4