Skip to main content
While interacting with the Vizlook API, you might encounter various HTTP status codes. These errors pinpoint issues with your request, enabling quick problem diagnosis. Below, you’ll find a resource detailing common HTTP errors and their resolutions.
Feel free to contact us at [email protected] if you have any problems.

​
API Errors

HTTP Status CodeOverview
400 - Bad RequestCause: This error occurs when the request parameters are incorrect or invalid.
Solution:
  • Check that all required parameters are included in the request.
  • Verify that the values provided match the expected format.
401 - UnauthorizedCause: This error occurs when the API key is missing or incorrect.
Solution:
  • Ensure that you have included a valid API key in your request.
  • Ensure proper authentication headers.
429 - Too Many RequestsCause: Rate limit exceeded.
Solution:
  • Check the Rate Limits page for current limits.
  • Implement rate limiting or exponential backoff in your application.
432 - Pay-As-You-Go Limit ExceededCause: Your request exceeds your current pay-as-you-go usage limit.
Solution: Increase your limit via the Vizlook dashboard.
500 - Internal Server ErrorCause: This error indicates an issue on Vizlook’s servers.
Solution: Retry the request after a few minutes and contact [email protected] if the issue persists.

​
Error Response Structure

All error responses include a error message: 
{
  "error": "Unauthorized: API key is missing."
}

​
Crawl Error Type for /videos

For the /videos endpoint, in addition to using HTTP status codes to indicate errors, we also use a status field to display specific error information for each video. This design facilitates more precise error management when retrieving multiple URLs. 
{
  "results": [
    {
      "data": {...},
      "status": {
        "url": "https://www.youtube.com/watch?v=xxx",
        "status": "Success"
      }
    },
    {
      "status": {
        "url": "https://www.youtube.com/watch?v=xxx",
        "status": "Fail",
        "error": {
          "type": "CRAWL_NOT_FOUND"
        }
      }
    }
  ]
}
Error TypeOverview
FAILED_TO_PARSE_URLThe URL is not supported, or the URL is incorrect. Check if the URL is supported by Vizlook and if the URL format is correct.
CACHE_NOT_FOUNDThis video does not exist in our database. If you need real-time crawling, please set the crawlMode parameter to Fallback or Always.
CRAWL_SOURCE_FAILFailed to retrieve video content from the URL. Check if the video content is existern, or retry the request after a few minutes.
CRAWL_NOT_FOUNDThe video content at the given URL does not exist. Check if the video content exists.
CRAWL_VIDEO_DURATION_EXCEEDS_LIMITThe video length exceeded the maximum length that the platform can crawl.
CRAWL_TIMEOUTRequest timed out while fetching content. Retry the request. The current timeout is 3 minutes.
CRAWL_SERVER_ERROROther crawling errors. Retry the request and contact [email protected] if the issue persists.

​
Best Practices to Avoid Errors

  • Always validate request parameters before sending.
  • Monitor your API usage to avoid exceeding limits.
  • Implement error handling and retries in your application.