TrackFlo
Load legs

Create or update a load leg

One leg per route / movement. Legs carry the carrier, driver and rep assignments that TrackFlo tracks and works.

POST /api/v1/loadlegs/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

· LoadLegUpsert
required application/json
native_system_load_leg_id string · max length: 100· nullable

Required. Your TMS's id for the leg (route / movement).

load_leg_sequence integer · nullable

Required. 1-based position of this leg within the load.

native_system_load_id string · max length: 100· nullable

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

native_system_load_unique_key string · max length: 100· nullable

Recommended. Key TrackFlo uses to build the 'View in TMS' link for this load.

native_system_reference_number string · max length: 100· nullable

Recommended. Leg-level reference number. Shown as a reference number and searchable.

pickup_reference_number string · max length: 1000· nullable

Recommended. Pickup number for the first stop. Shown as a reference number and searchable.

native_system_load_leg_permalink string · max length: 100 required

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

native_system_load_permalink string · max length: 100· nullable

Required. Unique key of the parent load: -.

Responses