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

> 2 changes across webhooks

**Released 3rd August 2026**

## Document resource support

This release extends the `resource` enum across the Integrations API to include `document` as a supported resource type. All endpoints that accept or return a `resource` field now recognise this new value.

<Check>
  **Backward-compatible addition:** Existing integrations are unaffected. The `document` value is purely additive — no existing enum values were removed or renamed.
</Check>

### New enum value: `document`

The `ResourceEnum` schema has been extended with a new value:

| Field | Change |
| - | - |
| `resource` | New value `document` added to the enum |

This change propagates across all endpoints that reference `ResourceEnum`, including request bodies, query parameters, and response payloads.

### Affected endpoints

<AccordionGroup>
  <Accordion title="Schedules" icon="calendar-day">
    The `resource` field in schedule-related endpoints now accepts and returns `document`.

    **Endpoints updated:**

    * `GET /v2/integrations/connections/{connection_id}/schedules` — `resource` query parameter and response items
    * `POST /v2/integrations/connections/{connection_id}/schedules` — `resource` in request body and response
    * `GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}` — `resource` in response
    * `PATCH /v2/integrations/connections/{connection_id}/schedules/{schedule_id}` — `resource` in response
    * `POST /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/activate` — `resource` in response
    * `POST /v2/integrations/connections/{connection_id}/schedules/activate-schedules` — `resource` in response
    * `POST /v2/integrations/connections/schedules/backfill` — `resource` in request body

    **Example — create a schedule for documents:**

    ```bash theme={null}
    POST /v2/integrations/connections/{connection_id}/schedules
    Content-Type: application/json

    {
      "resource": "document",
      "...": "..."
    }
    ```
  </Accordion>

  <Accordion title="Resource operations" icon="list">
    The `resource` field in resource operation endpoints now accepts and returns `document`.

    **Endpoints updated:**

    * `GET /v2/integrations/connections/resource-operations` — `resource` query parameter and response items
    * `GET /v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id}` — `resource` in response

    **Example — filter resource operations by document:**

    ```bash theme={null}
    GET /v2/integrations/connections/resource-operations?resource=document
    ```
  </Accordion>

  <Accordion title="Schedule executions" icon="clock">
    The `resource` field in execution responses now includes `document`.

    **Endpoints updated:**

    * `GET /v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions` — `resource` in response items
  </Accordion>

  <Accordion title="Data freshness" icon="filter">
    The `resource` field in the data freshness response now includes `document`.

    **Endpoints updated:**

    * `GET /v2/integrations/connections/data-freshness` — `resource` in response items
  </Accordion>
</AccordionGroup>

## Webhook Sorting Support

This release adds sorting support to the webhook and webhook log listing endpoints, giving you control over the order in which results are returned.

<Check>
  **Backward-compatible:** All changes in this release are additive. No existing integrations are affected.
</Check>

### New Features

<AccordionGroup>
  <Accordion title="Sort webhooks by field and order" icon="filter">
    `GET /v2/notifications/webhooks` now accepts two new optional query parameters:

    | Parameter | Type | Description |
    | - | - | - |
    | `sort_by` | `WebhookSortField` | The field to sort results by |
    | `sort_order` | `SortOrder` | The sort direction (`asc` or `desc`) |

    **Example:**

    ```bash theme={null}
    GET /v2/notifications/webhooks?sort_by=created_at&sort_order=desc
    ```
  </Accordion>

  <Accordion title="Sort webhook logs by field and order" icon="list">
    `GET /v2/notifications/webhooks/{webhook_id}/logs` now accepts two new optional query parameters:

    | Parameter | Type | Description |
    | - | - | - |
    | `sort_by` | `WebhookLogSortField` | The field to sort log results by |
    | `sort_order` | `SortOrder` | The sort direction (`asc` or `desc`) |

    **Example:**

    ```bash theme={null}
    GET /v2/notifications/webhooks/{webhook_id}/logs?sort_by=created_at&sort_order=asc
    ```
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup cols={2}>
  <Card title="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 this release? Our team is here to help
  </Card>
</CardGroup>


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