> ## 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.35.0

> 3 changes across webhooks, safety and fleet

**Released 7th August 2026**

## Document Webhook Events

This release expands the webhook notification system with support for document lifecycle events, enabling integrations to react to document additions, modifications, and any document-related activity.

<Check>
  **Backward-compatible addition:** All new event types are additive. Existing webhook subscriptions and integrations are unaffected.
</Check>

### New webhook event types

<AccordionGroup>
  <Accordion title="Document events" icon="file">
    Three new values have been added to the `WebhookEventNameEnum`, available across all webhook endpoints:

    | Event name | Description |
    | - | - |
    | `document.added` | Fires when a new document is added |
    | `document.modified` | Fires when an existing document is modified |
    | `document.*` | Wildcard — fires on any document event |

    You can now subscribe to document events when creating or updating a webhook:

    ```bash theme={null}
    # Subscribe to all document events using the wildcard
    POST /v2/notifications/webhooks
    Content-Type: application/json

    {
      "event_name": "document.*",
      "url": "https://your-endpoint.example.com/webhook"
    }
    ```

    ```bash theme={null}
    # Subscribe to document additions only
    POST /v2/notifications/webhooks
    Content-Type: application/json

    {
      "event_name": "document.added",
      "url": "https://your-endpoint.example.com/webhook"
    }
    ```

    You can also filter existing webhooks by the new event types:

    ```bash theme={null}
    GET /v2/notifications/webhooks?event_name=document.added
    GET /v2/notifications/webhooks?event_name=document.modified
    GET /v2/notifications/webhooks?event_name=document.*
    ```
  </Accordion>
</AccordionGroup>

### Affected endpoints

The new event types are available on all webhook management endpoints:

* `GET /v2/notifications/webhooks` — filter by new event names
* `POST /v2/notifications/webhooks` — subscribe to new event names
* `GET /v2/notifications/webhooks/{webhook_id}` — response includes new enum values
* `PATCH /v2/notifications/webhooks/{webhook_id}` — update subscription to new event names
* `POST /v2/notifications/webhooks/{webhook_id}/activate` — response includes new enum values
* `POST /v2/notifications/webhooks/{webhook_id}/pause` — response includes new enum values
* `GET /v2/notifications/webhooks/{webhook_id}/logs` — log entries include new event names

## Driver Safety Event URLs

This release adds a new `urls` field to driver safety event schemas, giving you direct access to associated media and resource links within safety event payloads.

<Check>
  **Backward-Compatible Addition:** All existing integrations continue to work without changes. The new `urls` field is additive and optional.
</Check>

### Schema Changes

<AccordionGroup>
  <Accordion title="Driver safety event schemas" icon="shield-check">
    A new `urls` property has been added to the following schemas:

    * `BaseDriverSafetyEvent`
    * `DriverSafetyEventAdded`
    * `DriverSafetyEventModified`

    The `urls` field provides a list of URLs associated with the safety event — for example, links to video clips, images, or other media captured during the event.

    **Example response (new field highlighted):**

    ```json theme={null}
    {
      "event_type": "driver_safety_event.added",
      "data": [
        {
          "id": "evt_123",
          "driver_id": "drv_456",
          "event_time": "2026-08-07T10:00:00Z",
          "severity": "high",
          "urls": [
            "https://media.example.com/safety/clip_001.mp4",
            "https://media.example.com/safety/thumb_001.jpg"
          ]
        }
      ]
    }
    ```
  </Accordion>
</AccordionGroup>

### Affected webhook events

| Schema | Change |
| - | - |
| `BaseDriverSafetyEvent` | New `urls` property added |
| `DriverSafetyEventAdded` | New `urls` property added to items in `data` array |
| `DriverSafetyEventModified` | New `urls` property added to items in `data` array |

## Driver Safety Event Webhooks

This release adds webhook support for driver safety events, enabling real-time notifications when safety events are created, updated, or removed in the Catena platform.

<Check>
  **New Feature:** Three new webhook event types cover the full lifecycle of driver safety events — added, modified, and removed — along with a catch-all wildcard subscription.
</Check>

### New webhook events

<AccordionGroup>
  <Accordion title="driver_safety_event.added" icon="circle-plus">
    Emitted when a new driver safety event is added to the database — for example, when a record fetched from the TSP is new and generates a new entry in Catena.

    **Event name:** `driver_safety_event.added`

    **Payload schema:** `DriverSafetyEventAdded`

    ```bash theme={null}
    # Subscribe to driver safety event additions
    POST /v2/notifications/webhooks
    {
      "url": "https://your-endpoint.example.com/webhooks",
      "event_name": "driver_safety_event.added"
    }
    ```
  </Accordion>

  <Accordion title="driver_safety_event.modified" icon="pen-to-square">
    Emitted when a driver safety event is modified in the database — for example, when a record fetched from the TSP differs from what was previously stored and prompts an update.

    **Event name:** `driver_safety_event.modified`

    **Payload schema:** `DriverSafetyEventModified`

    ```bash theme={null}
    # Subscribe to driver safety event modifications
    POST /v2/notifications/webhooks
    {
      "url": "https://your-endpoint.example.com/webhooks",
      "event_name": "driver_safety_event.modified"
    }
    ```
  </Accordion>

  <Accordion title="driver_safety_event.removed" icon="circle-minus">
    Emitted when a driver safety event is removed from the database — for example, when a record is deleted from the TSP and removed from Catena.

    **Event name:** `driver_safety_event.removed`

    **Payload schema:** `DriverSafetyEventRemoved`

    ```bash theme={null}
    # Subscribe to driver safety event removals
    POST /v2/notifications/webhooks
    {
      "url": "https://your-endpoint.example.com/webhooks",
      "event_name": "driver_safety_event.removed"
    }
    ```
  </Accordion>

  <Accordion title="driver_safety_event.* (catch-all)" icon="asterisk">
    Subscribe to all driver safety event lifecycle events with a single wildcard subscription.

    **Event name:** `driver_safety_event.*`

    ```bash theme={null}
    # Subscribe to all driver safety events
    POST /v2/notifications/webhooks
    {
      "url": "https://your-endpoint.example.com/webhooks",
      "event_name": "driver_safety_event.*"
    }
    ```
  </Accordion>
</AccordionGroup>

### Updated endpoints

The `event_name` field across all webhook endpoints now accepts the new `driver_safety_event.*` values. No changes are required to existing webhook subscriptions — this is a purely additive update.

| Endpoint | Change |
| - | - |
| `GET /v2/notifications/webhooks` | `event_name` filter accepts new values |
| `POST /v2/notifications/webhooks` | `event_name` field accepts new values |
| `GET /v2/notifications/webhooks/{webhook_id}` | Response `event_name` includes new values |
| `PATCH /v2/notifications/webhooks/{webhook_id}` | `event_name` field accepts new values |
| `POST /v2/notifications/webhooks/{webhook_id}/activate` | Response `event_name` includes new values |
| `POST /v2/notifications/webhooks/{webhook_id}/pause` | Response `event_name` includes new values |
| `GET /v2/notifications/webhooks/{webhook_id}/logs` | Response `event_name` includes new values |

***

## Need help?

<CardGroup cols={2}>
  <Card title="Webhook documentation" icon="book" href="/api-reference/webhooks/overview">
    Learn how to set up and manage webhooks with the Catena Notifications API
  </Card>

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


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