Documentation Index
Fetch the complete documentation index at: https://apixo.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Hailuo 2.3 Fast is an image-to-video model for turning one source image into a short generated video. Use this page when you are ready to call the API after trying the model in the APIXO playground.| Capability | Value |
|---|---|
| Model ID | hailuo-2-3-fast |
| Modes | standard-image-to-video, pro-image-to-video |
| Input type | Image-to-video only |
| Reference images | Exactly 1 image URL |
| Standard duration | 6 or 10 seconds |
| Pro duration | Fixed 6 seconds |
| Output resolution | Standard: 768p; Pro: 1080p |
| Result type | Video URL in resultJson.resultUrls |
Endpoint and authentication
Base URL:| Method | Endpoint | Purpose |
|---|---|---|
POST | /generateTask/hailuo-2-3-fast | Submit a generation task |
GET | /statusTask/hailuo-2-3-fast?taskId={taskId} | Poll task status and retrieve results |
Copy-paste async quickstart
This minimal request submits a standard image-to-video task and returns ataskId.
taskId; you need it to poll for the final result.
Poll for result
resultJson after state becomes success:
Request body
Standard image-to-video
Pro image-to-video
Parameters
Result delivery mode. Use
async for polling with statusTask, or callback for webhook delivery.Required when
request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.Hailuo 2.3 Fast input parameters.
Response format
Submit task response
POST /generateTask/hailuo-2-3-fast returns a task ID when the task is accepted:
API status code.
200 means the task was accepted.Human-readable status message.
Unique task identifier used with the status endpoint.
Status response fields
Unique task identifier.
Current task state:
processing, success, or failed.JSON string containing the generated video URLs. Present when
state is success.Machine-readable failure code. Present when
state is failed.Human-readable failure message. Present when
state is failed.Task creation timestamp in Unix milliseconds.
Task completion timestamp in Unix milliseconds. Present after completion when available.
Processing duration in milliseconds. Present after completion when available.
Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.Billing
Hailuo 2.3 Fast billing depends on the selectedmode. Standard mode is billed by output duration; pro mode is billed per task.
| Mode | Unit | APIXO price | Billable amount |
|---|---|---|---|
standard-image-to-video | Per output second | $0.032 / second | duration * $0.032 |
pro-image-to-video | Per task | $0.33 / use | $0.33 |
Latency and polling
Video generation is asynchronous. Actual latency may vary by input image, prompt complexity, current queue load, and storage transfer time.| Mode | Output duration | Recommended first poll | Poll interval |
|---|---|---|---|
standard-image-to-video | 6 or 10 seconds | 30s after task creation | 10s |
pro-image-to-video | Fixed 6 seconds | 30s after task creation | 10s |
costTime is returned in milliseconds after completion when timing data is available. Keep polling while state is processing.
Rate limits and concurrency can vary by account, API key, and route. If you receive 429, slow down requests and retry with backoff. For account-level details, see System APIs.
Errors and troubleshooting
HTTP errors
| Code | Meaning | What to do |
|---|---|---|
400 | Invalid request body, missing required field, unsupported mode, invalid duration, or invalid input URL | Fix the request before retrying |
401 | Missing or invalid API key | Check the Authorization header |
402 | Insufficient balance or quota | Add balance or switch account/key |
403 | Key or route cannot access the model | Check permissions and route strategy |
429 | Rate limit or concurrency limit reached | Retry with exponential backoff |
500 | Server error or unmapped upstream failure | Retry with backoff |
502 | Upstream provider error | Retry with backoff |
504 | Upstream timeout | Retry or use callback mode for long-running jobs |
Task failure codes
Failure codes are mapped from upstream task errors, so exact values can vary. Common examples include:| Fail code | Meaning | What to do |
|---|---|---|
PromptInvalid | Prompt was invalid or rejected | Rewrite the prompt and retry |
SensitiveContent | Prompt or media violated provider policy | Change the prompt or input image |
NSFW | Input or output was flagged as NSFW | Use different content |
ProhibitedContentDetected | Prohibited content was detected | Change the prompt or input image |
ImageFormatIncorrect | Image format or upload validation failed | Use a public JPG, JPEG, or PNG URL |
InvalidImageSize | Image dimensions or size were invalid | Check aspect ratio, short side, and file size |
RateLimited | Upstream provider rate limit was reached | Retry with exponential backoff |
Timeout | Upstream provider timed out | Retry, simplify the prompt, or use callback mode |
InsufficientBalance | Provider-side balance or quota was insufficient | Retry later or contact support |
Unknown error | Upstream failure was not mapped to a known code | Retry with backoff; contact support if it persists |
Request checks
- Send exactly one
image_urlsitem. - Use only
standard-image-to-videoorpro-image-to-video. - Include
durationonly when you need standard mode; pro mode ignores it. - Use
durationas6,10,"6", or"10"for standard mode. - Use a public, directly fetchable JPG, JPEG, or PNG image URL.