Flux 3 - PoYo AI

curl --request POST \
  --url https://api.poyo.ai/api/generate/submit \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "model": "flux-3/text-to-video",
  "input": {
    "prompt": "A red panda walks through a sunlit forest",
    "duration": 5,
    "resolution": "720p"
  }
}
'

{
  "code": 200,
  "data": {
    "task_id": "<string>",
    "status": "not_started",
    "created_time": "2023-11-07T05:31:56Z"
  }
}

{
  "code": 400,
  "error": {
    "message": "Invalid request parameters",
    "type": "invalid_request_error"
  }
}

{
  "code": 400,
  "error": {
    "message": "Invalid request parameters",
    "type": "invalid_request_error"
  }
}

POST

api

generate

submit

curl --request POST \
  --url https://api.poyo.ai/api/generate/submit \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "model": "flux-3/text-to-video",
  "input": {
    "prompt": "A red panda walks through a sunlit forest",
    "duration": 5,
    "resolution": "720p"
  }
}
'

{
  "code": 200,
  "data": {
    "task_id": "<string>",
    "status": "not_started",
    "created_time": "2023-11-07T05:31:56Z"
  }
}

{
  "code": 400,
  "error": {
    "message": "Invalid request parameters",
    "type": "invalid_request_error"
  }
}

{
  "code": 400,
  "error": {
    "message": "Invalid request parameters",
    "type": "invalid_request_error"
  }
}

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.
Regardless of whether callback_url is provided, you can retrieve the result through the unified Query Task Status endpoint.

Select a model based on the source media you want to provide:

Model	Required media input
`flux-3/text-to-video`	None
`flux-3/image-to-video`	One image in `image_urls`
`flux-3/first-last-frame-to-video`	Two ordered images in `image_urls`
`flux-3/extend-video`	One MP4 in `video_url`
`flux-3/keyframes-to-video`	1-10 items in `keyframes`

See the parameter descriptions below for model-specific requirements and limits.

Models

flux-3/text-to-video — Text to video
flux-3/image-to-video — Image to video
flux-3/first-last-frame-to-video — First last frame to video
flux-3/extend-video — Extend video
flux-3/keyframes-to-video — Keyframes to video

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:

Authorization: Bearer YOUR_API_KEY

Body

application/json

model

enum<string>

required

Flux 3 workflow to use. The selected model determines which media input field is required.

Available options:

flux-3/text-to-video,

flux-3/image-to-video,

flux-3/first-last-frame-to-video,

flux-3/extend-video,

flux-3/keyframes-to-video

input

object

required

Show child attributes

callback_url

string<uri>

Webhook URL that receives the finished or failed result.

Response

Task submitted

code

enum<integer>

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

Show child attributes

​Models

Authorizations

Body

Response

Models