Status Codes
When you call any of the BRM REST Services Manager operations, the response returns one of the standard HTTP/HTTPS 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 method.
|
201 Created |
The request was fulfilled and resulted in a new resource being created. The
response includes a Location
header which contains the canonical URI for the
newly created resource. A 201
status is returned for a successful
POST method.
|
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. |
403 Forbidden |
The user can't be authenticated. The user does not have authorization to perform this request. |
404 Not Found |
The request includes a resource URI that does not exist. |
405 Method Not Allowed |
The HTTP method specified in the request (DELETE ,
GET , POST ,
PUT ) is not supported for this
request URI.
|
409
Conflict |
The request can't be completed due to a conflict with the current state of the target resource. |
500 Internal Server Error |
The server encountered an unexpected condition that prevented it from fulfilling the request. |