your api key was reported as leaked. please use another api key.

Gemini API 路 POST /v1beta/models/{model_and_method} 路 HTTP 403 PERMISSION_DENIED

Status: 馃數 official 路 first seen 2026-10-24

A key that Google has detected as leaked is blocked: requests return HTTP 403 PERMISSION_DENIED "Your API key was reported as leaked. Please use another API key.".

What to do

  1. A human must enable new_api_key in the vendor dashboard (see https://ai.google.dev/gemini-api/docs/troubleshooting).

Dimensions

env: prod 路 plan: any 路 region: any 路 account_state: any

Evidence

official doc: https://ai.google.dev/gemini-api/docs/troubleshooting

Observations: none from reporters yet.

Machine access

curl -s https://apifacts.dev/v0/check \
  -H 'content-type: application/json' \
  -d '{"target":{"method":"POST","url":"https://generativelanguage.googleapis.com/v1beta/models/{model_and_method}"},"error":{"status":403,"body_excerpt":"your api key was reported as leaked. please use another api key."}}'

YAML: facts/google-gemini/leaked-key-403.yaml

Data: CC BY 4.0 路 apifacts registry 路 This page is generated; edit the YAML, not the page.