Skip to content

Nano Banana API to Pixapi migration

Nano Banana API has upgraded to Pixapi. The product, account system, API keys, credits, subscriptions, invoices, and user entitlements remain on the same platform foundation. Most integrations only need to update the API base URL.

What changed

AreaBeforeNow
Websitehttps://nanobananaapi.devhttps://pixapi.ai
API base URLhttps://api.nanobananaapi.devhttps://api.pixapi.ai
DashboardNano Banana API account pagesPixapi account pages
AuthExisting API keySame API key
CreditsExisting purchased and granted creditsPreserved
Subscription benefitsExisting plan and renewal statePreserved

Required integration change

Replace the base URL in your server-side integration:

diff
- https://api.nanobananaapi.dev
+ https://api.pixapi.ai

Request paths, headers, API key authentication, request bodies, and response formats remain compatible unless a model page documents a model-specific change.

Example

bash
curl https://api.pixapi.ai/v1/images/generation \
  -H "Authorization: Bearer $PIXAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gemini-3.1-flash-image-preview",
    "prompt": "A clean product photo of a ceramic mug",
    "size": "1:1"
  }'

Account and billing continuity

No purchased credit, granted credit, subscription entitlement, invoice, or API key is reset by the brand upgrade. Your balance and billing history remain available after signing in on Pixapi.

Compatibility guarantees

  • Existing API keys remain valid.
  • Purchased credits and remaining granted credits remain unchanged.
  • Subscription plans, renewal state, and plan benefits remain unchanged.
  • Request paths and response shapes remain compatible for the same model IDs.
  • Dashboard account history, invoices, and usage records remain tied to the same user account.

Operational notes

  • Update customer-facing copy from Nano Banana API to Pixapi.
  • Update server configuration, SDK examples, and environment variables that store the API base URL.
  • Keep legacy Nano Banana request-shape references only where they are explicitly documented as transition compatibility.
  • Monitor usage and credit consumption after switching traffic to Pixapi.

Checklist

  1. Update your API host to https://api.pixapi.ai.
  2. Keep the same API key and request headers.
  3. Run a test request from your backend.
  4. Confirm your credit balance in the Pixapi dashboard.
  5. Remove hardcoded references to nanobananaapi.dev from docs, logs, and UI.