Skip to main content

Overview

Runway Gen4 Image Turbo is a faster image generation model for prompt-driven images and reference-guided generation. It keeps the same public parameter shape as Runway Gen4 Image, with a flat per-image price.

Endpoint and authentication

Base URL:
All requests require your APIXO API key:
Submit requests also require:

Copy-paste async quickstart

Successful response:

Poll for result

Success response:

Request body

Text-to-image

Text-to-image with optional references

Image-to-image

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
Runway Gen4 Image Turbo input parameters.

Response format

Submit task response

POST /generateTask/runway-gen4-image-turbo 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 generated image 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.

Webhook callback mode

Use callback mode when your backend should receive the final result automatically instead of polling.
See Webhooks for delivery requirements and retry behavior.

Billing

Runway Gen4 Image Turbo is billed at a flat per-image price. text-to-image and image-to-image use the same public APIXO price.

Latency and polling

Actual latency may vary by prompt complexity, reference image accessibility, and current queue load.
For production image workloads, use callback mode to avoid frequent polling while generation is still running.

Validation notes

Errors and troubleshooting

See Error Codes for the full error reference.