> ## Documentation Index
> Fetch the complete documentation index at: https://docs.infery.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Get video generation status

> GET /v1/videos/generations/{jobId} — poll for job status and result.

Poll this endpoint to track an async video job submitted via [POST /v1/videos/generations](/api-reference/videos/generations).

```bash theme={null}
curl https://api.infery.ai/v1/videos/generations/vgen_... \
  -H "Authorization: Bearer $INFERY_API_KEY"
```

Response while running:

```json theme={null}
{"status": "processing", "progress": 42}
```

When done:

```json theme={null}
{
  "status": "completed",
  "result": {
    "url": "https://...",
    "duration_seconds": 4,
    "resolution": "1280x720"
  },
  "credits_used": 180
}
```

### Sample output

<video controls src="https://mintcdn.com/inferyai/5YDpMTITcUUspdCA/samples/video.mp4?fit=max&auto=format&n=5YDpMTITcUUspdCA&q=85&s=e405e2a92f673efe8316d267a8719f72" width="640" data-path="samples/video.mp4" />

*Generated with `veo-3.0-fast-generate-001` (4s, 16:9).*

## Polling guidance

Poll every 5 seconds. Most videos finish in 30–90 s; hard timeout is 1 hour.


## OpenAPI

````yaml openapi.json GET /v1/videos/generations/{jobId}
openapi: 3.0.0
info:
  title: Infery Gateway
  description: >-
    Infery Inference Gateway — OpenAI-compatible API for LLMs, embeddings,
    images, audio, and video
  version: '1.0'
  contact: {}
servers:
  - url: https://api.infery.ai
    description: Production
  - url: http://localhost:3001
    description: Local
security: []
tags: []
paths:
  /v1/videos/generations/{jobId}:
    get:
      tags:
        - Video
      summary: Get video generation status
      operationId: getVideoGenerationStatus
      parameters:
        - name: jobId
          required: true
          in: path
          description: Video generation job ID
          schema:
            type: string
      responses:
        '200':
          description: >-
            Video generation job status. `result` and `credits_used` are present
            when `status === "succeeded"`; `error` when `status === "failed"`.
          content:
            application/json:
              schema:
                type: object
                properties:
                  id:
                    type: string
                    example: vgen_01HYJ8F3K9QT2X5Z7N1V6W3B4R
                  status:
                    type: string
                    enum:
                      - queued
                      - processing
                      - succeeded
                      - failed
                  progress:
                    type: integer
                    example: 100
                    description: Progress percentage (0-100)
                  created:
                    type: integer
                    example: 1713204900
                  model:
                    type: string
                    example: veo-3-1-fast
                  result:
                    type: object
                    description: Present only when status is "succeeded"
                    properties:
                      url:
                        type: string
                        example: /samples/video.mp4
                        description: >-
                          Signed URL to the generated video (auto-mirrored to
                          GCS)
                      duration_seconds:
                        type: number
                        example: 4
                      resolution:
                        type: string
                        example: 1280x720
                    example:
                      url: /samples/video.mp4
                      duration_seconds: 4
                      resolution: 1280x720
                  credits_used:
                    type: integer
                    example: 180
                    description: Credits deducted. Present only on success.
                  error:
                    type: string
                    description: Error message. Present only when status is "failed".
        '401':
          description: Unauthorized — invalid or missing API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponseDto'
        '404':
          description: Job not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponseDto'
      security:
        - ApiKey: []
components:
  schemas:
    ErrorResponseDto:
      type: object
      properties:
        error:
          $ref: '#/components/schemas/ErrorDetailDto'
      required:
        - error
    ErrorDetailDto:
      type: object
      properties:
        message:
          type: string
          example: Model not found
          description: Human-readable error message
        type:
          type: string
          example: invalid_request_error
          description: Error category
          enum:
            - invalid_request_error
            - authentication_error
            - permission_error
            - quota_exceeded
            - rate_limit_error
            - server_error
        code:
          type: object
          example: model_not_found
          nullable: true
          description: Stable machine-readable error code
        param:
          type: object
          example: model
          nullable: true
          description: >-
            Name of the request parameter that triggered the error, if
            applicable
      required:
        - message
        - type
        - code
        - param
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: Authorization
      description: 'API key in format: Bearer inf_***'

````