Skip to main content

Overview

LTX 2 19B is a Lightricks video generation model for text-to-video and image-to-video workflows. It also supports LoRA-conditioned variants when you need custom styles, characters, or structural guidance. 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:
Submit requests also require:

Copy-paste async quickstart

This minimal request submits a text-to-video task and returns a taskId.
Successful response:
Save the taskId; you need it to poll for the final result.

Poll for result

Processing response:
Success response:
Failed response:
Parse resultJson after state becomes success:

Request body

Text-to-video

Image-to-video

Image-to-video with LoRA

Parameters

string
default:"async"
required
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 endpoint that can receive the final task payload. See Webhooks.
object
required
LTX 2 19B input parameters.

Response format

Submit task response

POST /generateTask/ltx-2-19b 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: pending, processing, success, or failed.
string
JSON string containing the 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 when available. Present after completion.

Webhook callback mode

Use callback mode when your backend should receive the final result automatically instead of polling.
The callback data object uses the same terminal fields as the status response. See Webhooks for delivery requirements and retry behavior.

Billing

LTX 2 19B is billed per second. The backend selects the unit price by resolution and base vs LoRA mode, then multiplies that unit price by the submitted duration. Formula:
For current route and market comparison pricing, see Pricing.

Latency and polling

Actual latency may vary by prompt complexity, duration, resolution, LoRA loading, provider queue load, and storage transfer time.
For production video workloads, use callback mode to avoid frequent polling while generation is still running.
Result URLs are normally stored for 15 days. Download and store important outputs promptly. For image-to-video modes, provide exactly one source image. Public image URLs should be directly accessible by APIXO; JPG, PNG, or WebP files are the safest choice. For LoRA workflows, use public downloadable model URLs such as Hugging Face or Civitai download links. Each LoRA item must include both path and scale, even if you want a neutral scale like 1.0. 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.