---
title: "Carrier Issue Updated"
method: POST
path: "/CARRIER_ISSUE_UPDATED"
tags: ["Carrier Support"]
---

# Carrier Issue Updated

`POST /CARRIER_ISSUE_UPDATED`

## Request

- Base URL: `https://apidocs.goaugment.com` (the document declares no server; this is the origin it was published from)
- URL: `https://apidocs.goaugment.com/CARRIER_ISSUE_UPDATED`
- Auth: none declared
- TypeScript: <https://skmtc.dev/goaugment/apis/webhooks/docs/CARRIER_ISSUE_UPDATED/post.ts> (a function with typed inputs; its response is checked against the schema)

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.

## Request body

- CarrierIssueUpdatedEvent: Fields present on every v2 webhook event.
  - `id` string, 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.
  - `occurredAt` string, date-time, required: When the underlying activity occurred (ISO 8601)
  - `loadNumber` string, nullable, required: Your load reference number
  - `customerLoadInternalId` string, nullable, required: Your internal load ID, if provided during load creation
  - `eventType` 'CARRIER_ISSUE_UPDATED', required: Event name for carrier issue updates.
  - `data` CarrierIssueUpdatedData, required: 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.
    - `carrierIssueId` string, nullable, 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.
    - `issueType` 'DETENTION_PICKUP' | 'DETENTION_DELIVERY' | 'LUMPER' | 'TONU' | 'LAYOVER' | 'BREAKDOWN' | 'DAMAGE' | 'SHORTAGE' | 'OVERAGE' | 'OTHER', required: The category of carrier issue.
    - `status` 'OPEN' | 'RESOLVED' | 'CANCELED', required: Current lifecycle status of the issue.
    - `stopType` 'PICKUP' | 'DELIVERY' | 'null', nullable: Which stop type is affected, if applicable.
    - `stopSequenceNumber` integer, nullable: 1-indexed position of the affected stop on the route.
    - `amountCents` integer, nullable: Monetary claim amount in USD cents (e.g. lumper fee, detention charge).
    - `waitTimeMinutes` integer, nullable: Wait or detention duration in minutes.
    - `description` string, required: Full narrative description of the issue.
    - `resolution` string, nullable: How the issue was resolved. Populated when status is RESOLVED.
    - `externalId` 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.

## Response `200`

Carrier issue update received successfully

---

[API](https://skmtc.dev/goaugment/apis/webhooks.md) - [All operations](https://skmtc.dev/goaugment/apis/webhooks/llms.txt) - [OpenAPI document](https://skmtc.dev/goaugment/apis/webhooks/revisions/a074b2ada419?raw)