> ## 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.5.0 - Fleet Connection Webhook Events

> New webhook event types for fleet connection lifecycle tracking

**Released 21st January 2026**

This minor release introduces new webhook event types for tracking fleet connection lifecycle events, enabling you to monitor when fleet-level connections are established in your integration.

<Check>
  **Minor Release:** This release adds new webhook event types without breaking existing functionality. All changes are backward-compatible additions.
</Check>

## New Webhook Events

<AccordionGroup>
  <Accordion title="Fleet Connection Events" icon="link">
    **Added:**

    * `fleet_connection.created` - Triggered when a new fleet connection is established
    * `fleet_connection.*` - Wildcard pattern for subscribing to all fleet connection events

    **Use Cases:**

    * Monitor fleet-level data ingestion setup
    * Track when new fleet connections become active
    * Automate workflows based on fleet connection lifecycle

    **Example Webhook Subscription:**

    ```json theme={null}
    {
      "url": "https://your-app.com/webhooks",
      "events": ["fleet_connection.created"],
      "enabled": true
    }
    ```

    **Example Event Payload:**

    ```json theme={null}
    {
      "event": "fleet_connection.created",
      "data": {
        "id": "fc_abc123",
        "fleet_id": "fleet_xyz789",
        "status": "active",
        "created_at": "2026-01-21T10:30:00Z"
      }
    }
    ```
  </Accordion>
</AccordionGroup>

## Documentation Improvements

<AccordionGroup>
  <Accordion title="Connection Schema Clarification" icon="book">
    Enhanced the `ConnectionCreated` event description to clarify that connections represent data ingestion from Telematics Service Providers (TSPs).

    **Updated Description:**

    > "Connection created event. A connection is how we ingest data from a TSP."

    This clarification helps developers better understand the role of connections in the Catena data pipeline.
  </Accordion>
</AccordionGroup>

## Migration Guide

<Steps>
  <Step title="Review Fleet Connection Events">
    If your integration monitors connection lifecycle events, consider subscribing to the new `fleet_connection.*` events for fleet-level visibility.
  </Step>

  <Step title="Update Webhook Subscriptions (Optional)">
    Add fleet connection events to your webhook configuration if you need fleet-level connection tracking:

    ```bash theme={null}
    POST /v2/webhooks
    {
      "url": "https://your-app.com/webhooks",
      "events": [
        "connection.*",
        "fleet_connection.*"
      ]
    }
    ```
  </Step>

  <Step title="Test Event Handling">
    Ensure your webhook handler can process the new event types, or safely ignore them if not needed.
  </Step>
</Steps>

<Tip>
  **No Action Required:** Existing integrations continue to work without changes. The new event types are purely additive.
</Tip>

***

## Need Help?

<CardGroup cols={2}>
  <Card title="API Reference" icon="book" href="/api-reference/telematics-api">
    View complete endpoint documentation with current API structure
  </Card>

  <Card title="Contact Support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about migrating 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.