APIMART Growth evidence. Veo 3.1 facts were checked on 2026-09-02. CTA links are attributed to this exact GitHub guide.

Veo 3.1 API Limits: Resolution, Inputs and Request Boundaries

APIMART serves Veo 3.1 through POST /v1/videos/generations. The current documentation describes an asynchronous submit-and-poll workflow. The boundaries below were checked on September 2, 2026.

Verified boundaries

• Official-channel requests use veo3.1-fast-official or veo3.1-quality-official and return an asynchronous task_id.
• The official-channel endpoint recommends durations of 4, 6 or 8 seconds; default is 8.
• Aspect ratio supports 16:9 and 9:16; default is 16:9.
• Resolution lists 720p, 1080p and 4K; default is 720p.
• Text-to-video and first-frame or first-and-last-frame image-to-video workflows are documented.
• generate_audio, person_generation and enhance_prompt are separate request controls.

Minimal integration rule

Send the documented model ID, required prompt and only compatible optional inputs. Persist the returned task_id, implement bounded polling and backoff, and keep 400, 401, 402, 429 and 5xx responses out of completed-output metrics.

FAQ

Which endpoint serves Veo 3.1?

Use POST /v1/videos/generations with the documented model ID and Bearer authentication.

Is processing synchronous?

No. A successful submission returns a task ID that must be polled for completion.

What is the first production safeguard?

Validate model ID, quantity or duration, resolution and input combinations before submission.

Can documented limits change?

Yes. Treat the live endpoint documentation as the source of truth and version your request profile.

Should a submitted task be counted as completed output?

No. Count success only after the task endpoint reports a completed result.

Try Veo 3.1 on APIMART

Open the attributed model page or review current APIMART pricing.

Sources and disclosure

Technical source: APIMART endpoint documentation, checked September 2, 2026. APIMART operates the gateway; limits may change.

APIMART links for this guide

• Open Veo 3.1 on APIMART
• Review current APIMART pricing

Machine-readable schema source

The eventual APIMART CMS page should emit these JSON-LD objects.

[
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "headline": "Veo 3.1 API Limits: Resolution, Inputs and Request Boundaries",
    "mainEntityOfPage": "https://apimart.ai/blog/veo-3-1-api-limits-resolution-inputs",
    "dateModified": "2026-09-02",
    "author": {
      "@type": "Organization",
      "name": "APIMART"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Which endpoint serves Veo 3.1?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Use `POST /v1/videos/generations` with the documented model ID and Bearer authentication."
        }
      },
      {
        "@type": "Question",
        "name": "Is processing synchronous?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "No. A successful submission returns a task ID that must be polled for completion."
        }
      },
      {
        "@type": "Question",
        "name": "What is the first production safeguard?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Validate model ID, quantity or duration, resolution and input combinations before submission."
        }
      },
      {
        "@type": "Question",
        "name": "Can documented limits change?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Treat the live endpoint documentation as the source of truth and version your request profile."
        }
      },
      {
        "@type": "Question",
        "name": "Should a submitted task be counted as completed output?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "No. Count success only after the task endpoint reports a completed result."
        }
      }
    ]
  }
]