Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

API Management: Restrict Gemini API keys

Aberta
  • Algo errado?
#1,239 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 2 dias

@Prajna1999 já está trabalhando nisso.

Desde 9/10/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

Is your feature request related to a problem?
Starting June 19, 2026, unrestricted API keys for the Gemini API will no longer be accepted, leading to potential unauthorized usage and billing risks. This causes errors and access issues for users relying on this API.

Describe the solution you'd like

  • Restrict existing API keys for the Gemini API in Google Cloud Credentials.
  • Alternatively, generate new restricted keys in Google AI Studio, which are restricted by default.
Original issue

Starting June 19, 2026, the Gemini API will stop accepting requests from unrestricted API keys to prevent unauthorized usage and billing risks. This error shows up

[GOOGLE_GCP] Authentication / permission denied (code: 403 PERMISSION_DENIED): Lightning dunning decision is deny for project: projects/877240188032. Verify the Google GCP API key is valid and not expired, the project_id and location are correct, and the service account has access to the requested model.

If your Google Cloud project has the Gemini API enabled and contains unrestricted keys, please restrict them immediately.
What to do:

Option 1 (Restrict existing keys): Go to [Google Cloud Credentials](https://console.cloud.google.com/apis/credentials), select your key, and under API restrictions, restrict it to Gemini API ([generativelanguage.googleapis.com](http://generativelanguage.googleapis.com/)).
Option 2 (New keys): Generate new restricted keys in [Google AI Studio](https://aistudio.google.com/app/apikey) and update your code.

Note: Keys generated directly in AI Studio are restricted to the Gemini API by default.

Linguagem predominante
Python
Estrelas
18
Forks
11
Merge médio
3d 5h
PRs com merge (30d)
10

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ProjectTech4DevAI/kaapi-backend

Todas as issues de ProjectTech4DevAI/kaapi-backend

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.