403 PERMISSION_DENIED — "Your project has been denied access" on Workspace-owned project (gen-lang-client-01776000..)

Gemini API
1

Hello,

I am requesting a review and unlock of access to the Gemini API for the project listed below. The error appears consistently on a freshly created project under a Google Workspace domain, with no policy violation and no prior usage history.

Account context

  • Workspace domain: cannabreedbrasil
  • Account email: l...@cannabreedbrasil.com
  • Project ID: gen-lang-client-0177600…
  • Project display name: Cannabreed Whatsapp
  • Region: Brazil
  • Use case: lead qualification chatbot for our company’s WhatsApp Business channel (internal automation, low volume — under 1,000 requests/day)

Error details

Every request to the Generative Language API returns:

{
“error”: {
“code”: 403,
“message”: “Your project has been denied access. Please contact support.”,
“status”: “PERMISSION_DENIED”
}
}

Troubleshooting already completed

  • API key successfully created via Google AI Studio with the Workspace account above.
  • Generative Language API is confirmed enabled in the project (status: “API enabled” in Google Cloud Console).
  • API key has no restrictions configured (no HTTP referrer, no IP, no API restriction).
  • Tested with a minimal curl/HTTP POST request — same error.
  • Account is fully verified and in good standing; no policy violations on record.
  • Project was created automatically by AI Studio upon key generation — never used previously, no prior calls or quota consumption.

Pattern observed in community reports

This error pattern has been reported by multiple users in this forum over the past weeks, predominantly affecting projects created under Google Workspace domains. Several reporters have confirmed that the exact same setup works when the key is created from a non-Workspace personal Gmail account.

Request

I would like to request:

  1. Review of project gen-lang-client-0177600078 and unblocking of Gemini API access, so the key created under the corporate Workspace account can be used in production.
  2. If the block is the result of an automated risk classifier and was triggered in error, confirmation of that and reinstatement of access.
  3. Any additional information you may need from me to expedite the review.

I am happy to provide any further context required.

Thank you in advance for your time.

Best regards,
Pedro Lyra
Cannabreed Brasil

2

Sorry to hear about this. We’re treating this as a potential bug in Gemini API. Could you please enter the details of projects receiving unexpected 403 errors into this form?

3

Hi, I also experience the same issue, which happened suddenly without any reason. Please help.

4

hmm, I also see the same issue.

5

  1. Provide your exact bugged Project ID that we found earlier:

    Plaintext

    gen-lang-client-08749941..

  2. Submit the form.

6

I continue to see this error and my GCP dashboard shows nothing, no banner, no mention of the issue - what can I do?

7

Facing same -

Hello Google Gemini API team,

I am requesting a manual review and unblock of Gemini API access for two of my projects. Both are returning 403 PERMISSION_DENIED: “Your project has been denied access. Please contact support.” on all REST API calls.

Project Details:

  • Project Number: 7733848672..
  • Project Number: 7563117021..
  • Region: India (Gujarat, Rajkot)
  • Use Case: Medical AI application (Gemini Live API integration for real-time assistance)

Troubleshooting Already Done:

  • Confirmed both API keys are valid (no API_KEY_INVALID error)
  • Generative Language API is enabled on both projects
  • API key restrictions updated — restricted to Gemini API only (not unrestricted)
  • Tested with keys generated both from Google Cloud Console and Google AI Studio
  • Tested with fresh keys after saving restrictions — same 403 on both
  • No VPN in use
  • No banner or warning visible on either project dashboard in Cloud Console
  • Google AI Studio web playground works fine with the same Google account
  • Issue persists across both projects, ruling out a single project misconfiguration
  • Waited 15+ minutes after applying key restrictions — no change

Error Response (identical on both projects):

{
  "error": {
    "code": 403,
    "message": "Your project has been denied access. Please contact support.",
    "status": "PERMISSION_DENIED"
  }
}

This strongly appears to be a false positive from an automated abuse-detection filter, as AI Studio works perfectly on the same account but the REST API is blocked across all projects.

I have also submitted the official unblock form. Could someone from the team please manually review and restore API access for both project numbers listed above?

Happy to provide any additional information needed. Thank you.

8

@Jon_Matthews Additional finding: The block appears to be at account level, not project level. Brand new projects under the same account immediately return 403, while a completely new Google account works fine. Both affected project numbers: 7733848672.. and 7563117021… Please review at account level.