Return Codes
In addition to returning an HTTP response code, the Oracle Life Sciences IAMS Inbound User Provisioning Service API returns errors in the body of the response with error code and descriptions, as well as messages describing successful requests.
Table 3-7 HTTP Return Codes
HTTP Return Code | Description |
---|---|
200 |
Request processed successfully. |
201 |
Request has been processed and a new resource has been created. |
204 |
The server has fulfilled the request, but does not return a response (in a DELETE request). |
303 |
See Other redirect. (If a user with similar user name or externalId exists in a DISABLED state, the location of the user is sent in the response.) |
401 |
Unauthorized. (User is not authenticated.) |
403 |
Forbidden. (User is not authorized for the operation.) |
404 |
Not found. |
412 |
Precondition failed. (One or more validations failed. Refer to the error response for remediation.) |
415 |
Client media type unsupported. (Only application/JSON is supported for all operations.) |
500 |
Generic server failure. |
501 |
Requested method or operation is not implemented. |
Parent topic: Resources