Subscribe to FourKites load tracking events and retrieve predictive ETA updates for an over-the-road truckload shipment via the FourKites in-app integration
Obtain FourKites API credentials (API key or OAuth token) from the FourKites partner or customer portal for your account.
POST a new tracking request to the FourKites Shipments API including the shipment identifier, carrier SCAC, PRO or BOL number, origin, destination, and scheduled pickup time.
Register a webhook endpoint in the FourKites platform or via API so FourKites pushes status events (departed, in-transit, ETA update, arrived, delivered) to your system rather than requiring polling.
On each webhook payload, extract the predicted_eta field and the confidence_score or reliability indicator FourKites includes alongside predictive ETAs; store these against the shipment record.
When a load is delivered or cancelled, call the FourKites API to explicitly close the tracking subscription to avoid unnecessary event traffic.
Known gotchas
FourKites ETA predictions are recalculated as the truck moves; downstream systems should treat ETA as a mutable field and not cache it statically — always use the most recently received value.
Carrier telematics data availability varies by carrier; FourKites may fall back to location inference from check-calls (EDI 214) if ELD data is not available, which reduces prediction accuracy — the payload typically signals the data source.
Webhook delivery is not guaranteed exactly-once; implement idempotency on your receiver using the event ID or shipment ID plus event type to deduplicate out-of-order or re-delivered events.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp