Track & Trace

Stop Update

v1 equivalent: stopUpdate (flat payload).

Sent when a stop's status changes. For example, when a driver arrives at a pickup, departs a facility, or a delivery is completed. Contains the stop sequence, updated status, timing information, and the stop's address when it is known.

post/STOP_UPDATE

Request

Request body

idstring required

Unique event identifier (ULID)

workflow'TRACK_AND_TRACE' | 'CARRIER_SUPPORT' | 'POD_COLLECTION' | 'LOAD_BUILDING' | 'CARRIER_SELECTION' | 'SCHEDULING' | 'CUSTOMER_SUPPORT' | 'null' nullable required

The Augment workflow that produced this event, or null when 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.

occurredAtstring date-time required

When the underlying activity occurred (ISO 8601)

loadNumberstring nullable required

Your load reference number

customerLoadInternalIdstring nullable required

Your internal load ID, if provided during load creation

eventType'STOP_UPDATE' required

Event name for a stop status update.

Example request

{
  "data": {
    "stopSequenceNumber": 1,
    "arrivalTime": "2025-08-21T12:34:56Z",
    "departureTime": "2025-08-21T12:34:56Z",
    "unloadStartTime": "2025-08-21T12:34:56Z",
    "unloadEta": "2025-08-21T12:34:56Z",
    "timezone": "America/Chicago",
    "accessorials": [
      "AFTER_HOURS"
    ],
    "address": {
      "country": "US"
    }
  }
}

Response

Event acknowledged

Changes

No recorded changes to this operation across all 1 revision of this API.