Status Codes
HTTP Response Header
When you call any of the Oracle Application Performance Monitoring Cloud Service (APMCS) REST API resource operations, the Response header returns one of the standard HTTP status codes defined in the following tables. Use the cURL -i command-line parameter to include the HTTP header in the output, even if no JSON data is returned from the cURL command you are executing.
HTTP/1.1 201 Created
Date: Tue, 23 Feb 2016 20:33:39 GMT
X-Frame-Options: SAMEORIGIN
Content-Length: 0
Content-Type: application/json
X-ORACLE-DMS-ECID: 005B7NTyOwSDGfQ_I_P5if0006Jl0000K_
Set-Cookie: EMCS_JSESSIONID=FkYP1lnLltWifdF5MVoD_ZKYA9MX8TDDWIU2E9E4MgGAX-ReDWrP!-1052259951; expires=Tue, 23-Feb-2016 20:33:49 GMT; path=/apmcs/data; secure; HttpOnly
Set-Cookie: _WL_AUTHCOOKIE_EMCS_JSESSIONID=DnwsiKqBHzdHJJdiZYSJ; path=/apmcs/data; secure; HttpOnly
Cache-Control: no-cache,no-store
Content-Language: en
HTTP Status Codes for GET Methods for All Operations
Code | Status | Description |
---|---|---|
200 | OK | Request completed successfully. Success may still result in null object (if result was a single object), or empty list (if result was a list). |
204 | No Content | Request includes a named or numbered resource that does not exist. For example, an unknown page ID /pages/{id} or server request ID /requests/{id} |
400 | Bad Request | Request contains an invalid or missing parameter. |
401 | Unauthorized | Request not authorized. The credentials included with this request are missing or invalid. |
403 | Request Forbidden | The server is denying access to the requested resource. For example, the requested resource requires special Administrator privileges. |
404 | Not Found | Resource URI is not a valid APMCS resource. For example, you used /pagess instead of /pages. |
500 | Internal Server Error | Server encountered unexpected condition that prevented it from fulfilling request. May include errors like being unable to obtain a tenant ID. |
503 | Service Unavailable | Server unable to handle the request due to temporary overloading or server maintenance. APMCS REST API web application may not currently be running. |
HTTP Status Codes for all Application Operations
This sections lists the status codes returned from Application operations. These operations are described in detail in the Application Definitions overview.
If no data response is returned from a cURL operation (like Create application or Delete application), then use the -i command-line parameter to include the HTTP header in the output, in order to diagnose any failures.
Method | Code | Status | Description |
---|---|---|---|
POST | 201 | Created | Application created. |
- | 409 | Conflict | Application name already exists. |
- | 404 | Not Found | Application creation failed. |
GET | 200 | OK | One or more applications retrieved. |
- | 204 | No Content | Named application not found. |
DELETE | 204 | No Content | Application deleted. |
- | 404 | Not Found | Named application not found to delete. |