Veo 3.1 Serverless API

Static images into high-quality videos with synchronized audio.

~110.98s
POST /v2/veo-3.1 · submit + poll
 1# pip install "segmind>=1.1.0"
 2# export SEGMIND_API_KEY="YOUR_API_KEY"
 3from segmind import SegmindClient, InferenceFailed, InferenceTimeout
 4
 5# Async (v2) — recommended for long-running / video models.
 6# run() blocks up to 600s; submit_async + job.wait(timeout=...) sets a longer
 7# deadline and keeps the request_id so you can re-poll later.
 8client = SegmindClient()                      # reads SEGMIND_API_KEY
 9payload = {
10    "prompt": "A woman is giving a keynote presentation at a tech conference, wearing a sleek white blazer with the Veo 3.1 logo subtly embroidered, highlighted by ambient blue stage lighting. She is on a modern conference stage with geometric patterns and LED screens behind her, discussing how Veo 3.1 can integrate reference images to enhance AI-generated video content. The Veo 3.1 logo is also displayed prominently on a large digital screen behind her",
11    "duration": 8,
12    "resolution": "1080p",
13    "aspect_ratio": "16:9",
14    "generate_audio": True,
15    "negative_prompt": "no black and white, no sharp angles",
16}
17job = client.submit_async("veo-3.1", **payload)
18print(job.request_id)                         # available immediately
19try:
20    result = job.wait(timeout=900, interval=2.0)
21    print(result["status"])                  # COMPLETED
22    print(result.get("output"))              # model output (e.g. video URL)
23except InferenceTimeout as e:
24    print("still running:", e.request_id)    # re-poll later with this id
25except InferenceFailed as e:
26    print("failed:", e.detail)
27
28# Fast models (<=600s) can use the one-liner instead:
29# result = segmind.run("veo-3.1", **payload)

API Endpoint

POSThttps://api.segmind.com/v1/veo-3.1

Parameters

promptrequired
string

Describe the video content. Use clear, concise language for best results.

Default: "A woman is giving a keynote presentation at a tech conference, wearing a sleek white blazer with the Veo 3.1 logo subtly embroidered, highlighted by ambient blue stage lighting. She is on a modern conference stage with geometric patterns and LED screens behind her, discussing how Veo 3.1 can integrate reference images to enhance AI-generated video content. The Veo 3.1 logo is also displayed prominently on a large digital screen behind her"
aspect_ratiooptional
string

Choose aspect ratio: 16:9 for landscape, 9:16 for portrait mode.

Default: "16:9"
Allowed values :
"16:9""9:16"
durationoptional
integer

Choose the video length: short is 4s, medium 6s, long 8s.

Default: 8
Allowed values :
468
generate_audiooptional
boolean

Enable audio generation. Recommended for videos requiring sound.

Default: true
imageoptional
string (uri)

Start generation from this image. Ideal for specific starting visuals.

Default: null
last_frameoptional
string (uri)

End video with this image. Useful for specific concluding visuals.

Default: null
negative_promptoptional
string

Exclude elements from video. Useful for refining details.

Default: "no black and white, no sharp angles"
reference_imagesoptional
string[]

Use reference images for consistency. Essential for maintaining subject style.

resolutionoptional
string

Set video quality: 720p for standard, 1080p for high resolution.

Default: "1080p"
Allowed values :
"720p""1080p"
seedoptional
integer

Sets a random seed for consistency. Useful for repeated generations.

Default: null

Response Type

Returns: Video

Asynchronous requests (v2)

Use Async for video, long-running (>~60s), or high-concurrency workloads; Sync is simplest for fast image & LLM calls. Async submits a request and you poll it to completion.

  1. 1
    POST /v2/veo-3.1

    Submitreturns request_id, status_url, response_url

  2. 2
    GET /v2/requests/{id}/status

    Polluntil COMPLETED or FAILED

  3. 3
    GET /v2/requests/{id}

    Resultfinal response body

Status states

QUEUEDAccepted, waiting for a worker
PROCESSINGRunning on a worker
COMPLETEDDone — result body is ready
FAILEDErrored (incl. content/RAI blocks)
  • A FAILED request is served as HTTP 422 — the body still carries the error detail.
  • An unknown or expired request_id returns HTTP 404.
  • Results are retained for 1 hour, then expire.
  • Content / RAI blocks surface as FAILED, not a separate state.
  • Track completion by polling the status endpoint.

Common Error Codes

The API returns standard HTTP status codes. Detailed error messages are provided in the response body.

400

Bad Request

Invalid parameters or request format

401

Unauthorized

Missing or invalid API key

403

Forbidden

Insufficient permissions

404

Not Found

Model or endpoint not found

406

Insufficient Credits

Not enough credits to process request

429

Rate Limited

Too many requests

500

Server Error

Internal server error

502

Bad Gateway

Service temporarily unavailable

504

Timeout

Request timed out