`POST /v1beta/interactions` succeeds, but `GET /v1beta/interactions/{id}` returns `403 permission_denied` for Deep Research

Gemini API
,
1

Hi Google AI team,

I’m reporting what looks like a Gemini Deep Research / Interactions API issue.

Summary

For the same API key:

  • normal Gemini generateContent requests work
  • POST /v1beta/interactions also works and returns a valid interaction ID
  • but GET /v1beta/interactions/{id} immediately returns 403 permission_denied

This breaks the documented Deep Research polling flow.

Reproduced On

March 8, 2026, around 11:35 UTC.

Environment

  • API style: raw REST and Python SDK
  • Python SDK: google-genai==1.61.0
  • Agent: deep-research-pro-preview-12-2025
  • Endpoint: https://generativelanguage.googleapis.com/v1beta/interactions

Control Test

The same API key works fine for normal Gemini generation:

curl -sS \
  -H "x-goog-api-key: $GEMINI_API_KEY" \
  -H "Content-Type: application/json" \
  "https://generativelanguage.googleapis.com/v1beta/models/gemini-2.5-flash:generateContent" \
  -d '{
    "contents": [
      {
        "parts": [
          { "text": "What is the capital of France? Answer in one short sentence." }
        ]
      }
    ]
  }'

This returns 200 OK and a valid answer.

Minimal Reproduction

1. Create a Deep Research interaction

curl -i -sS \
  -H "x-goog-api-key: $GEMINI_API_KEY" \
  -H "Content-Type: application/json" \
  "https://generativelanguage.googleapis.com/v1beta/interactions" \
  -d '{
    "input": "What is the capital of France? Answer in one short sentence.",
    "agent": "deep-research-pro-preview-12-2025",
    "background": true,
    "store": true
  }'

Observed result:

  • HTTP status: 200
  • response body contains a valid interaction ID, for example:
{
  "id": "v1_ChdtR090YWVMOUwtT3RfUFVQdHRMeW1RURIXbUdPdGFlTDlMLU90X1BVUHR0THltUVE",
  "status": "in_progress",
  "agent": "deep-research-pro-preview-12-2025"
}

2. Poll the interaction

curl -i -sS \
  -H "x-goog-api-key: $GEMINI_API_KEY" \
  "https://generativelanguage.googleapis.com/v1beta/interactions/v1_ChdtR090YWVMOUwtT3RfUFVQdHRMeW1RURIXbUdPdGFlTDlMLU90X1BVUHR0THltUVE"

Observed result:

  • HTTP status: 403
  • body:
{
  "error": {
    "message": "There was a problem processing your request. You will not be charged.",
    "code": "permission_denied"
  }
}

Expected Result

GET /v1beta/interactions/{id} should return the interaction object so the client can poll until completion, as described in the Interactions / Deep Research docs.

Actual Result

create succeeds, but get fails with 403 permission_denied, making Deep Research unusable even though the API key works for other Gemini endpoints.

Additional Notes

  • This reproduces with raw REST, not just the Python SDK.
  • This is not the older v1alpha / invalid_request issue.
  • store=false is not a workaround, because the API returns 400 for background interactions unless store=true.
  • We also verified the same behavior in Python with google-genai==1.61.0: interactions.create(...) succeeds, then interactions.get(id) fails with the same 403.

Related Threads

Could you confirm whether this is a backend issue, account capability issue, or a known regression in the Interactions API?

3 Likes
2

same issue

{“error”:{“message”:“There was a problem processing your request. You will not be charged.”,“code”:“permission_denied”}}

1 Like
3

Same 403 error! Legit keys!

Error details: “There was a problem processing your request. You will not be charged.”

1 Like
4

Hi

i wanted to follow up here, as i am unable to reproduce this

Are you getting the error always or it that sporadic ?

[Update] We identified the issue and it has been resolved .

2 Likes