Previously working Gemini API broke — account now restricted to AQ. keys, all 401 ACCESS_TOKEN_TYPE_UNSUPPORTED (project gen-lang-client-02513966..)

Gemini API
1

My account/project is restricted to AQ. prefix keys. They all return 401 ACCESS_TOKEN_TYPE_UNSUPPORTED on generativelanguage.googleapis.com. Requesting restoration of AIza-format API keys. Project ID: gen-lang-client-02513966..

{
“error”: {
“code”: 401,
“message”: “Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.”,
“status”: “UNAUTHENTICATED”,
“details”: [
{
“@type”: “type.googleapis.com/google.rpc.ErrorInfo”,
“reason”: “ACCESS_TOKEN_TYPE_UNSUPPORTED”,
“metadata”: {
“method”: “google.ai.generativelanguage.v1beta.GenerativeService.GenerateContent”,
“service”: “generativelanguage.googleapis.com”
}
}
]
}
}

2

Hello @Woraphat_Jankaew ,
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!