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

Usa 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 con an empty body?

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

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

Riferimento rapido per tutti i codici di stato HTTP con descrizioni

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

1Sfoglia all HTTP status codes organized by category (1xx, 2xx, 3xx, 4xx, 5xx).
2Cerca per numero codice, nome o descrizione per trovare uno stato specifico.
3Clicca any status code to see its description and when to use it.
4Usa the live endpoint tester to send a request and see the actual status code returned.
5Copia the status code for documentation or API specs.

Usa 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 con an empty body.
Usa 422 Unprocessable Entity for validation errors and 400 Bad Request for malformed requests.

Team OneKitToolsAggiornato 2.21.4