ShipmentLocationUpdateUrl

Fires when a new GPS/location update is received for a shipment.

Triggers

  • Public API POST /PublicApi/Location/v2/ShipmentLocations
  • Driver-tracking provider callbacks (MacroPoint, TruckerTools, FourKites, Project44, FarEye, OpenTrack)

Delivery

Batched with a ~1-minute delay after the triggering event.

Throttle

Fires at most once every 15 minutes per shipment. Additional location pings within the 15-minute window are silently dropped from the webhook (the underlying location data is still stored in the TMS).

Notes

  • 15-min throttle is tracked via ShipmentActionLog (ShipmentActionType = ShipmentLocationUpdate).
  • The underlying GPS ping is always persisted in the TMS regardless of whether the webhook fires — the throttle only affects webhook delivery.

Payload — LocationShipmentDetails

Trimmed view focused purely on location. Does not include stops, commodities, or financials.

FieldTypeNullableDescription
shipmentIdintegerNoUnique shipment identifier.
statusstring (enum)NoCurrent shipment status.
latitudenumberYesCurrent GPS latitude.
longitudenumberYesCurrent GPS longitude.
locationStringstringYesHuman-readable location description.
lastLocationUpdatestring (datetime)YesUTC timestamp of this location ping.

Example

{
  "shipmentId": 128340192,
  "status": "In Transit",
  "latitude": 39.7684,
  "longitude": -86.1581,
  "locationString": "Indianapolis, IN, US",
  "lastLocationUpdate": "2026-07-10T18:42:00Z"
}

Did this page help you?