Canceled Scheduled Outreach
v1 equivalent: none. v2 only.
Sent when a carrier outreach that Augment had scheduled is canceled before it ran. The data payload describes the outreach that was canceled and is the same shape as SCHEDULED_CARRIER_OUTREACH, so you can match it against the outreach you recorded earlier. occurredAt is when the cancellation happened; scheduledAt is when the outreach would have run.
Sent only for outreach directed at a contact — a call, email, or text that will now not happen.
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: 3
The outreach that was canceled. Same shape as
SCHEDULED_CARRIER_OUTREACH. - enumevent
Type const:CANCELED_SCHEDULED_OUTREACHrequiredEvent name for a canceled scheduled carrier outreach.
- 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
curl /CANCELED_SCHEDULED_OUTREACH \
--request POST \
--header 'Content-Type: application/json' \
--data '{
"id": "evt_01HZXK9P7QM3N8YV4TBWJC2RDR",
"workflow": "TRACK_AND_TRACE",
"occurredAt": "2026-05-13T12:34:56Z",
"loadNumber": "LOAD-456",
"customerLoadInternalId": "INT-789",
"eventType": "CANCELED_SCHEDULED_OUTREACH",
"data": {
"scheduledAt": "2026-05-14T08:00:00Z",
"outreachType": "PHONE_CALL",
"context": "Follow up on delivery ETA"
}
}'