Review the following table to learn more about status codes that the API returns.
HTTP status code | Name | Description |
|---|---|---|
200 | OK | Your request was successful. |
201 | Created | Your request was successful. The resource was created. |
204 | No content | Your request was successful. The response doesn’t requires any content. This occurs frequently, for example, with PUT or DELETE requests. |
400 | Bad request | The server can’t process the request. This is usually due to a client-side error, such as an incorrect URL in the request. |
401 | Unauthorized | The server requires authentication to process the request. In this case, the client usually provided no or incorrect credentials. |
403 | Access denied | The server denies access, because the client doesn’t have the required access rights. |
404 | Not found | The server can’t find the requested resource. This can be due to a broken link, incorrect URL, or because resources were moved or deleted. |
409 | Conflict | There’s a conflict between the request and the current state of the target resource. Multiple users may be attempting to access the target resource at the same time, or the resource version may differ between the client and server. |
500 | Unexpected error | An unexpected error has occurred on the server which prevents the request from being executed. This can happen, for example, if there’s a problem with the server itself. |
Troubleshooting
If you receive an error response, the following steps can help you identify and solve the issue:
Syntax and content: Ensure that the syntax and content of your request are correct.
Correct URL: Check whether the requested address (URL) is correct.
Required permissions: Ensure that you have sufficient user permissions in IXM One.
Correct parameters: Check whether your parameters are correct. For example, double-check the Booking ID in your request.
Resource state: Check the state of the resource in your request. For example, an item you want to delete might be in use, or the resource in your request might have been removed or renamed.
Cache and cookies: Clear the browser cache and cookies.