CS-SAMPLE-001 · Illustrative

Interactions API response shape migration

This demonstration uses Google's public May 2026 migration guide. ContractSignal did not autonomously detect this event, and no private consumer code was inspected.

Summary

Provider	Google Gemini API
Surface	Interactions API (`v1beta`)
Severity	Breaking, identified by the provider
Confidence	High for documented behavior; unknown for a specific consumer

Before and after

- interaction.outputs[-1].text
+ interaction.output_text

- response.outputs[]
+ response.steps[]

The guide documents a structured steps response and recommends the SDK's output_text convenience property.

Potential impact

Code that reads outputs, parses old streaming event names, or carries legacy response objects through stateless history may require migration. Actual impact depends on SDK version and implementation.

Recommended check

Search for interaction.outputs, old streaming names and response_mime_type.
Run existing integration tests against the new API revision or SDK.
Update parsing according to the provider checklist.
Confirm behavior before the documented legacy removal.

Source: Google Gemini Interactions API breaking changes migration guide.

Return to the ContractSignal experiment.