Stop Event Endpoint

Updated today

Record the arrival and departure times on the stop named in native_system_stop_id. We send a stop event whenever a tracker records an arrival or departure, or one is approved from a driver or carrier message, along with any delay reason.

Suggested path: POST /trackflo/stop-events. 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 stop_event.

Field	Type	Description
`native_system_stop_id`	string	Your stop id, as you sent it to TrackFlo.
`stop_sequence`	integer	The stop's position on the leg, starting at 1.
`stop_type`	string	The stop type, as you sent it to TrackFlo.
`arrived_date_time_utc`	string or null	When the truck arrived.
`arrived_date_time_local`	string or null	The same time, local to the stop.
`departed_date_time_utc`	string or null	When the truck left.
`departed_date_time_local`	string or null	The same time, local to the stop.
`stop_local_iana_timezone`	string	The stop's timezone, for example `America/New_York`.
`delay_code`	string or null	Why the truck was late. See Delay codes below.
`delay_comment`	string or null	The tracker's explanation of the delay, up to 500 characters.
`stop_update_data_source`	string	Where the times came from. Same values as `load_update_information_source` on the Load Update Endpoint.
`comment`	string or null	Anything else the tracker wrote, up to 600 characters.

Example

{
  "event_id": "0c9a7e52-3b1f-4d8e-a6c2-91f04e7d2b13",
  "event_type": "stop_event",
  "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-25T13:05:44Z",
  "trackflo_load_url": "https://app.trackflo.tech/public_load_details/4b6e…",
  "native_system_stop_id": "88214",
  "stop_sequence": 2,
  "stop_type": "Delivery",
  "arrived_date_time_utc": "2026-10-25T12:10:00Z",
  "arrived_date_time_local": "2026-10-25T07:10:00",
  "departed_date_time_utc": null,
  "departed_date_time_local": null,
  "stop_local_iana_timezone": "America/Chicago",
  "delay_code": "AH",
  "delay_comment": "Driver ran out of hours overnight, restarted at 05:00.",
  "stop_update_data_source": "Phone Call with Driver",
  "comment": null
}

Respond with your stop's id or the id of the record you created:

{ "id": "88214" }

Applying a stop event

An event can carry an arrival, a departure, or both. A null time means that time isn't part of this update. Leave the value you hold in place; it never means clear it.
A correction is a new event. When a tracker fixes a wrong time, we send the corrected time in a new stop event. Overwrite the stored time with it.
A status change can follow. When a stop event moves the load to a new status, such as an arrival at the pickup, we also send a status change using your status code for it. Your team builds that mapping with us during onboarding.

Delay codes

By default, delay_code is an EDI 214 status reason code. If your TMS keeps its own list, we agree it with you during onboarding and send your codes instead.

Code	Meaning
`AF`	Accident
`AG`	Consignee related
`AH`	Driver related
`AI`	Mechanical breakdown
`AJ`	Other carrier related
`AL`	Previous stop (multi-stop loads only)
`AM`	Shipper related
`AO`	Weather or natural disaster related
`BG`	Customer, other
`D1`	Internal error

A delay_code always comes with a delay_comment.

Was this helpful?