Picsart API Platform
← All models

Hunyuan V3

Hunyuan · Image · Text → Image

Infographic-friendly generation with readable text and cfg control.

Model ID: hunyuan-v3Workflow: hunyuan-image/v3/text-to-image
1K
Try on Playground ↗

Authentication

Send your Picsart API key as a bearer token on every request.

Header
Authorization: Bearer <PICSART_API_KEY>

Make a request

One endpoint serves every model: POST to /workflows/v1/models/execute with the model id and its input in the body. The nesting is deliberate — the outer paramsis the envelope every workflow takes, and the inner one is this model's own input. Those inner names are the same unified ones the SDK takes, so a call translates one-to-one between the two — no per-vendor naming to learn.

cURL
curl -X POST 'https://api.picsart.com/workflows/v1/models/execute' \
  -H 'Authorization: Bearer $PICSART_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "params": {
    "model": "hunyuan-v3",
    "params": {
      "prompt": "A serene mountain lake at golden hour, ultra detailed",
      "aspectRatio": "16:9"
    }
  }
}'

Parameters

5 parameters, sent inside the inner paramsobject. Identical to the SDK's — one parameter set, whichever transport you use.

ParameterTypeRequiredDefaultDetails
prompt
Prompt
textyes
aspectRatioenumno16:91:1, 16:9, 9:16, 4:3, 3:4
countenumno11, 2, 4
negativePrompt
Negative Prompt
textno
cfgScale
CFG Scale
rangeno7.51–20 (step 0.5)

Response

The body arrives in the gateway's status envelope, so the output is at response.result — alongside the task id, its status and the credits charged. Asset models return url plus an items array; text models return text instead.

Response body
{
  "status": "success",
  "response": {
    "id": "task_abc123",
    "status": "COMPLETED",
    "result": {
      "url": "https://cdn.picsart.com/…/result",
      "items": [
        {
          "url": "https://cdn.picsart.com/…/result"
        }
      ],
      "model": "hunyuan-v3"
    },
    "usage": {
      "credits": 3
    }
  }
}