Human Assistance Requested
v1 equivalent: none. v2 only.
Sent when an Augment agent hands a load off to a human. contact is the person at your brokerage the agent routed the request to, so you can surface the handoff to the right queue or rep.
reasonCode says why the agent could not continue on its own.
Body·
Fields present on every v2 webhook event.
- Type: string | nullcustomer
Load Internal Id requiredYour internal load ID, if provided during load creation
- Type:datarequiredProperties: 2
Human assistance request data payload.
- enumevent
Type const:HUMAN_ASSISTANCE_REQUESTEDrequiredEvent name for a human-assistance request.
- 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
curl /HUMAN_ASSISTANCE_REQUESTED \
--request POST \
--header 'Content-Type: application/json' \
--data '{
"id": "evt_01HZXK9P7QM3N8YV4TBWJC2RDQ",
"workflow": "TRACK_AND_TRACE",
"occurredAt": "2026-05-13T12:34:56Z",
"loadNumber": "LOAD-456",
"customerLoadInternalId": "INT-789",
"eventType": "HUMAN_ASSISTANCE_REQUESTED",
"data": {
"reasonCode": "INSUFFICIENT_INFORMATION",
"contact": {
"name": "Sam Rep",
"externalId": "REP-123",
"email": "sam@brokerage.example",
"phone": "+15559876543",
"phoneExtension": null
}
}
}'