JPG to MP4 API - Convert JPG to MP4 API: Pricing, Documentation

Authentication

Every request is authenticated with your Pixazo API key in the Ocp-Apim-Subscription-Key header — the same key across every Pixazo endpoint.

JPG to MP4 generate request

Plenty of systems will not take a still. Ad slots, story formats, broadcast timelines and signage players all want a video file, and the usual answer is to open an editor and export a five-second hold by hand. The JPG to MP4 API does that one step over HTTP: it decodes your JPG, holds it for the duration you choose, and encodes a silent H.264/yuv420p MP4 with even dimensions and correct headers, downscaled to fit within 1920x1920 if the source is larger and never upscaled if it is smaller. Nothing is added and nothing moves — no motion, no prompt, no model. It is a container change, priced like one at a flat $0.002 per clip.

Endpoint: POST https://gateway.pixazo.ai/media-tools/v1/image-to-video

Request Code

curl -X POST 'https://gateway.pixazo.ai/media-tools/v1/image-to-video' \
  -H 'Ocp-Apim-Subscription-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"image_url":"https://example.com/input.jpg","duration_seconds":5}'

Output

{
  "request_id": "req_9f3c1a7b2e",
  "status": "QUEUED",
  "polling_url": "https://gateway.pixazo.ai/v2/requests/status/req_9f3c1a7b2e"
}

Webhook (Optional)

Instead of polling, include a webhook_url in the request body and Pixazo will POST the completed job payload to that URL when the conversion finishes. The webhook body is identical to the completed-status response shown under Retrieving Results.

Request Parameters

Example Request

curl -X POST 'https://gateway.pixazo.ai/media-tools/v1/image-to-video' \
  -H 'Ocp-Apim-Subscription-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"image_url":"https://example.com/input.jpg","duration_seconds":5}'

import requests

resp = requests.post(
    "https://gateway.pixazo.ai/media-tools/v1/image-to-video",
    headers={
        "Ocp-Apim-Subscription-Key": "YOUR_API_KEY",
        "Content-Type": "application/json",
    },
    json={
  "image_url": "https://example.com/input.jpg",
  "duration_seconds": 5
},
)
print(resp.json())

const res = await fetch("https://gateway.pixazo.ai/media-tools/v1/image-to-video", {
  method: "POST",
  headers: {
    "Ocp-Apim-Subscription-Key": "YOUR_API_KEY",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({"image_url":"https://example.com/input.jpg","duration_seconds":5}),
});
console.log(await res.json());

Response

Every request returns a request_id immediately with a QUEUED status. Use the polling_url (or a webhook) to retrieve the finished file.

{
  "request_id": "req_9f3c1a7b2e",
  "status": "QUEUED",
  "polling_url": "https://gateway.pixazo.ai/v2/requests/status/req_9f3c1a7b2e"
}

Request Headers

Response Handling

The submit call returns one of the HTTP status codes below. A 202 means the job was accepted — everything else is an error you should handle.

Error Responses

Errors return a JSON body with a machine-readable code and a human-readable message.

{
  "request_id": "req_9f3c1a7b2e",
  "status": "FAILED",
  "error": {
    "code": "INSUFFICIENT_BALANCE",
    "message": "Your account balance is too low to process this request."
  }
}

Retrieving Results

Poll the status endpoint until the job reaches COMPLETED (or FAILED).

curl 'https://gateway.pixazo.ai/v2/requests/status/req_9f3c1a7b2e' \
  -H 'Ocp-Apim-Subscription-Key: YOUR_API_KEY'

Response (Completed)

{
  "request_id": "req_9f3c1a7b2e",
  "status": "COMPLETED",
  "model_id": "image-to-video",
  "output": {
    "media_url": "https://api-assets.pixazo.ai/out/result.mp4",
    "media_type": "MP4"
  },
  "error": null,
  "created_at": "2026-01-01T00:00:00Z",
  "completed_at": "2026-01-01T00:00:04Z"
}

Response Fields

Status Values