Skip to main content
Veo-3.1 legacy route incident noticeThe veo-3.1 series legacy route began experiencing failures on May 14, 2026 and is temporarily unavailable. When troubleshooting errors, check this route incident first instead of assuming the problem is the API key, balance, or request body.

Authentication Issues

Invalid API Key

Error Message:
Possible Causes:
  • Incorrect API Key format
  • API Key expired or deleted
  • Incorrect Authorization header format
Solutions:
  1. Check if API Key format starts with sk-
  2. Verify Authorization header format: Bearer sk-YOUR_API_KEY
  3. Regenerate API Key in Console
Correct Example:
Error Message:
Solutions:
  1. Log in to Console to check balance
  2. Account Credit account balance
  3. Veo-3.1 charges per request: $0.15-$0.25/request
Fee Information:
  • veo-3.1-fast*: $0.15/request
  • veo-3.1 (others): $0.25/request
  • Using n=2 generates 2 videos, charged for 2 requests

Request Parameter Issues

Model Name Error

Error Message:
Common Incorrect Usage:
Correct Usage:
All Available Models:
  • veo-3.1
  • veo-3.1-fast
  • veo-3.1-fl
  • veo-3.1-fast-fl
  • veo-3.1-landscape
  • veo-3.1-landscape-fast
  • veo-3.1-landscape-fl
  • veo-3.1-landscape-fast-fl
Error Message:
Incorrect Examples:
Correct Example:
Error Message:
Possible Causes:
  • Invalid or expired image URL
  • Image requires authentication
  • Slow image server response or timeout
  • Network connection issues
Solutions:
  1. Use publicly accessible image URLs
  2. Use Base64 encoded images
  3. Ensure image URLs support HTTPS
Using Base64 Solution:
Error Message:
Supported Formats:
  • ✅ JPEG (.jpg, .jpeg)
  • ✅ PNG (.png)
  • ✅ WebP (.webp)
  • ❌ GIF (animated not supported)
  • ❌ BMP
  • ❌ TIFF
Solution: Use PIL/Pillow to convert image format:
Error Message:
Limitations:
  • Maximum file size: 10MB
  • Recommended resolution: 1024x1024 or higher
  • Maximum images: 2
Solution: Compress image:
Error Message:
Reason: Only models with fl suffix support image inputModels Supporting Images:
  • veo-3.1-fl
  • veo-3.1-fast-fl
  • veo-3.1-landscape-fl
  • veo-3.1-landscape-fast-fl
Models Not Supporting Images:
  • veo-3.1
  • veo-3.1-fast
  • veo-3.1-landscape
  • veo-3.1-landscape-fast
Solution:

Connection and Timeout Issues

Connection Timeout

Error Message:
Reasons:
  • Unstable network connection
  • High server load
  • Default timeout too short
Solution: Increase timeout:
Node.js:
Error Message:
Reasons:
  • Stream interrupted due to unstable network
  • Server-side processing exception
Solution: Implement retry mechanism:

Content Generation Issues

Unsatisfactory Results

Possible Causes:
  • Prompt description insufficient
  • Used fast model but expected high quality
  • Low-quality reference images
Solutions:
  1. Optimize prompt:
  1. Choose appropriate model:
  1. Use high-quality reference images:
  • Resolution ≥ 1024x1024
  • Clear, not blurry
  • Good lighting
Possible Causes:
  • Prompt contains contradictory information
  • Description too complex or abstract
  • Expectations exceed model capabilities
Solutions:
  1. Simplify and clarify requirements:
  1. Avoid contradictions:
  1. Step-by-step description:
  • Subject → Action → Environment → Style
Possible Causes:
  • Two images too different
  • Inconsistent lighting, angle, color tone
  • Prompt doesn’t guide transition method
Solutions:
  1. Choose similar images:
  • Same scene, different angles
  • Same subject, different poses
  • Unified lighting and color tone
  1. Specify transition method:
  1. Use intermediate frames: If two images differ greatly, consider step-by-step:
  • Image A → Image B (intermediate frame)
  • Image B → Image C (final frame)

Python SDK Issues

Node.js SDK Issues

Possible Causes:
  • Used n > 1 parameter to generate multiple results
  • Frequent retries of failed requests
  • Mistakenly used standard model ($0.25) instead of fast model ($0.15)
Solutions:
  1. Check n parameter:
  1. Use fast model for testing:
  1. View detailed billing in console: View Call Logs
Answer: NoBilling follows console order status and the returned generation result. For these situations, check the order before retrying:
  • API errors (4xx, 5xx)
  • Parameter validation failures
  • Insufficient balance
  • Network timeouts
  • Generation failures
How to Confirm: Log in to Call Logs to check:
  • ✅ Successful requests: Show charges
  • ❌ Failed requests: No charge record

Get Help

Technical Support

Email technical support teamhi@laozhang.ai

Telegram Community

Join official Telegram groupReal-time communication and Q&A

Call Logs

View detailed API call recordsDiagnose issues and track costs

Console

Manage account and view balanceAccount Credit and configure API Keys

More Resources

Quick Start

Get started with Veo-3.1 from scratch

Code Examples

Complete example code in various languages

Best Practices

Improve video generation quality