Status Codes
When you call any of the GoldenGate Veridata REST operations, the response returns one of the standard HTTP status codes defined in the following table:
| HTTP Status Code | Description |
|---|---|
200 OK
|
The request was completed successfully. A 200 status is returned for a
successful GET or POST method.
|
201 Created
|
The request was fulfilled and resulted in a new resource being created.
A 201 status is returned from a synchronous resource creation or an asynchronous resource creation that completed before the response was returned. |
204 No Content |
The request was fulfilled and there is no content to send in the response payload body. |
207 Multi-Status |
The request was partially successful. The response contains status information for multiple independent operations, where some may have succeeded while others failed. |
400 Bad Request
|
The request could not be processed because it contains missing or invalid information (such as a validation error on a parameter or a missing required value). |
401 Unauthorized |
The request is not authorized. The authentication credentials included with this request are missing or invalid. |
404 Not Found
|
The request includes a resource URI that does not exist. |
405 Method Not Allowed
|
The HTTP verb specified in the request (DELETE, GET, POST, PUT) is not supported for this request URL. |
409 Conflict |
Represents a conflict arising from POST operations. |
429 Too Many
Requests |
The request could not be processed because too many requests were sent in a given amount of time. The client should retry after some time. |
500 Internal Server Error
|
The server encountered an unexpected condition that prevented it from fulfilling the request. |
502 Bad Gateway |
The server, while acting as a gateway or proxy, received an invalid response from an upstream service. |