Overview
GPT Image 2 is an OpenAI image model for text-to-image generation and reference-guided image editing. 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 text-to-image task and returns ataskId.
taskId; you need it to poll for the final result.
Poll for result
resultJson after state becomes success:
Request body
Text-to-image
Image-to-image
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
GPT Image 2 input parameters.
Response format
Submit task response
POST /generateTask/gpt-image-2 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 image URLs. 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 successful completion.
Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.Billing
GPT Image 2 is billed per generated image. The selectedquality and billed resolution determine the unit price.
For current route and market comparison pricing, see Pricing.
Latency and polling
Actual latency may vary by prompt complexity, provider route, and current queue load.Size rules
sizecan be either a supported ratio value or a customWIDTHxHEIGHT.- Supported ratio values are the same as
aspect_ratio:auto,1:1,1:2,2:1,2:3,3:2,4:3,3:4,4:5,5:4,16:9,9:16,21:9. - When both
sizeandaspect_ratioare provided,sizetakes precedence. 1:2and2:1are supported.- When
resolution=4k, only16:9,9:16,21:9,1:2,2:1, or customWIDTHxHEIGHTwith one edge equal to3840will keep4k. - When
resolution=4kis used with other supported ratios, or with customWIDTHxHEIGHTwhose two edges are both not3840, the task will be processed as2k. - Custom
WIDTHxHEIGHTrequires both dimensions to be divisible by16. - Custom
WIDTHxHEIGHTcannot exceed3840pixels on either edge. - Custom
WIDTHxHEIGHTtotal pixels must stay between655360and8294400. - Custom
WIDTHxHEIGHTaspect ratio cannot exceed3:1. - Custom
WIDTHxHEIGHTrequiresresolutionto be2kor4k.
429, slow down requests and retry with backoff. For account-level details, see System APIs.
Errors and troubleshooting
HTTP errors
Task failure codes
See Error Codes for the full error reference.