HTTP Response Codes
- Igor Dantas Silva (Unlicensed)
The HTTP response codes present in Open Keys cover the descriptive table below.
Situation | HTTP code | Grades | POST | GET | DELETE | PATCH | PUT |
|---|---|---|---|---|---|---|---|
Query completed successfully. | 200 OK. | In the case of POST, return 200 only when it does not change the resource | Yes | Yes | No | Yes | Yes |
Normal execution. The request was successful. | 201 Created. | The operation results in the creation of a new resource. | Yes | No | No | No | No |
Delete operation completed successfully. | 204 Not Satisfied. |
| No | No | Yes | No | No |
The request was malformed, omitting mandatory attributes, either in the payload or through attributes in the URL. | 400 Bad Request. | The requested operation will not be performed. | Yes | Yes | Yes | Yes | Yes |
Missing/invalid authentication header or invalid token . | 401 Unauthorized. | The operation was refused due to an authentication problem. | Yes | Yes | Yes | Yes | Yes |
The requested feature does not exist or has not been implemented. | 404 Not Found. |
| Yes | Yes | Yes | Yes | Yes |
The request was well-formed but could not be processed due to the specific business logic of the request. | 422 Unprocessable Entity. | If applicable to the endpoint , this error is expected to result in an error payload . | Yes | Yes | No | Yes | Yes |
An error occurred in the API gateway or microservice. | 500 Internal Server Error. | The operation failed. | Yes | Yes | Yes | Yes | Yes |