Carrier Support

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.

post/CARRIER_ISSUE_UPDATED

Request

Request body

idstring required

Unique event identifier (ULID)

workflow'TRACK_AND_TRACE' | 'CARRIER_SUPPORT' | 'POD_COLLECTION' | 'LOAD_BUILDING' | 'CARRIER_SELECTION' | 'SCHEDULING' | 'CUSTOMER_SUPPORT' | 'null' nullable required

The Augment workflow that produced this event, or null when no single workflow can be attributed. New values may be added over time, so treat this as an open set rather than a fixed list.

occurredAtstring date-time required

When the underlying activity occurred (ISO 8601)

loadNumberstring nullable required

Your load reference number

customerLoadInternalIdstring nullable required

Your internal load ID, if provided during load creation

eventType'CARRIER_ISSUE_UPDATED' required

Event name for carrier issue updates.

Example request

{
  "data": {
    "carrierIssueId": "01JCARRIERISSUERECORD00001",
    "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.",
    "externalId": "TMS-INC-30275"
  }
}

Response

Carrier issue update received successfully

Changes

No recorded changes to this operation across all 1 revision of this API.