> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catenatelematics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# v2.25.0 - Michelin Connected Fleet Support

> Michelin Connected Fleet added as a supported telematics service provider across the Integrations API

**Released 16th July 2026**

## Michelin Connected Fleet Support

This release adds Michelin Connected Fleet as a supported telematics service provider (TSP) in the Integrations API. The `michelin_connected_fleet` value is now a valid option for the `source_name` field across all integration endpoints.

<Check>
  **Backward-compatible addition:** All existing integrations continue to work without any changes. This release only adds new enum support.
</Check>

### New TSP support

<AccordionGroup>
  <Accordion title="Michelin Connected Fleet" icon="sparkles">
    `michelin_connected_fleet` is now a valid `source_name` value across all Integrations API endpoints. You can create connections, manage schedules, and retrieve execution history for Michelin Connected Fleet the same way you would for any other supported TSP.

    **Affected endpoints:**

    | Endpoint | Change |
    | - | - |
    | `GET /v2/integrations/connections` | `source_name` response field now includes `michelin_connected_fleet` |
    | `POST /v2/integrations/connections` | `source_name` response field now includes `michelin_connected_fleet` |
    | `GET /v2/integrations/connections/{connection_id}` | `source_name` response field now includes `michelin_connected_fleet` |
    | `PATCH /v2/integrations/connections/{connection_id}` | `source_name` response field now includes `michelin_connected_fleet` |
    | `GET /v2/integrations/connections/{connection_id}/schedules` | Schedules for Michelin Connected Fleet connections are now returned |
    | `GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions` | `source_name` response field now includes `michelin_connected_fleet` |
    | `GET /v2/integrations/connections/resource-operations` | `source_name` filter and response field now include `michelin_connected_fleet` |
    | `GET /v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id}` | `source_name` response field now includes `michelin_connected_fleet` |
    | `GET /v2/integrations/tsps` | `source_name` response field now includes `michelin_connected_fleet` |
    | `GET /v2/integrations/tsps/{tsp_id}` | `source_name` response field now includes `michelin_connected_fleet` |

    **Example — filtering resource operations by Michelin Connected Fleet:**

    ```bash theme={null}
    GET /v2/integrations/connections/resource-operations?source_name=michelin_connected_fleet
    ```

    **Example — listing TSPs and finding Michelin Connected Fleet:**

    ```bash theme={null}
    GET /v2/integrations/tsps
    ```

    ```json theme={null}
    {
      "items": [
        {
          "tsp_id": "tsp_michelin_connected_fleet",
          "source_name": "michelin_connected_fleet",
          ...
        }
      ]
    }
    ```
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup cols={2}>
  <Card title="Integrations API reference" icon="book" href="/api-reference/integrations-api">
    View complete endpoint documentation for the Integrations API
  </Card>

  <Card title="Contact support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about your integration? Our team is here to help
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.