Optional
New Email
v1 equivalent: none. v2 only.
Sent when an inbound email relating to one of your loads is received by an Augment agent. participants and subject identify the email, while summary and classification describe what it was about.
Body·
required
application/json
Fields present on every v2 webhook event.
- Type: string | nullcustomer
Load Internal Id requiredYour internal load ID, if provided during load creation
- Type:datarequiredProperties: 6
Email data payload.
- enumevent
Type const:NEW_EMAILrequiredEvent name for a received email.
- Type: stringidrequired
Unique event identifier (ULID)
- Type: string | nullload
Number requiredYour load reference number
- Type: stringFormat: date-timeoccurred
At requiredWhen the underlying activity occurred (ISO 8601)
- Type: string | nullenumworkflowrequired
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.valuesTRACK_AND_TRACECARRIER_SUPPORTPOD_COLLECTIONLOAD_BUILDINGCARRIER_SELECTIONSCHEDULINGCUSTOMER_SUPPORTnull
Responses
- 200
Event acknowledged
Request Example for post/NEW_EMAIL
curl /NEW_EMAIL \
--request POST \
--header 'Content-Type: application/json' \
--data '{
"id": "evt_01HZXK9P7QM3N8YV4TBWJC2RDH",
"workflow": "TRACK_AND_TRACE",
"occurredAt": "2026-05-13T12:34:56Z",
"loadNumber": "LOAD-456",
"customerLoadInternalId": "INT-789",
"eventType": "NEW_EMAIL",
"data": {
"direction": "INBOUND",
"attachmentCount": 1,
"participants": {
"from": {
"name": "Jane Dispatcher",
"address": "dispatch@carrier.com"
},
"to": [
{
"name": "Augment",
"address": "loads@augment.example"
}
],
"cc": []
},
"subject": "RE: LOAD-456 delivery update",
"summary": "Carrier reports delivery completed at 14:05.",
"classification": "DELIVERY_UPDATE"
}
}'
No Body