Os códigos de resposta HTTP presentes no Open Keys abrangem a tabela descritiva abaixo.
...
Situação
...
Código HTTP
...
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, |
Sim
Sim
Não
Sim
Sim
Operação de exclusão concluída com sucesso.
return 200 only when it does not change the resource | Yes | Yes | No | Yes | Yes |
Normal execution. The request was successful. | 201 Created. |
A operação resulta na criação de um novo recurso.
Sim
Não
Não
Não
Não
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 |
Não
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 |
Sim
Yes | |
Missing/invalid authentication header or invalid token . | 401 Unauthorized. |
A operação foi recusada devido a um problema de autenticação.
Sim
Sim
Sim
Sim
Sim
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 |
Sim
Yes | |
The request was well-formed but could not be processed due to the specific business logic of the request. | 422 Unprocessable Entity. |
Se aplicável ao endpoint, espera-se que esse erro resulte em um payload de erro.
Sim
Sim
Não
Sim
Sim
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 |