Common Errors

These are some of the common errors you may see when debugging and how to troubleshoot them.


This is an authentication error.

Make sure you are providing a valid API token in the authentication header in your request.


This is a read error on the URL provided as input.

If you are using a pre-signed URL or protected server it may be that the tokens or keys are invalid for accessing the file.

    "path": "/media/enhance",
    "status": "Failed",
    "progress": 5,
    "api_version": "v1.1.2",
    "error": {
        "type": "/problems/input-file-access",
        "title": "Input file access problem",
        "detail": "Input file does not exist or access is denied."

If you are using Media Input and Output solutions such as Temporary Cloud Storage or AWS S3 you should verify that you are following valid file naming conventions when storing your media.


This is a processing error if we are able to read the file but it is not a supported format or is corrupted in some way.

Potential Causes:

  • Audio must be a minimum of 1 second in order to receive output
  • Check the Supported Media Formats to make sure it is the type of media we support
  • Try a different media file, we have a few samples that are known to work, for example, airplane.original.mp4


This is a read or write error if the input or output parameters given as an AWS S3 location reference an invalid bucket.


This is a write error if the URL provided as output is inaccessible. The endpoint must accept a PUT request along with a concluding HEAD or GET request that validates the full file has been stored.


This is a general access error to read or write a given input and output parameters.


This problem can occur if we are unable to read or write media in a reasonably expected amount of time. If this problem occurs frequently please raise a support ticket so that we can work with you on a solution:


This problem can occur if you exceed usage thresholds for the Media APIs. If you are making an unexpectedly high volume of API calls this problem could be triggered. If you believe this is an error please raise a support ticket.


If you are on a free-tier this may indicate you have consumed your free processing minutes. Check that your billing details on file are correct.

    "type": "/problems/usage-limit",
    "title": "Usage limit reached",
    "status": 403,
    "instance": "/media/analyze",
    "detail": "Request would exceed free usage limits"

If you anticipate this is an error, please use the Contact form and raise a question so that we can help upgrade your account.