Optional
Carrier Issue Updated
Sent when a carrier issue (detention, lumper, TONU, breakdown, damage, shortage, overage, or other incident) is created or updated on a load. Clients must configure a CARRIER_ISSUE_UPDATED webhook subscription to receive these events.
Body·
required
application/json
Common envelope fields shared by v2 webhook events. Each concrete event schema adds its own eventType and typed data payload.
- Type: string | nullcustomer
Load Internal Id requiredYour internal load ID, if provided during load creation
- Type: object ·datarequired
Carrier issue data payload.
- enumevent
Type const:CARRIER_ISSUE_UPDATEDrequiredEvent name for carrier issue updates.
values- C
A R R I E R _ I S S U E _ U P D A T E D
- Type: stringidrequired
Unique event identifier (ULID)
- Type: string | nullload
Number requiredYour load reference number
- Type: string Format: date-timeoccurred
At requiredWhen the underlying activity occurred (ISO 8601)
- Type: string | null enumworkflowrequired
The Augment workflow that produced this event
values- T
R A C K _ A N D _ T R A C E - C
A R R I E R _ S U P P O R T - null
Responses
- 200
Carrier issue update received successfully
Request Example for post/CARRIER_ISSUE_UPDATED
curl /CARRIER_ISSUE_UPDATED \
--request POST \
--header 'Content-Type: application/json' \
--data '{
"id": "01JN3GVAY1T1V8E5VFXY4N2K9X",
"workflow": "CARRIER_SUPPORT",
"occurredAt": "2026-06-16T14:00:00Z",
"loadNumber": "LOAD-12345",
"customerLoadInternalId": "internal-123",
"eventType": "CARRIER_ISSUE_UPDATED",
"data": {
"carrierIssueId": "01JCARRIERISSUERECORD00001",
"issueType": "DETENTION_PICKUP",
"status": "OPEN",
"stopType": "PICKUP",
"stopSequenceNumber": 1,
"amountCents": 15000,
"waitTimeMinutes": 180,
"description": "Carrier reported 3-hour wait at shipper. Appointment was 08:00, arrived 07:45, still not loaded as of 11:00.",
"resolution": null,
"externalId": "TMS-INC-30275"
}
}'
No Body