V-Spark Online Help

Possible Error Codes from the /request API

The /request API returns HTTP error codes when called with incorrect or invalid parameters:

400

The /request API usually returns a 400 in cases when the authentication token that is required to access V‑Spark is missing or invalid. The error text differs based on the cause of the error, and helps identify the cause of the problem:

Auth token doesn't match

The authorization token that was used in your call to the /request API is not correct. Locating your authorization token is shown in V‑Spark API Permission Requirements.

Request not finished

The results that you requested are not yet available. Always check the status of the audio processing for a "done" response before requesting the JSON transcript, as shown in Examples of calling the /request API.

404

The/request API returns a 404 in response to multiple errors. The error text differs based on the cause of the error, and helps identify the cause of the problem:

Company not found

V‑Spark can look up the name of the company that you are using based on the value that you passed for the ORG_SHORT parameter. This error means that the value that you specified for this parameter was incorrect.

No file types were specified

The default JSON output format was disabled in your call to the /request API, but you did not enable another format (mp3 or text)

Organization organization-name not found

The organization whose short name was passed as a parameter does not exist or cannot be accessed

RequestFile not found

This message indicates a problem communicating with the database that is used by V‑Spark. Retrying the operation should succeed. If you continue to see this message, contact Voci product support ().

RequestId not found

The request ID that was passed as a parameter does not exist. Check for typographical errors if testing the /request API call from the command line, or check your application code to ensure that you are storing and using a valid request ID.