Required

Transit Update

v1 equivalent: trackingEvent (flat payload).

Sent when Augment receives a location or tracking update from a carrier communication. Contains the driver's current position, the next stop ETA, and the source of the tracking data.

Body·
required
application/json

Fields present on every v2 webhook event.

    • customerLoadInternalId
      Type: string | null
      required

      Your internal load ID, if provided during load creation

    • data
      Type: object ·
      required

      Transit update data payload.

    • eventType
      enum
      const:  
      TRACKING_UPDATE
      required

      Event name for a transit update.

      values
      • TRACKING_UPDATE
    • id
      Type: string
      required

      Unique event identifier (ULID)

    • loadNumber
      Type: string | null
      required

      Your load reference number

    • occurredAt
      Type: string Format: date-time
      required

      When the underlying activity occurred (ISO 8601)

    • workflow
      Type: string | null enum
      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.

      values
      • TRACK_AND_TRACE
      • CARRIER_SUPPORT
      • POD_COLLECTION
      • LOAD_BUILDING
      • CARRIER_SELECTION
      • SCHEDULING
      • CUSTOMER_SUPPORT
      • null
Responses
  • 200

    Event acknowledged

Request Example for post/TRACKING_UPDATE
curl /TRACKING_UPDATE \
  --request POST \
  --header 'Content-Type: application/json' \
  --data '{
  "id": "",
  "workflow": "TRACK_AND_TRACE",
  "occurredAt": "",
  "loadNumber": "",
  "customerLoadInternalId": "",
  "eventType": "TRACKING_UPDATE",
  "data": {
    "nextSequence": 1,
    "nextEtaUtc": "",
    "eventType": "PING",
    "eventSource": "PHONE_EMAIL",
    "eventUtc": "",
    "city": "",
    "stateOrProvince": "",
    "latitude": 0,
    "longitude": 0,
    "notes": ""
  }
}'
No Body