Hello
I tried to use Veo 2 in N8N to generate videos at scale, and while my API calls are successfull, I get a weird error message in the returned URI, about a project I don’t own where I need to enable Gemini. Not sure what to do and why this gcp project is mentioned as I can’t access it and it isn’t call in my API calls
Anyone with a similar situation?
Hi @Anthony_Roger , Welcome to the forum.
Is this error specific to Veo 2? Have you tried using other Gemini models to see if the error persists?
403 error usually means your API key is not valid or doesn’t have the right access.
Thanks for the troubleshooting steps. So I tried other gemini model with the same GCP account/API key and it works. The issue I face: Veo does return 200 status code for my 2 API calls (I post my image+ pompt and then wait for the async process to end to get the completed URI) so I believe I am successful at calling this API. The issue is that when I get the final URI from Veo, it shows a 403 error about a GCP project ID I don’t own, and I don’t call anywhere in my flow. I searched in GCP for that project ID (I only have 2 projects) and this ID doesn’t exist so either I don’t something wrong or it is a gcp bug
Also I am actually being charged for my API calls so these first 2 calls work 
OK I made some progress, I believe my issue may be based on the fact that I didn’t use OAUTH2 and just passed an API KEY in my query. I was charged for the successful API calls but could not retrieve the URI as it was blocked
Next issue: What scope should I use for Veo 2? The API document is not really clear (even when I gemini it it doesn’t tell much) so hoping the tech writer at Google will make an effort to make this more accessible.