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

> 2 changes across schema

**Released 23rd July 2026**

## Fuel Card Resource Support

This release extends the `ResourceEnum` across the Integrations API to include `fuel_card` as a supported resource type. All endpoints that accept or return a `resource` field now support fuel card data synchronization.

<Check>
  **Backward-compatible addition:** Existing integrations are unaffected. The `fuel_card` value is purely additive to the existing resource enum.
</Check>

### New resource type

<AccordionGroup>
  <Accordion title="fuel_card added to ResourceEnum" icon="sparkles">
    The `fuel_card` value is now a valid option for the `resource` field across all Integrations API endpoints. This enables scheduling, monitoring, and backfilling of fuel card data from connected TSP providers.

    **Affected endpoints:**

    | Method | Endpoint |
    | - | - |
    | `GET` | `/v2/integrations/connections/{connection_id}/resource-operations/{resource_operation_id}` |
    | `GET` | `/v2/integrations/connections/{connection_id}/schedules` |
    | `POST` | `/v2/integrations/connections/{connection_id}/schedules` |
    | `GET` | `/v2/integrations/connections/{connection_id}/schedules/{schedule_id}` |
    | `PATCH` | `/v2/integrations/connections/{connection_id}/schedules/{schedule_id}` |
    | `POST` | `/v2/integrations/connections/{connection_id}/schedules/{schedule_id}/activate` |
    | `GET` | `/v2/integrations/connections/{connection_id}/schedules/{schedule_id}/executions` |
    | `POST` | `/v2/integrations/connections/{connection_id}/schedules/activate-schedules` |
    | `GET` | `/v2/integrations/connections/data-freshness` |
    | `GET` | `/v2/integrations/connections/resource-operations` |
    | `POST` | `/v2/integrations/connections/schedules/backfill` |

    **Example — create a fuel card sync schedule:**

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

    {
      "resource": "fuel_card",
      "cron": "0 * * * *"
    }
    ```

    **Example — filter resource operations by fuel card:**

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

    **Example — check data freshness for fuel card:**

    ```bash theme={null}
    GET /v2/integrations/connections/data-freshness
    ```

    The response will now include entries where `resource` is `"fuel_card"`.
  </Accordion>
</AccordionGroup>

## Fuel Card Webhook Support

This release extends webhook event support to include fuel card as a resource type, enabling real-time notifications for fuel card operations across your fleet.

<Check>
  **Backward-Compatible:** All existing webhook subscriptions and integrations continue to work without any changes.
</Check>

### New Resource Type

<AccordionGroup>
  <Accordion title="Fuel card added to ResourceEnum" icon="sparkles">
    The `fuel_card` value has been added to the `ResourceEnum` schema and is now supported across all webhook event types. You can subscribe to fuel card events using the same event patterns as other resource types.

    **Affected event schemas:**

    * `BaseExecutionEvent`
    * `BaseResourceOperationEvent`
    * `BaseScheduleEvent`
    * `ExecutionFailed`
    * `ExecutionStaled`
    * `ResourceOperationCreated`
    * `ResourceOperationFailed`
    * `ResourceOperationSucceeded`
    * `ScheduleDeactivated`

    **Example — subscribe to fuel card operation events:**

    ```bash theme={null}
    curl -X POST https://api.catenatelematics.com/v2/notifications/webhooks \
      -H 'Authorization: Bearer <token>' \
      -H 'Content-Type: application/json' \
      -d '{
        "url": "https://your-endpoint.example.com/webhooks",
        "events": ["fuel_card.*"]
      }'
    ```

    **Example — fuel card resource operation event payload:**

    ```json theme={null}
    {
      "event": "fuel_card.created",
      "resource": "fuel_card",
      "data": [
        {
          "resource": "fuel_card",
          "operation": "created"
        }
      ]
    }
    ```
  </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 integrating fuel card data? Our team is here to help
  </Card>
</CardGroup>


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