Tai Integration Guide

TrackFlo receives Tai webhooks for shipment create, update and location events, and runs a reconciliation poll against the Tai API to catch anything a webhook missed.

What TrackFlo reads

• Shipments and their stops from the create and update events.

• Location updates from Tai's tracking feed.

• Activity log entries, so notes made in Tai appear on the TrackFlo timeline.

What TrackFlo writes

• Status changes and stop arrivals and departures, through Tai's tracking endpoints.

• Check-call notes.

What your Tai admin sets up

• A Tai API key for TrackFlo. Tai authenticates with an x-api-key header, not a bearer token.

• Webhook delivery to TrackFlo. Subscriptions are configured by Tai support, not through the API. Ask Tai to send ShipmentCreate, ShipmentUpdate and location events to your tenant's TrackFlo webhook hostname with the credentials we issue.

Things to know

• Rate limits. Tai sits behind a rate limiter that returns 429 in bursts. TrackFlo paces its reads around it; an occasional delayed refresh is expected, not a fault.

• No shipment search. Tai has no list or search endpoint, so a shipment TrackFlo never received an event for cannot be discovered by polling. Webhook delivery is therefore essential.

• Stop-level status is derived. Tai reports shipment status, not per-stop status. TrackFlo derives stop progress from arrival and departure timestamps.

• Timezones. Tai reports a UTC offset per stop rather than a zone name. TrackFlo converts on the way in and out.