Status and error codes

This page lists the response status codes for the Cloud Transcoding REST API, along with their descriptions and recommended actions.

Response status codesCopy Anchor Link

When you call the Cloud Transcoding REST API, you receive an HTTP response status code:

• If the HTTP status code is 200, the request is successful.
• If Destroy returns 206, the server hasn't finished processing the request. Call Query to confirm the task status.
• Any other status code means the request failed.

The following examples show responses to failed requests:

// 400 Bad Request: invalid parameter
{
  "message": "#/transcoder/outputs is invalid after minItems schema validate"
}

// 401 Unauthorized: authentication failure
{
  "message": "Invalid authentication credentials"
}

// 404 Not Found: task not found
{
  "message": "The task is not found"
}

When using Cloud Transcoding, you may receive status codes that indicate the service status. Refer to the following table to understand their meanings and take appropriate action.

When using the Cloud Transcoding response status code for troubleshooting, keep the following in mind:

• If the request fails, do not perform logical processing based on the message field in the response body. Rely primarily on the status code for troubleshooting.
• If the troubleshooting methods in the table do not resolve the issue, contact technical support with the values of the X-Request-ID and X-Resource-ID fields in the response header.
• If you receive a 404 status code after a Create request has returned successfully and you have not called Delete, or if the transcoder remains idle beyond the idleTimeout value in the request, use a backoff algorithm. Retry at increasing intervals of 5, 10, and 15 seconds to call Query for confirmation.
• A 5XX response status code usually indicates an issue in the server response process. Use a backoff strategy for query requests, retrying at increasing intervals of 5, 10, and 15 seconds, or contact technical support.