Overview
Nano Banana is a fast Google image model for lightweight 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
Nano Banana input parameters.
Response format
Submit task response
POST /generateTask/nano-banana 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. Nano Banana normalizes provider timing to milliseconds.
Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.Billing
Nano Banana is billed per generated image. The public APIXO price is currently a single flat price for this model.
For current route and market comparison pricing, see Pricing.
Latency and polling
Actual latency may vary by prompt complexity, reference image availability, provider route, and current queue load.
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
Task failure codes
See Error Codes for the full error reference.