curl-X POST 'https://pollo.ai/api/platform/v1/generation/google/veo-3-1-fast/video'\-H'Content-Type: application/json'\-H'x-api-key: YOUR_API_KEY'\-d'{ "input": { "prompt": "A cinematic shot of a golden retriever running through a field of sunflowers at sunset, warm rim light, shallow depth of field", "aspectRatio": "16:9", "duration": 4, "resolution": "720p", "generateAudio": true }}'
Optionally include webhookUrl to receive a callback when the task succeeds or fails.
Optional request field
{"input":{"prompt":"A cinematic shot of a golden retriever running through a field of sunflowers at sunset, warm rim light, shallow depth of field","aspectRatio":"16:9","duration":4,"resolution":"720p","generateAudio":true},"webhookUrl":"https://example.com/webhooks/pollo"}
Schema
Input fields for the selected endpoint and mode.
Field
Type
Required
Description
prompt
string
Yes
Text prompt describing the content to generate.
aspectRatio
string
No
Output aspect ratio, as width:height (e.g. 16:9).
duration
number
No
The duration of the generated video, in seconds.
resolution
string
No
Output resolution of the generated media (e.g. 720p, 1080p, 2K, 4K). Values are case-insensitive.
seed
integer
No
Random seed for reproducible generation.
generateAudio
boolean
No
Generate natural-sounding, fitting audio for the output video.
Veo 3.1 Fast is the speed-oriented variant of Google's Veo 3.1 video model, suited for short text-to-video and image-guided clips where turnaround matters. It keeps the 3.1 family focus on prompt adherence, frame guidance, and practical audio-video generation.
Running Veo 3.1 Fast on Pollo API gives developers a direct route for adding Google video generation to apps, creative tooling, content pipelines, and automated testing workflows without managing separate provider integrations.
Key Features of Veo 3.1 Fast API
Faster Veo 3.1 Iteration
Veo 3.1 Fast prioritizes quicker generation for workflows that need multiple drafts, prompt variants, or generated clips inside user-facing product loops.
Text and Image Guidance
The model supports prompt-first generation and image-guided workflows, making it useful for turning written scene descriptions or existing visual assets into motion.
First and Last Frame Control
Frame-guided generation helps developers define the beginning and ending visual state, then generate the transition between those points.
Reference-Led Visual Direction
Reference images can guide subjects, settings, objects, or style, helping generated clips stay closer to a target visual brief across repeated attempts.
Short-Form Output Design
Veo 3.1 Fast works well for compact video units, including previews, tests, templates, and short social or in-app clips.
Optional Audio-Aware Generation
Where enabled, the model can generate video with sound cues, dialogue direction, or ambient audio described in the prompt.
Use Cases of Veo 3.1 Fast API
Creative Variant Testing: Generate multiple prompt, framing, or motion variants before selecting a final direction.
App-Generated Social Clips: Add short video creation to creator tools, campaign builders, or social scheduling products.
Product Motion From Stills: Turn product, packaging, or interface images into short clips for storefronts and demos.
Storyboard Transition Tests: Use first and last frames to prototype transitions before committing to manual production.
Localized Content Pipelines: Generate market-specific video drafts from structured prompts and reusable visual inputs.
Interactive Template Systems: Let users choose a template, upload an image, and receive a generated clip through your app.
Internal Concept Previews: Produce quick visual tests for product, training, education, or editorial teams.
How to Use Veo 3.1 Fast API
Get an API Key: Create a Pollo API key and send it with requests using the x-api-key header.
Choose the Model: Use the Veo 3.1 Fast route, such as POST /generation/google/veo3-1-fast.
Add Your Inputs: Provide a prompt, optionally add image or imageTail, and set practical options such as length, aspectRatio, resolution, seed, and generateAudio.
Generate and Retrieve: Submit the request, store the returned taskId, and retrieve the completed video through task status polling or a configured webhookUrl.
Prompting Best Practices for Veo 3.1 Fast API
Write prompts as production instructions rather than loose mood boards. Define the subject, starting state, motion, camera behavior, visual constraints, and audio intent if sound matters.
A Simple Prompt Formula
subject + starting visual state + action over time + camera behavior + environment details + audio cue + output intent
What You Should Notice
Keep Motion Bounded: Short clips work better when the action has one clear motion path instead of several competing events.
Use Concrete Visual Anchors: Name objects, placement, colors, and scene state so image-guided outputs have fewer open variables.
Define Frame Intent: For frame-guided generation, describe how the first frame should change into the last frame.
Limit Audio Complexity: Use concise dialogue, ambience, or sound-effect notes rather than a dense sound design script.
Match Format to Use: Mention whether the clip is for a vertical feed, product module, onboarding screen, or preview tool.
Example Prompts
App Onboarding Preview
"A clean mobile budgeting app screen floats above a desk, then expands into three animated panels showing spending categories, savings progress, and weekly alerts. Slow side camera move, soft office daylight, subtle notification sound."
Museum Guide Kiosk Loop
"A touchscreen museum map highlights one gallery path, then small illustrated markers appear beside three exhibits. The camera stays locked as the interface responds smoothly, with quiet room ambience and a brief confirmation chime."
Meal Kit Assembly Clip
"A top-down kitchen counter shows labeled ingredients moving into place for a meal kit recipe. Hands arrange vegetables, sauce, and noodles in order, ending on a neat plated bowl. Natural kitchen sound, no spoken dialogue."
Industrial Sensor Demo
"A compact factory sensor mounted on a conveyor line lights up as packages pass. The shot begins close on the device, then pulls back to show the monitoring dashboard updating in sync. Low machinery hum."
Veo 3.1 Fast vs Veo 3.1 vs Kling 2.6
Capability
Veo 3.1 Fast
Veo 3.1
Kling 2.6
Render speed
✅ Speed-tuned for fast turnaround
Slower, quality-first
Moderate
Native audio generation
✅
✅
❌ Limited
Start and end frame control
✅
✅
✅
Max resolution
Up to 4K
Up to 4K
Up to 1080P
Clip length
4, 6, or 8 seconds
4, 6, or 8 seconds
Short directed clips
Recommended For
Fast iteration with sound
Highest-fidelity finals
Character motion
Why Choose Veo 3.1 Fast API?
Veo 3.1 Fast is the tier to reach for when you need Veo-grade motion and synced audio quickly, trading a little render time for the speed iteration-heavy work demands.
Start with the Veo 3.1 Fast endpoint to ship quick, audio-ready clips, then switch to the full Veo 3.1 or another model without touching your integration.
Veo 3.1 Fast API FAQs
What is Veo 3.1 Fast?
Veo 3.1 Fast is Google's speed-optimized version of Veo 3.1, generating short videos with synced audio, start and end frame control, and output up to 4K.
Does Veo 3.1 Fast API support text and image inputs?
Yes. You can generate from a text prompt or from an image, and add an optional end frame to guide how the shot begins and finishes.
Does Veo 3.1 Fast generate audio?
Yes. Fitting audio, including ambient sound and spoken lines, is generated alongside the video by default and stays timed to on-screen action.
What resolutions and lengths are available?
Veo 3.1 Fast supports 720p, 1080p, and 4K output in 16:9 or 9:16, with clip lengths of 4, 6, or 8 seconds per request.
How is it different from the full Veo 3.1?
Fast prioritizes quicker turnaround for iteration and high-volume work, while standard Veo 3.1 leans toward maximum fidelity when render time is less critical.
Why run Veo 3.1 Fast through Pollo API?
Pollo API gives one integration for Veo 3.1 Fast and 300+ other models, with documentation, task tracking, webhooks, and lower-cost generation than comparable providers.
