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 TRACKING_UPDATE, STOP_UPDATE or LOAD_CARRIER_UPDATE. Use this event to capture communication activity that does not map to a specific tracking or carrier update.
Fields present on every v2 webhook event.
- Type: string | nullcustomer
Load Internal Id requiredYour internal load ID, if provided during load creation
- Type: object ·datarequired
Comment data payload.
- enumevent
Type const:SEND_TMS_COMMENTrequiredEvent name for an unstructured communication comment.
values- S
E N D _ T M S _ C O M M E N T
- 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, or
nullwhen 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.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 - P
O D _ C O L L E C T I O N - L
O A D _ B U I L D I N G - C
A R R I E R _ S E L E C T I O N - S
C H E D U L I N G - C
U S T O M E R _ S U P P O R T - null
- 200
Event acknowledged
curl /SEND_TMS_COMMENT \
--request POST \
--header 'Content-Type: application/json' \
--data '{
"id": "",
"workflow": "TRACK_AND_TRACE",
"occurredAt": "",
"loadNumber": "",
"customerLoadInternalId": "",
"eventType": "SEND_TMS_COMMENT",
"data": {
"comment": "Driver Marcus confirmed pickup of load test12345 from Dallas and is en route to Atlanta with ETA of tomorrow 2pm."
}
}'