Integrate FourKites predictive ETA and live location tracking for over-the-road truckload shipments via API
domain: developer.fourkites.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate using the FourKites API key provided in your account settings; include it as a header on all API requests
Create a shipment tracking record via POST to the shipments endpoint with carrier SCAC code, PRO/BOL number, origin, destination, and pickup appointment
Poll GET /shipments/{id} or subscribe to FourKites webhooks for location updates, dwell alerts, and ETA change notifications
Parse the currentLocation object for GPS coordinates and the predictedEta field for the machine-learning-derived arrival estimate
Surface ETA deltas (difference between original appointment and predicted ETA) in your TMS or customer notification system to trigger proactive communications
Handle geofence events from the webhook payload to detect arrival at shipper, carrier terminal, and consignee locations automatically
Known gotchas
FourKites ETA accuracy depends on carrier ELD data availability; shipments with carriers that have low telematics coverage will fall back to cell-tower or check-call data with lower precision
Shipments must be activated before the scheduled pickup; if you submit a tracking record after departure, initial location history may be absent
Webhook delivery is not guaranteed exactly-once; implement idempotent event processing using the shipment ID and event timestamp as a deduplication key
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?