Gemini API (Interactions API) changelog

Generate Content API now stores requests by default on new paid projects

New projects using generateContent, streamGenerateContent and batchGenerateContent on the paid tier now store requests by default (store=true), matching the Interactions API. Existing projects keep their current setting.

Who is affected:

Developers creating new paid-tier projects on the Generate Content API will have requests logged unless they opt out.

What to do:

Set store=false on individual requests or turn off Generate Content API logging in the Logs and Datasets settings if you do not want requests stored.

Gemini Interactions API changes its request and response schema

The Interactions API schema changes from outputs to steps and the output format configuration changes to response_format. The new schema became the default on May 26, 2026 and the legacy schema was removed on June 8, 2026.

Who is affected:

Code that parses Gemini Interactions API responses using the old outputs field.

Action needed:

Migrate parsing code to the steps schema using Google's migration guide.