403 PERMISSION_DENIED on generateContent with Files API reference, even though billing is linked and text/JSON generateContent work

Gemini API
1

Project ID: axe-jerky
Project number: 591697401..
Billing Account ID: 01AA27-BB6AFC-98B4..

After activating Prepay billing on this project, plain text generateContent and structured JSON output (responseSchema) work correctly with my API key. However, any generateContent call that references an uploaded Files API file (file_data/file_uri, video/quicktime, state ACTIVE) fails with:

403 PERMISSION_DENIED: “The caller does not have permission”

Files API upload and polling (state becomes ACTIVE successfully) work fine — only the reference-in-generateContent step fails. Reproduced identically both from a Cloud Functions backend and via a standalone curl/fetch test directly from my machine, ruling out any client-side or network cause.

Looks like a permission-sync gap specific to file-based multimodal requests after the Paid Tier upgrade. Could someone check whether this project is stuck in a broken quota-tier state for file-based requests specifically, and unblock it?

2

Hello @Pavlo_Konopada ,

We recently rolled out a fix that should have resolved this issue. Request you to retry and let us know if you still face the issue.