HTTP status codes

Article summary

Did you find this summary helpful?

Thank you for your feedback

Review the following table to learn more about HTTP status codes that the IXM Platform API returns:

HTTP status code	Name	Description
200	OK	Your request succeeded.
201	Created	Your request succeeded; the resource was created.
204	No content	Your request succeeded; sending content to the client isn’t required.
400	Bad request	The server can’t process the request.
401	Unauthorized	The client doesn’t have the required authentication credentials for the target resource.
403	Access denied	The client doesn’t have the required access rights.
404	Not found	The server can’t find the requested resource.
409	Conflict	There’s a conflict between the request and the current state of the target resource.
500	Unexpected error	The server has encountered an unexpected error that stops it from fulfilling the request.

Troubleshooting

If you receive an error response, the following steps can help you identify and solve the issue:

Ensure that the syntax and content of your request is correct.
Check whether the requested address (URL) is correct.
Ensure that you have sufficient user permissions in the IXM Platform.
Check whether your parameters are correct. For example, double-check the location ID, API key, or token that you specified in your request.
Check the state of the resource in your request. For example, the spot you want to delete is in use or the player whose InitBox you want to start is already initialized.
Check whether the resource in your request has been removed or renamed. For example, the spot file you want to download doesn’t exist anymore.
Clear the browser cache and cookies.

In this article