Skip to main content
It is an API error returned when the API fails to serve the request due to invalid request parameters.

​
Reasons and how to fix

​
Invalid request parameters

The most common reason for the invalid-request error is that one or more of the request parameters are invalid or missing. To fix this, ensure that all required parameters are included in the request and that they are correctly formatted and valid.

​
Missing required parameters

If required parameters are missing from the request, this will trigger the invalid-request error. To fix this, ensure that all mandatory parameters are provided in the request. Refer to the API documentation for a list of required parameters.

​
Incorrect data types

Providing parameters with incorrect data types (e.g., a string instead of an integer) can lead to this error. To fix this, verify that the data types of all parameters match the expected types as specified in the API documentation.

​
Parameter value constraints

Some parameters may have constraints on their values (e.g., minimum or maximum length, specific formats). Violating these constraints will result in this error. To fix this, check the constraints for each parameter in the API documentation and ensure that the provided values comply with these constraints.

​
Syntax errors

Syntax errors in the request, such as missing commas or brackets in JSON, can make the request invalid. To fix this, carefully review the syntax of your request and correct any errors. Using a JSON validator can help identify syntax issues.

​
Expired pre-signed URLs or tokens

When url is a file URL with a time-limited access token (for example a pre-signed URL from AWS S3, Google Cloud Storage, or Azure Blob Storage) whose expiry time has already passed, the request is rejected with invalid-request before any download attempt. To fix this:
  1. Use publicly accessible URLs without expiration when possible
  2. Generate pre-signed URLs immediately before making the API request
  3. Set a longer TTL (Time To Live) on pre-signed URLs - we recommend at least 1 hour
  4. Configure your storage bucket to allow public read access for media files

​
Unsupported media

File URLs over the size or duration limits of the endpoint (see Transcript and Extract), live streams, and URLs from unsupported platforms also return invalid-request.

​
Reach out to support

If you continue to face issues or need further assistance, please reach out to support@supadata.ai, and we will assist you as soon as possible.