Optional

Comment

​

v1 equivalent: comment (flat payload).

Sent when Augment sends or receives a carrier communication (email, phone, or text) that does not produce a distinct structured event like TRANSIT_UPDATE, STOP_UPDATE or CARRIER_INFO_UPDATE. Use this event to capture communication activity that does not map to a specific tracking or carrier update.

Body·
required
application/json

  • Common envelope shared by Track & Trace webhook events. Use eventType to determine how to interpret the data field.

    • brokerageLoadInternalId
      Type: string | null
      required

      Your internal load ID, if provided during load creation

    • data
      required
    • eventType
      Type: stringenum
      required

      Determines the shape of data

      values
      • TRANSIT_UPDATE
      • STOP_UPDATE
      • CARRIER_INFO_UPDATE
      • COMMENT
      • SCHEDULED_CARRIER_OUTREACH
    • id
      Type: string
      required

      Unique event identifier (ULID)

    • loadNumber
      Type: string | null
      required

      Your load reference number

    • occurredAt
      Type: stringFormat: date-time
      required

      When the underlying activity occurred (ISO 8601)

    • workflow
      Type: string | nullenum
      required

      The Augment workflow that produced this event

      values
      • TRACK_AND_TRACE
      • null
Responses
  • 200

    Event acknowledged

Request Example for post/COMMENT
curl /COMMENT \
  --request POST \
  --header 'Content-Type: application/json' \
  --data '{
  "id": "",
  "workflow": "TRACK_AND_TRACE",
  "occurredAt": "",
  "loadNumber": "",
  "brokerageLoadInternalId": "",
  "eventType": "COMMENT",
  "data": {
    "comment": "Driver Marcus confirmed pickup of load test12345 from Dallas and is en route to Atlanta with ETA of tomorrow 2pm."
  }
}'
No Body

Event acknowledged