Workflow activity type changes
TheHOOK_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.
Enum changes
Affected endpoints
GET /v2/telematics/workflows
GET /v2/telematics/workflows
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.GET /v2/telematics/workflows/{workflow_id}
GET /v2/telematics/workflows/{workflow_id}
The
activities field on each stop in the response no longer returns HOOK_DROP. It may now return DROP_TRAILER or HOOK_TRAILER instead.POST /v2/telematics/workflows
POST /v2/telematics/workflows
The
activities field in the request body no longer accepts HOOK_DROP. Use DROP_TRAILER or HOOK_TRAILER instead.PATCH /v2/telematics/workflows/{id}
PATCH /v2/telematics/workflows/{id}
The
activities field in the request body no longer accepts HOOK_DROP. Use DROP_TRAILER or HOOK_TRAILER instead.Migration
Before:HOOK_DROP with the appropriate specific value depending on the intended action:
Migration checklist
1
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.2
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.3
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.4
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.Expanded TMS provider support for TMS loads
This release adds 21 new valid values for thesource_name field across the TMS loads endpoints. The change is additive and backward-compatible.
Backward-compatible addition: All new
source_name enum values are purely additive. No existing integrations are affected.New TMS source names
The followingsource_name values are now valid on TMS load responses:
Affected endpoints
GET /v2/telematics/tms-loads
GET /v2/telematics/tms-loads
The
source_name field in each item of the response may now return any of the 21 new values.GET /v2/telematics/tms-loads/{load_id}
GET /v2/telematics/tms-loads/{load_id}
The
source_name field in the response may now return any of the 21 new values.Need help?
API reference
View complete endpoint documentation for the Telematics API
Contact support
Questions about this release? Our team is here to help