Skip to main content
POST
  1. After submission, a task_id will be returned. If you provided a callback_url, when the task status becomes finished or failed, a POST request will be sent to the callback_url.
  2. Regardless of whether callback_url is provided, you can retrieve the result through the unified Query Task Status endpoint.
omni-flash creates short videos from text prompts, optional image references, or an optional video reference.

Models

  • omni-flash - Text-to-video, image-to-video, reference image fusion, and video-input generation

Input modes

  • Text to video: Send prompt only, plus optional resolution, duration, and aspect_ratio
  • Image to video: Send prompt and exactly one image in image_urls
  • Reference image fusion: Send prompt and exactly three images in image_urls
  • Video input: Send prompt and one video in video_urls; omit duration

Required parameters

  • prompt: Text prompt describing the scene, motion, style, camera behavior, and other generation instructions

Optional parameters

  • image_urls: Image URL array. Allowed counts are 0, 1, or 3
  • video_urls: Video URL array. At most 1 video is allowed
  • resolution: 720p, 1080p, or 4k. Default is 720p
  • duration: 4, 6, 8, or 10 seconds. Default is 6. Do not provide this field when video_urls is provided
  • aspect_ratio: 16:9 or 9:16. 16:9 is landscape, and 9:16 is portrait. Default is 16:9
  • callback_url: Optional webhook URL for completion notifications

Examples

Text to Video

Image to Video

Three-Image Reference Fusion

Video Input

Notes

  • Use public HTTPS image and video URLs, or upload files through the playground before submitting
  • image_urls with two images is not supported
  • video_urls supports at most one video
  • When video_urls is provided, duration must be omitted
  • The response returns a task_id; query task status to retrieve generated video files

Authorizations

Authorization
string
header
required

All API endpoints require Bearer Token authentication.

Create an API key: sign in to PoYo, open Dashboard → API Key at poyo.ai/dashboard/api-key, and click to create a key.

Add it to the request header:

Body

application/json
model
enum<string>
required

Omni Flash model identifier

Available options:
omni-flash
input
object
required
callback_url
string<uri>

Webhook callback URL for result notifications

Example:

"https://your-domain.com/callback"

Response

Task submitted successfully

code
enum<integer>
required

Business status code. 200 means success; any other value means the request failed. Always check this field: some validation errors return HTTP 200 with code: 400 in the body.

  • 200: Success
  • 400: Invalid request parameters
  • 401: Missing or invalid API key
  • 402: Insufficient credits
  • 403: Permission denied
  • 404: Resource not found
  • 408: Request timeout
  • 429: Rate limit exceeded
  • 500: Internal server error
  • 502: Upstream service error
  • 503: Service unavailable

See Error Codes for details.

Available options:
200,
400,
401,
402,
403,
404,
408,
429,
500,
502,
503
Example:

200

data
object
required
message
string
Example:

"success"