Status Codes

When you call any of the Oracle Messaging Cloud Service REST endpoints, the response returns one of the following HTTP status codes:

Status Code	Description
200 Ok	Successful requests other than creations and deletions.
201 Created	Successful creation of a queue, topic, temporary queue, temporary topic, session, producer, consumer, listener, queue browser, or message.
204 No Content	Successful deletion of a queue, topic, session, producer, or listener.
400 Bad Request	The path info doesn't have the right format, or a parameter or request body value doesn't have the right format, or a required parameter is missing, or values have the right format but are invalid in some way (for example, destination parameter does not exist, content is too big, or client ID is in use).
403 Forbidden	The invoker is not authorized to invoke the operation.
404 Not Found	The object referenced by the path does not exist.
405 Method Not Allowed	The method is not one of those allowed for the path.
409 Conflict	An attempt was made to create an object that already exists.
500 Internal Server Error	The execution of the service failed in some way.

Response bodies for status codes greater than or equal to 400 are either empty or contain an error response in JSON or XML format.

Note:

For more information about the error codes and error messages, see Error Keys, Status Codes and Error Messages in Using Oracle Messaging Cloud Service.