TrackFlo
Stops

Create or update a stop

One stop per pickup or delivery on a leg, with its appointment window and actual arrival / departure.

POST /api/v1/stops/upsert
API key in header X-API-Key

Query parameters

· 1
sync_run_time string · date-time

ISO-8601 UTC time your sync run started (e.g. 2026-09-06T12:00:00Z). Send it on every batch / polling upsert: if the record changed in TrackFlo after this time (a user edit, a fresher webhook) the upsert answers skipped instead of overwriting it. Not needed for event-driven (webhook) posts.

Headers

· 1
Trackflo-Ingest-Source string · enum

pull for scheduled polling, webhook for event-driven pushes. Lets TrackFlo monitor the health of each ingestion path separately; recommended on every request.

values

  • pull
  • webhook

Body

· StopUpsert
required application/json
native_system_stop_id string · max length: 100· nullable

Required. Your TMS's id for the stop.

native_system_load_id string · max length: 100· nullable

Required. Your TMS's id of the parent load.

native_system_load_leg_id string · max length: 100· nullable

Required. Your TMS's id of the parent leg.

native_system_load_permalink string · max length: 100· nullable

Required. Unique key of the parent load: -.

native_system_load_leg_permalink string · max length: 100· nullable

Required. Unique key of the parent leg: -.

native_system_stop_permalink string · max length: 100 required

Required. Unique key: -. Identifies the stop on every upsert.

native_system_stop_reference_number string · max length: 100· nullable

Recommended. Stop-level reference (pickup / delivery number). Shown and searchable.

native_system_stop_status string · max length: 100· nullable

Recommended. Stop status as your TMS names it (e.g. planned, arrived, departed).

Responses