Overview
Hailuo 2.3 generates videos from text prompts or a single first-frame image. Use this page when you are ready to call the API after trying the model in the APIXO playground.Endpoint and authentication
Base URL:
All requests require your APIXO API key:
Copy-paste async quickstart
This minimal request submits a standard text-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 text-to-video
Standard image-to-video
Pro text-to-video
Pro image-to-video
Parameters
string
default:"async"
Result delivery mode. Use
async for polling with statusTask, or callback for webhook delivery.string
Required when
request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.object
required
Hailuo 2.3 input parameters.
Response format
Submit task response
POST /generateTask/hailuo-2-3 returns a task ID when the task is accepted:
integer
API status code.
200 means the task was accepted.string
Human-readable status message.
string
Unique task identifier used with the status endpoint.
Status response fields
string
Unique task identifier.
string
Current task state:
processing, success, or failed.string
JSON string containing generated video URLs in
resultUrls. Present when state is success.string
Machine-readable failure code. Present when
state is failed.string
Human-readable failure message. Present when
state is failed.integer
Task creation timestamp in Unix milliseconds.
integer
Task completion timestamp in Unix milliseconds. Present after completion.
integer
Processing duration in milliseconds. Present after completion when timing data is available.
Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.code, message, and data. See Webhooks for delivery requirements and retry behavior.
Billing
Hailuo 2.3 billing depends on the selected mode family.
For current route and market comparison pricing, see Pricing.
Latency and polling
Actual latency may vary by prompt complexity, image accessibility, mode, provider queue load, and upstream processing time. The status response reportscostTime in milliseconds after completion when timing data is available.
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
Validation notes
Task failure codes
See Error Codes for the full error reference.