Console Batch Images

The /batch-image page submits multiple image prompts as one managed job, with unified status and downloads. Batch images currently require an API Key bound to an eligible Gemini group with batch image generation enabled by an administrator.

Before creating a job

1. Create an API Key bound to the target Gemini group.
2. Confirm that the Key, USD balance, and quota windows are available.
3. Select the Key, then choose a model from the returned eligible model list.
4. Prepare a unique custom_id and prompt for every item.

Do not guess a model name. The model selector is filtered by current Key and group capability.

Creating a job

A job can specify:

• Task name.
• Model, image size, and aspect ratio.
• Multiple prompt items.
• Output count per item.
• Optional reference images.
• A unique tracking custom_id.

custom_id maps output files and errors back to a business item. Never duplicate it within one job. For large jobs, derive it from a stable business ID instead of an array index.

The page shows estimated cost and a hold before submission. QuotaAPI reserves part of the USD balance, settles against successful results, and releases excess hold. Estimated cost is not the final charge.

Status reference

Status	Meaning
queued	Waiting in the queue
running	Being submitted or processed
indexing / processing_results	Indexing and organizing results
settling	Calculating actual cost and releasing the hold
completed	Complete and available for viewing or download
failed	Job failed; inspect item errors
cancelled	Job cancelled
output_deleted	Stored outputs removed while the job record remains

Filter the list by task name, API Key, status, and download state. Details separate success count, failure count, estimated cost, hold, and actual cost.

Retrying failed items

When a terminal job has failed items, use Retry failed items. QuotaAPI creates a child job with parent_batch_id and copies only eligible failed items. The list displays the parent-child relationship. Successful items are not generated or billed again.

Inspect each error first. Correct invalid prompts or parameters before retrying; direct retry is appropriate for temporary service failures.

Downloads and cleanup

• Item content: download a specific output by custom_id.
• ZIP: download successful outputs and a manifest.
• Selected jobs: download several completed jobs.
• Delete outputs: remove files from object storage while retaining the job record.
• Delete record: available only for terminal jobs and not a substitute for cancellation.

Downloads are timestamped. Output retention follows system configuration, so move important files into your own storage promptly.

Cancelling a job

Eligible non-terminal jobs expose a cancel action. Cancellation is best effort: work already accepted by the target platform may still produce output or cost. Final settlement remains the source of truth.

API relationship

The console uses the /v1/images/batches endpoint family. Direct API submissions should include Idempotency-Key. See Image Generation, Editing, and Async Tasks for a request example.

Common errors

• Empty model list: the Key is not bound to Gemini or batch images are disabled for its group.
• Insufficient balance on submit: estimated hold exceeds available USD balance.
• Partial failure: open item details and diagnose by custom_id.
• Download unavailable: job is incomplete, outputs were deleted, or retention expired.
• Stuck in settling: open a ticket with batch ID and time; do not create a duplicate job.