Gemini Image API — HTTP 400 content_blocked after multiple successful product image generations

Hello Google Gemini API Support Team,

I am experiencing a recurring issue with image generation through the Gemini API in my UK e-commerce automation project.

We use the Google image generation API to create professional product photographs for eBay listings, mainly vinyl records, footwear and small consumer products.

The system previously generated more than a dozen successful 2K product images using this workflow. However, our two most recent attempts have failed.

Latest confirmed failure:

  • Date: 2 November 2026

  • Product: PinkPantheress — Heaven Knows (vinyl record)

  • Task: Generate a clean, professional product image based on the original photographs of the physical item, preserving the product’s appearance and artwork

  • HTTP status: 400

  • API error: content_blocked

  • Detailed reason: Not provided

  • Image generated: No

  • Our internal job reference: ed450bc6616545038e5c1d8b0de4e0fa

This is a legitimate product photography workflow involving physical retail products. We are not requesting prohibited or harmful content.

The error provides no actionable explanation. We cannot determine whether it is caused by the input image, the prompt, the requested transformation, the model’s output filters or a recent service change.

Could you please clarify:

  1. What specifically triggers content_blocked in this type of image-generation request?

  2. Is it possible to obtain a more detailed reason, including whether the block relates to copyright/recitation, input-image screening or output-image screening?

  3. Have there been any recent changes or known issues affecting image generation that could explain why previously successful workflows are now failing?

  4. Are there recommended model settings or supported request formats for faithful product photography, especially commercial product packaging and vinyl album covers?

  5. Are failed HTTP 400 requests charged, and how can we verify the final billing status?

  6. What additional request identifiers or diagnostic logs would help your team investigate these failures?

We have preserved the error response and operation logs and can provide the exact model ID, request parameters, timestamps and sanitized diagnostic data.

This issue is disrupting our automated product listing process. We would appreciate guidance on identifying the cause and restoring reliable image generation without compromising your usage policies.

Thank you for your assistance.

Kind regards,

Reselling AI Engine
United Kingdom

Hello @lukasz_kyc ,

This error occurs when built-in policy, safety, or copyright/recitation filters block an uploaded image or generated output, and the API does not return a more specific sub-reason (see Generation blocked codes). Built-in protections cannot be turned off in safety settings, so keep edits to product images you have the rights to modify and avoid reproducing copyrighted cover art or recognizable people (see Image editing).

Failed HTTP 400 requests are not charged for tokens (see Billing FAQ). You can check your AIS prepaid wallet history at https://aistudio.google.com/billing and Gemini API charges in Cloud Billing reports.