Create images through the API

Generate and protect your API key

Open Account, then API key. Each account has one active key. Regenerating invalidates the previous token immediately while preserving usage statistics.

Send the token only in the Authorization header.
Never place an API key in browser code, screenshots, or a public repository.

Send a generation request

Use JSON for prompt-only requests or multipart form data when you include reference images. Requests are accepted only through the API subdomain. The prompt is required and accepts up to 2,000 characters.

POST /api/ai/images creates a private image.
POST /api/ai/images/publish creates and publishes the result.
Image API requests are synchronous. Concurrent requests share the account limit, and HTTP 409 responses do not consume quota.

Read quota and request logs

API quota is separate from daily web quota. One quota is charged only after a successful generation. Validation, moderation, quota, and provider failures do not consume it.

Use the latest request logs to diagnose status codes and duration.
Regenerating a token does not reset quota or logs.

Handle errors by status code

Treat 401 as an invalid key, 403 as a blocked account, 422 as invalid or rejected input, 429 as exhausted quota, and 503 as a temporary review failure.

Do not retry 401, 403, 422, or 429 without correcting the cause.
Use bounded retries with backoff for temporary 503 or network failures.

curl -X POST https://api.genanh.com/api/ai/images \ -H "Authorization: Bearer genanh_xxx" \ -F "prompt=A cinematic product photo with soft studio lighting" \ -F "model=cx/gpt-5.5-image" \ -F "images[]=@/path/to/reference.jpg"

Create images through the API

Working cURL example