API Changelog

Every change to the TrackFlo Integration API, newest first.

10.16.26

• New optional field on POST /api/v1/loadlegs/upsert: no_contact_load. Send true when your TMS marks the movement (or its order) as do-not-contact. TrackFlo then sends no automated outreach on it (SMS, voice, WhatsApp, carrier email, MacroPoint) and shows a no-contact icon on the board.

• New optional field on POST /api/v1/stops/upsert: planned_appointment_utc, the stop's original planned appointment, kept as first planned even after a reschedule. It enables the Planned ETA Drift exception. For a date-only plan, send 12:00 in the stop's local time, as UTC.

• New optional field on POST /api/v1/loadupdates/upsert: eta_stop_permalink, the stop that eta_utc is for (its native_system_stop_permalink). Without it, TrackFlo assumes the next stop not yet arrived.

9.25.26

• New optional field on POST /api/v1/loads/upsert: commodity carries the order's freight. The top level holds the order totals: description, pieces, weight and weight_unit. An optional items list gives the lines behind them, with the same four keys per line.

  • pieces and weight must be JSON numbers, not strings.

  • weight_unit is required whenever weight is sent.

  • pieces counts pieces only. A quantity your TMS records in pallets or other handling units is not a piece count, so leave it out.

  • 0 pieces is valid (bulk freight).

  • Extra keys are accepted.

  • The object replaces what TrackFlo holds; send null to clear it.

  • A malformed commodity fails the whole upsert with 400, and details names the field. See Data model.

9.12.26

• New optional field on POST /api/v1/loadlegs/upsert: driving_type: single or team. Send it when your TMS knows. If omitted, TrackFlo keeps the value it already holds, except that a populated driver_2_name or driver_2_phone_number promotes the leg to team (it is never demoted to single automatically). Team legs are excluded from the single-driver rest-break ETA when a company enables it.

• Authentication page and spec now state that a key is issued for one kind of caller: an integration key opens the /api/v1/* upserts and nothing else; a key of another kind presented there is refused with 403.

9.9.26

• get-assignee is X-API-Key only. The legacy token query parameter is no longer accepted; a request without the header returns 401 regardless of the query string. Every Front workspace was migrated to a Front Integration key first, so no configuration change is needed unless yours still relies on token=.

9.6.26

• Documented timestamp semantics (_utc / _local, offsets are not converted) and the versioning policy.

• First publication of the OpenAPI 3.1 reference for the five upsert endpoints.

• Upsert responses are now a JSON envelope {status, message, permalink} on all five endpoints (status codes unchanged).

• get-assignee accepts X-API-Key (Front Integration keys); the legacy token query parameter is being retired.

• Per-key rate limits with 429 + Retry-After.