Manual review request: 403 PERMISSION_DENIED — project denied access

Hello Google Gemini API team,

I am requesting a manual review of my Gemini Developer API access.

Every generateContent request returns:

403 PERMISSION_DENIED
Your project has been denied access. Please contact support.

Account and environment:

Country: India
Account type: Personal Google account
IAM role: Owner
Billing: Free Tier / no billing account
SDK: Official @google/genai JavaScript SDK
Model tested: gemini-2.5-flash

Projects tested:

Project ID: facebook-multi-page-publisher
Project number: 4479907050..

Project ID: facebook-publisher-gemini
Project number: 1405910708..

Troubleshooting completed:

  • Created fresh API keys through Google AI Studio
  • Created and imported a new Google Cloud project
  • Confirmed that my account is the project Owner
  • Confirmed that the API keys are recognized
  • Tested multiple fresh projects and keys
  • The same 403 error occurs on every project
  • No API key is exposed in client-side code
  • The API is used only from a secure server environment

Use case:

I am building a server-side Facebook publishing tool. Gemini analyzes an uploaded video and generates an English title, caption, exactly five hashtags, and a recommended thumbnail timestamp.

Please manually review my account/projects and restore Gemini Developer API access. I can provide redacted logs or request details if required.

Thank you.

Hello @Sk_Gous ,

Getting a 403 API error response and / or seeing “Unavailable” next to your project in AI audio indicates a flag has been placed on your account. To proceed:

  1. Check for banners / error callouts in the AI Studio Projects page & the Billing page. Mostly these flags cause visible banners or other errors on these pages with concrete next steps / appeal links.

  2. If you’re on the free tier with no billing attached, you should consider setting up billing. In most cases this is enough to clear any flag on your account. Please note this will mean you lose your free tier quota.

We apologise if the above doesn’t resolve the problem for you. We’re working to improve our messaging in AI Studio and support processes to handle this better.