This page provides an overview of how to troubleshoot your API requests.

Error messages

See the Response Status Codes section of this Headers and Responses page.

CORS Errors

Here’s our list of things to try:

  1. CORS errors are often caused by invalid requests – usually in the headers.
  2. Check the header response, in particular the MG-message field, which contains detailed information on any errors that need resolving
  3. Localhost Server related – sometimes the set up of localhost servers can cause the issue. Check out these resources:
    1. The ultimate guide to enabling Cross-Origin Resource Sharing (CORS) – LogRocket Blog
    2. Avoiding CORS Errors on Localhost (in 2020) | by Andy Potts

If you experience the errors, and identify solutions not listed here, please let us know by emailing, so that we can make them available to others.

Incorrect Case Used

The API method names are case sensitive.  If you see this message, or similar, then check that you have used the same cases as in the documentation.
“message”: “Authorization header requires ‘Credential’ parameter. Authorization header requires ‘Signature’ parameter. Authorization header requires ‘SignedHeaders’ parameter.
For example, you will see this error message if you use GET “CinemaDetails”.  But it will work fine if you use “cinemaDetails”.

HTTP 429

You ran out of quota