Common HTTP Errors and Messages

Common error codes produced by Oracle Hospitality APIs are listed in the following table.

For a complete list of OPERA Cloud REST API error codes, refer to the Web Service Error Codes topic.

Table 8-3 Common HTTP Error Messages

Error Status	Error Response Body	How to Resolve
400	Response body details which fields are at fault.	Change the fields mentioned in the error response, such that they align with the specifications; referencing the swagger spec will help here.  In some cases the values are determined by a (hotel specific) configured List of Values (LOV), so ensure you supply a value that is in the LOV for that hotel; the List Of Values Oracle Hospitality APIs will help here.
400	This API is not supported for the current database version.	Contact Oracle Customer Support at the Customer Support Portal stating the gateway being called and the error message received.
401	No response body	Ensure your oAuth token is valid and latest. Also, ensure your Application Key is valid. Check it by Viewing the Application Key
402	"invalid_grant", "[Wrong Password]"	Check the password of the integration user. See Changing Your Integration User Password for more information.
403	Unauthorized to access the resource	This could be caused by the integration user missing the WSACCESS role. Ensure the environment owner has approved the integration user. This could also occur if you are sending the wrong hotelId.  Ensure the hotel ID being sent in the x-hotelid header matches a hotel in the environment being called. In recently migrated environments secured by Client Credentials authentication (OPERA Cloud Identity Management), ensure you are using the reissued clientId and clientSecret, not the pre-migration clientId and clientSecret.
403	No response body	Ensure your oAuth token is valid and up to date. Re-request it by using Authenticating to Oracle Hospitality Property APIs. Also ensure your integration user in OPERA Cloud Services has access to the property (hotel) you supplied in the "x-hotelid" header.
403	No Subscribed Plan or API found	This occurs when accessing an API to which you do not have access. If this is an early adopter (v0) API and you think you already have access to the Early Adopter API Program, check that the application specified in the x-app-key header has access to the Early Adopter APIs by following this process: In the Developer Portal, click the Applications tab. Choose the application whose key matches the x-app-key being sent (double check against the end of the application key that appears in the list of applications). Click View details Click the Subscriptions tab and verify it shows all of the following: Early Adopter Hospitality APIs OAuth If you have not yet called the v0 APIs but would like to, contact us as explained in the Early Adopter API Program. If this is a Distribution API, you must register in the Developer Portal to use the API.
403	User is not authorized to access data for resort	Check that your integration user has the WSACCESS role: Find the email you received when the hotel approved your integration user. This includes a URL for the Shared Security Domain identity server. Go to this URL. Log in using your integration username and password. If the login fails, click the "Can't Sign In?" link to reset your password. Verify the hotelId supplied in the "x-hotelid" header matches the one provided by the hotel. See Obtaining Details from the Hotel for more information.
404	No response body	If you are calling an Asynchronous API: Once you have sent the final GET call to obtain the results of the async processing, the data is no longer available on the same summaryId, so you will receive a 404 error. To retrieve the data again, you must restart the request sequence at step one.
404	OPICS-NOT_FOUND	Contact the environment owner to verify that Oracle Payment Interface Cloud Service has been set up by checking for product ID 14308 and ensuring that Token Exchange Service is selected. Customers can contact Oracle Consulting or a reseller to configure Oracle Payment Interface Cloud as needed.
405	No response body	Ensure the HTTP verb you are using is supported by the Oracle Hospitality APIs by checking the Oracle Hospitality APIs documentation.
406	No response body	Set your "accept" header to "application/json" as the Oracle Hospitality APIs will produce only "application/json".
413	No response body	Ensure your request matches the documented request body schema.  If your scenario requires "bulk" fetch or update then consider the jobbed Oracle Hospitality APIs.
414	No response body	Consider whether you need to specify all the query parameters being specified; there may be more efficient resources or ways to structure your query.
415	Unsupported Media Type	Ensure your request payload has a content-type of "application/json".
500	Response body details the error.	Try your request again in a few moments or contact Oracle Customer Support at the Customer Support Portal.
502	No response body	Try your request again in a few moments or contact Oracle Customer Support at the Customer Support Portal.
503	No response body	Try your request again in a few moments or contact Oracle Customer Support at the Customer Support Portal.