Overview
Image Upscaler is an asynchronous image-to-image API for enlarging and enhancing one source image. Use it when you already have an image URL and want a higher-resolution output without writing a text prompt.Endpoint and authentication
Base URL:
All requests require your APIXO API key:
Copy-paste async quickstart
This minimal request submits a 4k JPG upscaling task and returns ataskId.
taskId; you need it to poll for the final result.
Poll for result
resultJson after state becomes success:
Parse
resultJson only after state becomes success.Request body
Default 4k JPG
8k WebP
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 URL that can receive the final task payload. See Webhooks.object
required
Image Upscaler input parameters.
Response format
Submit task response
POST /generateTask/image-upscaler 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 upscaled image URL 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. For polling success responses, Image Upscaler reads this from the upstream inference timing.
Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.Billing
Image Upscaler is billed per submitted image at$0.01 / image. In the current backend implementation, billing is fixed for the model and does not vary by resolution or output_format.
For current route and market comparison pricing, see Pricing.
Latency and polling
Image Upscaler tasks run asynchronously. Actual latency varies by source image size, selected target resolution, upstream queue load, and result storage time.
Recommended polling pattern:
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
Request validation
Task failure codes
See Error Codes for the full error reference.