Load Update Endpoint

Updated today

Store each load update as a check call, call-in or tracking note on the movement named in native_system_load_leg_id. We send one for every check call a tracker saves, every update approved from a driver or carrier message, and every note TrackFlo writes to record an action on the load, such as a driver's text reply.

Suggested path: POST /trackflo/load-updates. Authentication, the shared fields, responses and retries are in Build Write-Back Endpoints for TrackFlo.

Fields

Every request carries the shared fields plus these. event_type is load_update.

Field	Type	Description
`load_update_utc_timestamp`	string	When the update happened. Earlier than `entered_at_utc` when a tracker logs a call after the fact. Always present.
`load_update_local_timestamp`	string or null	The same time, local to the update's location.
`load_update_iana_timezone`	string or null	The timezone of `load_update_local_timestamp`, for example `America/Chicago`.
`load_update_type`	string	What kind of update this is. See Update types below.
`load_update_information_source`	string	Where the information came from. See Information sources below.
`comment`	string	What the tracker wrote, or the note TrackFlo recorded. Plain text, up to 1,000 characters. Always present.
`comment_formatted`	string	One line combining the comment, location, ETA, temperature and times, ending in `(via TrackFlo)`. Use it if your TMS keeps check calls as a single notes field. Up to 2,000 characters.
`city`	string or null	The truck's city at `load_update_utc_timestamp`.
`state`	string or null	Two-letter state or province code.
`latitude`	number or null	Decimal degrees.
`longitude`	number or null	Decimal degrees.
`eta_utc`	string or null	The ETA to the stop in `eta_native_system_stop_id`.
`eta_local`	string or null	The same ETA, local to that stop.
`eta_native_system_stop_id`	string or null	Your id for the stop the ETA is for. Null when there's no ETA.
`miles_to_next_stop`	number or null	Driving miles from the location to the next stop.
`temperature_fahrenheit`	number or null	The reefer temperature the driver or carrier reported.
`load_empty`	boolean	`true` when the driver reported the truck empty and ready before pickup.

A load update with no location is still a valid update: a tracker's note that the carrier didn't answer has a comment and nothing else. Store it the same way.

Example

{
  "event_id": "6f1d2c0e-8a43-4f0b-9a57-2b8d3e1c4f90",
  "event_type": "load_update",
  "native_system_load_id": "1089520",
  "native_system_load_leg_id": "2330158",
  "entered_by_name": "Jordan Ellis",
  "entered_by_email": "[email protected]",
  "entered_by_tms_user_id": "JELLIS",
  "entered_at_utc": "2026-10-24T15:42:10Z",
  "trackflo_load_url": "https://app.trackflo.tech/public_load_details/4b6e…",
  "load_update_utc_timestamp": "2026-10-24T15:37:00Z",
  "load_update_local_timestamp": "2026-10-24T10:37:00",
  "load_update_iana_timezone": "America/Chicago",
  "load_update_type": "Check Call with Location",
  "load_update_information_source": "Phone Call with Driver",
  "comment": "Driver rolling, no issues. Fuel stop in Joplin.",
  "comment_formatted": "Check Call with Location - Driver rolling, no issues. Fuel stop in Joplin., Data Source: Phone Call with Driver, Location: Springfield, MO, Miles to stop: 412, ETA to next stop: 10/25/2026 06:30 CDT (via TrackFlo)",
  "city": "Springfield",
  "state": "MO",
  "latitude": 37.2089,
  "longitude": -93.2923,
  "eta_utc": "2026-10-25T11:30:00Z",
  "eta_local": "2026-10-25T06:30:00",
  "eta_native_system_stop_id": "88214",
  "miles_to_next_stop": 412,
  "temperature_fahrenheit": null,
  "load_empty": false
}

Respond with your record's id:

{ "id": "callin-99812" }

Update types

We agree the list with you during onboarding, so load_update_type uses the names your team already knows. If you don't have one, we send these:

Check Call with Location
Check Call without Location
ETA Confirmation
Load is Late Update
Problem
Detention Warning
No Response
Note, for a note TrackFlo records about an action on the load rather than a tracker's check call

Information sources

load_update_information_source is one of:

Phone Call with Driver, Text Message with Driver, WhatsApp with Driver, Phone Call with Carrier, Email with Carrier, Carrier Tracking Website, Tracking Portal, FourKites, MacroPoint, Trucker Tools, P44, No Contact, Other.

Things to know

The ETA names its stop. Store it against eta_native_system_stop_id, not against whatever your TMS treats as the next stop. They differ when a stop was skipped or reordered.
Updates are append-only. We never edit or delete a load update we sent. A correction arrives as a new update.
comment has no prefix or suffix. If you store comment rather than comment_formatted, use entered_by_name and load_update_information_source to show who made it and where it came from.

Was this helpful?