Optional
New Rep Email
v1 equivalent: none. v2 only.
Sent when an inbound email from one of your own reps is received by an Augment agent. Same payload as NEW_EMAIL; the separate event type lets you distinguish correspondence with your team from correspondence with carriers.
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_REP_EMAILrequiredEvent name for a received email from one of your reps.
- 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_REP_EMAIL
curl /NEW_REP_EMAIL \
--request POST \
--header 'Content-Type: application/json' \
--data '{
"id": "evt_01HZXK9P7QM3N8YV4TBWJC2RDJ",
"workflow": "TRACK_AND_TRACE",
"occurredAt": "2026-05-13T12:34:56Z",
"loadNumber": "LOAD-456",
"customerLoadInternalId": "INT-789",
"eventType": "NEW_REP_EMAIL",
"data": {
"direction": "INBOUND",
"attachmentCount": 0,
"participants": {
"from": {
"name": "Sam Rep",
"address": "sam@brokerage.example"
},
"to": [
{
"name": "Augment",
"address": "loads@augment.example"
}
],
"cc": []
},
"subject": "RE: LOAD-456 — please stop tracking",
"summary": "Rep asks the agent to pause outreach on this load.",
"classification": "GENERAL_INQUIRY"
}
}'
No Body