Webhook

Carrier Issue Updated

​

v2 equivalent: CARRIER_ISSUE_UPDATED (uses shared event envelope).

Augment POSTs this payload to your configured carrier-issue endpoint 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

A standardized carrier issue notification. Sent when the carrier-support agent creates or updates an issue (detention, lumper, TONU, breakdown, damage, shortage, overage, or other incident) on a load. Flat equivalent of the v2 CARRIER_ISSUE_UPDATED envelope — the same fields are sent at the top level rather than nested under data.

  • carrierIssueId
    Type: string | null
    required

    Correlation token for this carrier issue (Augment's internal incident record id). Echo it back on the callback to update the same incident in place. Null if not yet available.

  • description
    Type: string
    required

    Full narrative description of the issue.

  • issueType
    Type: stringenum
    required

    The category of carrier issue.

    values
    DETENTION_PICKUPDETENTION_DELIVERYLUMPERTONULAYOVERBREAKDOWNDAMAGESHORTAGEOVERAGEOTHER
  • loadNumber
    Type: string
    required

    The unique identifier for the load

  • status
    Type: "OPEN" or "RESOLVED" or "CANCELED"enum
    required

    Current lifecycle status of the issue.

  • amountCents
    Type: integer | null

    Monetary claim amount in USD cents (e.g. lumper fee, detention charge).

  • brokerageLoadInternalId
    Type: string | null

    Optional internal load ID in the TMS. Use loadNumber as the main ID. Will be null if not provided.

  • externalId
    Type: string

    The incident id in your TMS, once you have reported it back via the callback. When present, treat this event as an update to that existing incident rather than a new one.

  • resolution
    Type: string | null

    How the issue was resolved. Populated when status is RESOLVED.

  • stopSequenceNumber
    Type: integer | null

    1-indexed position of the affected stop on the route.

  • stopType
    Type: "PICKUP" or "DELIVERY" or nullenum

    Which stop type is affected, if applicable.

  • waitTimeMinutes
    Type: integer | null

    Wait or detention duration in minutes.

Responses

  • 200

    Carrier issue update received successfully

Request Example for postcarrierIssueUpdated
{
  "loadNumber": "",
  "brokerageLoadInternalId": null,
  "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

Carrier issue update received successfully

Previous
Scheduled Carrier Outreach
Next
Bid Created