I understand that Interactions API is experimental and subject to change, but this change makes no sense to me and is probably a bug. I have been successfully using Interactions API with file search tool and prepared request like this:
{
model: model,
input: textPrompt,
systemInstruction: textSetup,
previousInteractionId: lastInteractionId,
stream: isStreamSupported,
tools: [
{
type: “file_search”,
fileSearchStoreNames: [store.name]
}
]
}
It has worked well for a month or two. But now it is suddenly expecting snake_case parameters:
{
model: model,
input: textPrompt,
system_instruction: textSetup,
previous_interaction_id: lastInteractionId,
stream: isStreamSupported,
tools: [
{
type: “file_search”,
file_search_store_names: [store.name]
}
]
}
This is not the case with JS API elsewhere in Gemini API (for example with generateContent or generateContentStream), so I would assume this might not have been an intentional change.