OpenManage Enterprise–Tech Release REST API Guide
Response codes
For synchronous operations, the server returns HTTP response codes 200 or 204 depending on the request. For long-running operations, the server returns a status code of 202 along with a HTTP response header (Location), corresponding to the URI of the temporary resource that can be used to monitor the operation. The following table includes a few examples of response codes. For an extensive list of response codes, see List of HTTP status codes.
| Request header | Description |
|---|---|
Success codes |
|
GET |
200 – OK with message body 204 – OK with no message body 206 – OK with partial message body |
POST | 201 – Resource created (operation complete) 202 – Resource accepted (operation pending) |
PUT | 202 – Accepted (operation pending) 204 – Success (operation complete) |
DELETE | 202 – Accepted (operation pending) 204 – Success (operation complete) |
Failure codes | |
Invalid parameter | 400 – Invalid parameter |
Authorization | 401 – Authorization failure |
Permission denied | 403 – Permission denied |
Not found | 404 – Resource not found |
Invalid request method | 405 – Invalid request method |
Internal server error | 500 – Internal server error |
Service unavailable | 503 – Service unavailable |
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\