> ## 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.72.0 - Workflow Activity Types & Expanded TMS Provider Support

> HOOK_DROP replaced by DROP_TRAILER and HOOK_TRAILER across workflow endpoints, plus 21 new TMS source_name values for TMS loads

**Released 17th September 2026**

<Warning>
  **This release includes a breaking change:** the `HOOK_DROP` activity type has been removed from workflow schemas and replaced by two distinct values: `DROP_TRAILER` and `HOOK_TRAILER`. See [Workflow activity type changes](#workflow-activity-type-changes) below.
</Warning>

## Workflow activity type changes

The `HOOK_DROP` value has been removed from the workflow activity type enum and replaced by two more precise values: `DROP_TRAILER` and `HOOK_TRAILER`. This change affects all endpoints that read or write workflow stop activities.

<Warning>
  **Breaking change:** Any code that sends or checks for `HOOK_DROP` must be updated. The value is no longer accepted in requests and will no longer appear in responses.
</Warning>

### Enum changes

| Removed value | Replacement values |
| - | - |
| `HOOK_DROP` | `DROP_TRAILER`, `HOOK_TRAILER` |

### Affected endpoints

<AccordionGroup>
  <Accordion title="GET /v2/telematics/workflows" icon="list">
    The `activities` field on each stop in the response items no longer returns `HOOK_DROP`. It may now return `DROP_TRAILER` or `HOOK_TRAILER` instead.

    ```bash theme={null}
    GET /v2/telematics/workflows
    ```
  </Accordion>

  <Accordion title="GET /v2/telematics/workflows/{workflow_id}" icon="magnifying-glass">
    The `activities` field on each stop in the response no longer returns `HOOK_DROP`. It may now return `DROP_TRAILER` or `HOOK_TRAILER` instead.

    ```bash theme={null}
    GET /v2/telematics/workflows/{workflow_id}
    ```
  </Accordion>

  <Accordion title="POST /v2/telematics/workflows" icon="plus">
    The `activities` field in the request body no longer accepts `HOOK_DROP`. Use `DROP_TRAILER` or `HOOK_TRAILER` instead.

    ```bash theme={null}
    POST /v2/telematics/workflows
    Content-Type: application/json

    {
      "stops": [
        {
          "activities": ["DROP_TRAILER"]
        }
      ]
    }
    ```
  </Accordion>

  <Accordion title="PATCH /v2/telematics/workflows/{id}" icon="pen">
    The `activities` field in the request body no longer accepts `HOOK_DROP`. Use `DROP_TRAILER` or `HOOK_TRAILER` instead.

    ```bash theme={null}
    PATCH /v2/telematics/workflows/{id}
    Content-Type: application/json

    {
      "stops": [
        {
          "activities": ["HOOK_TRAILER"]
        }
      ]
    }
    ```
  </Accordion>
</AccordionGroup>

### Migration

**Before:**

```json theme={null}
{
  "stops": [
    {
      "activities": ["HOOK_DROP"]
    }
  ]
}
```

**After:**

Replace `HOOK_DROP` with the appropriate specific value depending on the intended action:

```json theme={null}
{
  "stops": [
    {
      "activities": ["DROP_TRAILER"]
    }
  ]
}
```

or

```json theme={null}
{
  "stops": [
    {
      "activities": ["HOOK_TRAILER"]
    }
  ]
}
```

### Migration checklist

<Steps>
  <Step title="Audit activity type usage">
    Search your codebase for any references to `"HOOK_DROP"` in the context of workflow stop activities and replace them with `"DROP_TRAILER"` or `"HOOK_TRAILER"` as appropriate.
  </Step>

  <Step title="Update request payloads">
    If you send `HOOK_DROP` in `POST /v2/telematics/workflows` or `PATCH /v2/telematics/workflows/{id}` request bodies, update those payloads to use the correct replacement value.
  </Step>

  <Step title="Update response handling">
    If you read or store the `activities` field from workflow responses, update your code to handle `DROP_TRAILER` and `HOOK_TRAILER` instead of `HOOK_DROP`.
  </Step>

  <Step title="Update stored enumerations">
    If you store or validate activity type values in a database schema, enum type, or configuration, remove `HOOK_DROP` and add `DROP_TRAILER` and `HOOK_TRAILER`.
  </Step>
</Steps>

***

## Expanded TMS provider support for TMS loads

This release adds 21 new valid values for the `source_name` field across the TMS loads endpoints. The change is additive and backward-compatible.

<Check>
  **Backward-compatible addition:** All new `source_name` enum values are purely additive. No existing integrations are affected.
</Check>

### New TMS source names

The following `source_name` values are now valid on TMS load responses:

| New `source_name` value | Provider |
| - | - |
| `alvys` | Alvys |
| `ascend_tms` | Ascend TMS |
| `axon_software` | Axon Software |
| `blue_yonder` | Blue Yonder |
| `dat` | DAT |
| `descartes_aljex` | Descartes Aljex |
| `freightpop` | FreightPOP |
| `manhattan_associates` | Manhattan Associates |
| `mastery_tms` | Mastery TMS |
| `mcleod` | McLeod Software |
| `mercury_gate` | MercuryGate |
| `oracle_transportation_management` | Oracle Transportation Management |
| `pcs_software` | PCS Software |
| `revenova` | Revenova |
| `rose_rocket` | Rose Rocket |
| `sap_transportation_management` | SAP Transportation Management |
| `tailwind_tms` | Tailwind TMS |
| `tai_tms` | TAI TMS |
| `transport_pro` | Transport Pro |
| `trimble_transportation` | Trimble Transportation |
| `turvo` | Turvo |

### Affected endpoints

<AccordionGroup>
  <Accordion title="GET /v2/telematics/tms-loads" icon="list">
    The `source_name` field in each item of the response may now return any of the 21 new values.

    ```bash theme={null}
    GET /v2/telematics/tms-loads
    ```
  </Accordion>

  <Accordion title="GET /v2/telematics/tms-loads/{load_id}" icon="magnifying-glass">
    The `source_name` field in the response may now return any of the 21 new values.

    ```bash theme={null}
    GET /v2/telematics/tms-loads/{load_id}
    ```
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup cols={2}>
  <Card title="API reference" icon="book" href="/api-reference/telematics-api">
    View complete endpoint documentation for the Telematics 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.