Task-based generation
Use request ids and task states to manage longer-running video output in your own application UI.
Video Generation API
Video Generation API for text-to-video and image-to-video
Connect video generation models such as Seedance, Kling, Wan, Grok Video, and HappyHorse through Pixapi with API keys, credit tracking, task states, and documentation designed for production product teams.
Text-to-videoImage-to-videoTask-based responses
Video generation request
Submit async video tasks and poll GET /v1/tasks/{id} from your backend.
curl https://api.pixapi.ai/v1/async/videos/generations \
-H "Authorization: Bearer $PIXAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "veo3.1-fast",
"prompt": "A cinematic reveal of a smart speaker",
"seconds": 8,
"resolution": "720p"
}'Direct answer: Pixapi video generation is async-only
Pixapi video generation must be submitted with POST /v1/async/videos/generations; new integrations should not use /v1/videos/generations.
Video requests use Bearer authentication, a video model such as veo3.1-fast, seedance-2, kling-3.0-turbo, wan2.6, grok-video-3, or happyhorse-1.1, plus prompt, seconds, resolution, and optional image for image-to-video workflows.
Pixapi returns a task id immediately; your backend polls GET /v1/tasks/{id} until the task is completed or failed, then reads the final video URL from result.data[0].url.
A video API needs workflow control
Video models are slower and more expensive than image generation, so the API layer needs task tracking, credits, and clear error handling.
Text and image prompts
Build both text-to-video and image-to-video flows while keeping authentication and billing consistent.
Model catalog guidance
Compare video model capabilities, pricing hints, and common use cases before choosing a route.
Credit visibility
Estimate and monitor video generation spend across users, plans, and internal product features.
Production retries
Handle rate limits, transient model failures, and user-facing status updates with consistent error patterns.
One visual AI account
Use the same Pixapi account for images, editing, and video instead of stitching together separate vendors.
Video API workflow map
| Need | Recommended Pixapi route | Why it fits |
|---|---|---|
| Prompt-to-video product clips | Seedance, Kling, Wan, Grok Video, or HappyHorse | Choose based on realism, style, and credit cost. |
| Image-to-video animation | Video route with reference image | Turn generated or uploaded images into short clips. |
| Async user workflows | Task id plus status tracking | Keep the UI responsive while the generation runs. |
| Cost-controlled launches | Credit plans and pricing page | Forecast demand before opening video features to all users. |
Related implementation resources
API documentation
Review endpoints, authentication, request fields, and response formats.
Authentication guide
Create and protect a bearer API key before making production calls.
Model catalog
Compare available image and video models by capability and cost.
Credits and pricing
Check credit packs, billing rules, and current product pricing.
Video Generation API FAQ
How is video generation different from image generation?
Video generation usually runs as a task because outputs take longer and cost more. Your app should store the task id and display progress.
Which video models are available?
Pixapi lists curated video routes such as Seedance, Kling, Wan, Grok Video, and HappyHorse in the model catalog. Availability can change as providers update models.
Can I generate video from an image?
Supported video routes can use a reference image for image-to-video workflows. Check each model page for parameters.
Can I combine Pixapi image and video APIs?
Yes. A common workflow is to generate an image first, then use it as a reference for short video generation.
Launch video generation without a separate model stack
Use Pixapi to test video routes, monitor credit usage, and move from prototype to product with one API key.
Create API key