# Permission denied when generating video with Veo 3.1 Fast

**URL:** <https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170>\
**Category:** Gemini API\
**Tags:** bug\
**Created:** [September 7, 2026, 3:56am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170 "2026-09-07T03:56:46Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![dd26f32a546b13cf02c9](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/dd26f32a546b13cf02c9/32/147613_2.png) [@dd26f32a546b13cf02c9](https://discuss.ai.google.dev/u/dd26f32a546b13cf02c9)\
**Post date:** [September 7, 2026, 3:56am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170/1 "2026-09-07T03:56:46Z")

</div>

Hello Google AI Studio team,

I am using Google AI Studio with a paid Gemini API project and prepaid billing.

Veo 3.1 Fast was previously working correctly for me and I successfully generated several videos.

Now every new video generation request returns:

**“Failed to generate video: permission denied. Please try again.”**

I have tried Veo 3.1 Fast and Veo 3.1. The error persists.

My project is paid and AI Studio confirms that I am using a paid API key.

This is a legitimate low-volume creative project for testing short marketing/lifestyle videos.

Could you please check whether there is an access restriction, entitlement issue, or automated security flag on my project and restore Veo access if this is a false positive?

I can provide my project ID, screenshots, timestamps and other diagnostic information privately if needed.

Thank you.

---

<div class="post-metadata">

**Author:** ![Javier\_Berrocal\_Tade](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/javier_berrocal_tade/32/148126_2.png) [@Javier\_Berrocal\_Tade](https://discuss.ai.google.dev/u/Javier_Berrocal_Tade)\
**Post date:** [September 8, 2026, 4:04am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170/2 "2026-09-08T04:04:07Z")

</div>

Update with additional diagnostic evidence (8 September 2026):

- Google AI Studio recognizes the project as Paid Tier 1 with active prepaid credit.
- The Gemini API ([generativelanguage.googleapis.com](http://generativelanguage.googleapis.com)) is enabled.
- The Rate Limit page explicitly lists Veo 3 Generate, Veo 3 Fast Generate, and Veo 3 Lite Generate, each with available limits of 2 RPM and 10 RPD. Usage is 0, so this is not quota exhaustion.
- The Projects and Billing pages show the correct project and billing account, with no actionable warning or appeal banner.
- Following the troubleshooting advice given in a similar thread, I attempted to create a fresh API key in AI Studio for the same project. That request was rejected immediately with: “Failed to generate API key. The request is suspicious. Please try again.”

This new result strongly suggests an automated security/trust flag affecting AI Studio or the account/project control plane. The Veo request is also rejected before it is recorded in usage.

Could a Google AI Studio / Gemini API team member please initiate a manual Trust & Safety review and remove the restriction if this is a false positive? I can provide the project ID, billing account reference, timestamps, and screenshots privately to a Googler. I will not publish API keys.

Thank you.

---

<div class="post-metadata">

**Author:** ![Pooja\_Kapse](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/pooja_kapse/32/24754_2.png) [@Pooja\_Kapse](https://discuss.ai.google.dev/u/Pooja_Kapse)\
**Post date:** [September 9, 2026, 11:11am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170/3 "2026-09-09T11:11:26Z")

</div>

Hello @dd26f32a546b13cf02c9@Javier_Berrocal_Tade ,

DM’ed you for details.

---

<div class="post-metadata">

**Author:** ![Pooja\_Kapse](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/pooja_kapse/32/24754_2.png) [@Pooja\_Kapse](https://discuss.ai.google.dev/u/Pooja_Kapse)\
**Post date:** [September 10, 2026, 3:36am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170/4 "2026-09-10T03:36:34Z")

</div>

Hello @Javier_Berrocal_Tade ,

Could you also confirm that the below verifications are done. If not done, please do so and retry creating a new api key linked to your billing-linked project and retry API requests. Just want to rule out any edge cases, Thanks!

Visit [Google Account Security](https://myaccount.google.com/security) and ensure [Phone Verification](https://myaccount.google.com/phone), [2-Step Verification (2SV)](https://myaccount.google.com/signinoptions/twosv), and [Age Verification](https://myaccount.google.com/age-verification) (under [Birthday](https://myaccount.google.com/birthday)) are completed and enabled on the Google Account linked to your AI Studio project.

If you still get the same error, please let us know.

---

<div class="post-metadata">

**Author:** ![Javier\_Berrocal\_Tade](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/javier_berrocal_tade/32/148126_2.png) [@Javier\_Berrocal\_Tade](https://discuss.ai.google.dev/u/Javier_Berrocal_Tade)\
**Post date:** [September 10, 2026, 8:26am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170/5 "2026-09-10T08:26:46Z")

</div>

Hello Pooja,

I have completed the requested checks for the Google Account linked to the AI Studio project:

- Phone verification is completed.
- 2-Step Verification is enabled.
- The Google age-verification page confirms that no further age verification is required for this account.

I then retried creating a new API key in Google AI Studio, explicitly linked to the billing-enabled project:

Project ID: gen-lang-client-08959428..  
Project name: Default Gemini Project  
Billing tier: Paid Tier 1 — Prepaid

The request still fails immediately with the exact error:

“Failed to generate API key. The request is suspicious. Please try again.”

Therefore, the issue persists after completing all requested account-security checks. Could you please escalate this for a manual review of the account/project restriction or automated Trust & Safety flag?

Thank you.

---

<div class="post-metadata">

**Author:** ![Pooja\_Kapse](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/pooja_kapse/32/24754_2.png) [@Pooja\_Kapse](https://discuss.ai.google.dev/u/Pooja_Kapse)\
**Post date:** [September 16, 2026, 7:55am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170/6 "2026-09-16T07:55:55Z")

</div>

Hello @Javier_Berrocal_Tade,

The error could have been triggered by browser-side anti-automation checks instead of an account restriction (as your account is already on paid tier 1). Please try using a different browser or incognito window, closing browser developer tools (DevTools), disable suspicious browser extensions or custom user-agent overrides, and try generating a new key in a clean browser window.

---

<div class="post-metadata">

**Author:** ![no6mis](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/no6mis/32/149021_2.png) [@no6mis](https://discuss.ai.google.dev/u/no6mis)\
**Post date:** [September 18, 2026, 3:57am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170/7 "2026-09-18T03:57:02Z")

</div>

I have the same problem. I’m also using a paid Tier 1 account and get the same error message. I’ve completed age verification, two-factor authentication, and phone verification. Even using the Chrome browser in incognito mode with all extensions disabled didn’t help.

---

<div class="post-metadata">

**Author:** ![no6mis](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/no6mis/32/149021_2.png) [@no6mis](https://discuss.ai.google.dev/u/no6mis)\
**Post date:** [September 18, 2026, 7:31am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170/8 "2026-09-18T07:31:41Z")

</div>

I was able to “fix” the problem by creating a new API key. I don’t understand why the old “default” key caused this problem for me and many others.

---

<div class="post-metadata">

**Author:** ![Javier\_Berrocal\_Tade](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/javier_berrocal_tade/32/148126_2.png) [@Javier\_Berrocal\_Tade](https://discuss.ai.google.dev/u/Javier_Berrocal_Tade)\
**Post date:** [September 22, 2026, 8:25am UTC](https://discuss.ai.google.dev/t/permission-denied-when-generating-video-with-veo-3-1-fast/181170/9 "2026-09-22T08:25:41Z")

</div>

Update: the issue is now resolved.

Following the suggestions in this thread, I opened a clean Chrome Incognito session with extensions and DevTools disabled. In that session I was able to create a new Gemini API key for the same billing-enabled Paid Tier 1 project without receiving the previous “suspicious request” error.

I then linked and saved the new key in my normal Google AI Studio session. Veo 3.1 successfully generated a video, and AI Studio now confirms that the new key is active.

One detail: during testing, video generation also succeeded once while AI Studio still appeared to reference the previous key. Therefore, I cannot confirm whether creating the new key itself fixed the problem or whether a temporary browser-side/security restriction cleared at the same time. What I can confirm is that PERMISSION\_DENIED is no longer reproducible and Veo video generation is working normally.

Thank you @Pooja_Kapse and @no6mis for the help.
