●Change8

Migrating to Mistral Client v2.0.0

Version v2.0.0 introduces 4 breaking changes. This guide details how to update your code.

Released: 3/10/2026

4
Breaking Changes
4
Migration Steps
12
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

mistralaimistralai.clientmistralai.azure.clientmistralai.gcp.clientMistralAzureMistralGCPMistralGoogleCloudFunctionTool.typeCreateAgentRequestListFilesResponseBatchJobCheckpoint

Breaking Changes

●Issue #1

All import paths have changed due to the SDK becoming a PEP 420 namespace package. Users must update imports from `mistralai.X` to `mistralai.client.X`.

●Issue #2

42 request/response types have been renamed following new conventions (e.g., Request bodies are now `{Verb}{Entity}Request`). Consult MIGRATION.md for the full list.

●Issue #3

`FunctionTool.type` changed from `Optional[FunctionToolType]` to `Literal["function"]`.

●Issue #4

The GCP client class name has been changed from `MistralGoogleCloud` to `MistralGCP`.

Migration Steps

  1. 1
    Update all imports from `mistralai.X` to `mistralai.client.X` (e.g., `from mistralai.client import Mistral`).
  2. 2
    Update imports for Azure and GCP clients accordingly (e.g., `from mistralai.azure.client import MistralAzure`).
  3. 3
    Review and update code referencing the 42 renamed types according to the mapping provided in MIGRATION.md.
  4. 4
    Update usage of the GCP client class from `MistralGoogleCloud` to `MistralGCP`.

Release Summary

This technical release introduces a major structural change by adopting a PEP 420 namespace package structure and standardizing type naming conventions. It also improves forward compatibility by allowing enums to accept unknown values.

Need More Details?

View the full release notes and all changes for Mistral Client v2.0.0.

View Full Changelog