Error codes

We hope you never get an error using our API. But if you do, this page will help you understand what went wrong.

We use all status codes according to the http protocol specification.

The best status code of all is:

200 - Successful Request

If you do see errors, here are the most common ones:

Error Code	Title	Description
400	Bad Request	The server cannot or will not process the request due to a client error, such as invalid syntax or missing required parameters. Try recreating the call URL with its parameters on the relevant API reference page.
401	Unauthorized	The request requires user authentication, but the user has not provided valid credentials or does not have permission to access the requested resource. Check your X-Token is correct. You can find it on your profile on the main site (note, you must be logged in on the main site).
403	Forbidden	The user is authenticated but cannot access the requested resource. Check what subscription you need for this dataset.
404	Not Found	The requested resource could not be found. This can happen if the URL is incorrect, the resource has been deleted, or the server cannot access the resource. Try finding the datasource in the API reference pages, and recreating your call URL there.
405	Method Not Allowed	The requested method is not allowed for the resource. For example, using a POST request on a resource that only accepts GET requests.
429	Too Many Requests	The user has sent too many requests in a given amount of time. The server indicates that the client should wait before sending more requests.
500	Internal Server Error	The server encountered an unexpected error and could not complete the request. This could be due to a bug in the server code or a problem with the server's configuration.
503	Service Unavailable	The server cannot handle the request due to maintenance, overloading, or other temporary reasons.