Title: Account only issues AQ. keys — all return 401 ACCESS_TOKEN_TYPE_UNSUPPORTED

Gemini API
1

Every API key my account generates has the AQ. prefix, including keys from brand-new Cloud projects. All are rejected by generativelanguage.googleapis.com.

  • Endpoint: POST /v1beta/models/gemini-2.5-flash:generateContent
  • Tried: ?key= query param and x-goog-api-key header, on both v1beta and v1
  • Response: 401 UNAUTHENTICATED — ACCESS_TOKEN_TYPE_UNSUPPORTED
  • Gemini API shows API Enabled in Cloud Console
  • Key restricted to Gemini API, Application restrictions = None
  • Project: 43174576691 / gen-lang-client-09862832..
  • Account: k...@v.com

Requesting account review to restore working API key issuance.

Google staff (Pooja_Kapse, Jon_Matthews) respond in these threads and have restored accounts.

2

Hello @KOMALAN_RAMASH ,

We are moving away from Traffic keys (Alza) and towards a more secure Authentication Key (AQ). AI Studio will now only generate Authentication Key (AQ) keys. More information on key usage can be found in the Using Gemini API keys documentation.

Please submit any compatibility issues with services / SDKs etc. in this form for our engineering team to review. Thanks!