OmniHuman 2.0 API documentation

Integrate OmniHuman 2.0 with your VezAPI key. The operations below share the same authentication and account balance.

Base URL: https://api.vezapi.com
Send Authorization: Bearer YOUR_VEZAPI_KEY. Use a unique Idempotency-Key for each submission; reuse it only when checking the same request.

Omnihuman 2.0

POST/api/v1/jobs/createTask

Model IDs: omnihuman-2-0

Parameter	Type	Description & constraints
`model` required	`string`	The model name used for generation. This field is required. - This endpoint must use the `omnihuman-2-0` model Values: `"omnihuman-2-0"` Default: `"omnihuman-2-0"`
`input` required	`object`	Input parameters for the OmniHuman 2.0 video generation task.
`input.image_urls` required	`array`	Source image URL. Only one image is supported. Pass it as a one-element array. - Formats: jpeg, png, webp, bmp, tiff, gif, heic, heif (`image/jpeg`, `image/png`, `image/webp`, `image/bmp`, `image/tiff`, `image/gif`, `image/heic`, `image/heif`) - Size: less than 30 MB - Aspect ratio (width/height): `[0.4, 2.5]` - Dimension: `[300, 6000]` px
`input.audio_url` required	`string`	Audio URL that drives motion and lip sync. - Duration: `[4, 300]` seconds - Formats: wav, mp3 (`audio/wav`, `audio/x-wav`, `audio/mpeg`) - Size: less than 15 MB
`input.prompt` optional	`string`	Optional text prompt for precise control of the scene, character motion, and camera movement. Supported languages: Chinese, English, Japanese, Korean, Spanish (Mexican), Indonesian. Up to 300 characters. `maxLength: 300`
`input.enable_watermark` optional	`boolean`	Whether to add a watermark to the output video. Default: `true` (enabled). Default: `true`
`callBackUrl` optional	`string`	The URL to receive generation task completion updates. Optional but recommended for production use. - The system POSTs task status and results to this URL when generation completes (success or failure) - On success, `data.resultJson` contains `resultUrls` with the generated MP4 video URL - `data.param` echoes the submitted OmniHuman 2.0 input (`image_urls`, `audio_url`, `prompt`, `enable_watermark`) - Your endpoint should accept POST requests with a JSON payload - Alternatively, poll task status with the Get Task Details endpoint - To verify callbacks, see [Webhook Verification Guide](/common-api/webhook-verification)

Request example

curl -X POST 'https://api.vezapi.com/api/v1/jobs/createTask' \
  -H 'Authorization: Bearer YOUR_VEZAPI_KEY' \
  -H 'Idempotency-Key: your-unique-request-id' \
  -H 'Content-Type: application/json' \
  -d '{
  "model": "omnihuman-2-0",
  "input": {
    "image_urls": [
      "https://example.com/input.png"
    ],
    "audio_url": "https://example.com/input.png",
    "prompt": "Your prompt"
  }
}'

Responses and errors

HTTP 200

Request successful

Task status and callbacks

For asynchronous tasks, keep the returned taskId. Query GET /api/v1/jobs/recordInfo?taskId=... or provide callBackUrl when creating the task. Only the account that created a task can access it or derive new resources from it.

A timeout can mean the submission was accepted. Inspect the existing request in your dashboard; do not create another task automatically. Callback delivery is retried and may arrive more than once. Deduplicate with X-VezAPI-Event-Id.

Files, logs and billing

Generated media normally follows a 14-day provider lifetime; uploaded files expire after 24 hours. Save the files you need before expiration. VezAPI streams registered files without keeping a permanent media library. Request logs are retained for two calendar months.

Credits are reserved before submission. Final deductions match actual discounted consumption one for one. Unknown usage pauses new paid requests. If available funds cannot cover final usage while protecting other reservations, settlement stays pending until funded; model usage cannot make the wallet negative. Time-based inputs require server-side metadata reads; a failed read prevents submission.