FourKites API

Overview

FourKites is a supply chain visibility platform that connects shippers, carriers, and brokers with real-time freight tracking, predictive ETA data, and exception management across multimodal shipments. Its platform aggregates carrier tracking data from GPS, ELD systems, and carrier check-ins to provide a unified visibility layer that enterprise shippers use to monitor active shipments, manage delivery commitments, and coordinate carrier responses to delays and exceptions. For freight analytics platforms, supply chain visibility tools, and shipper technology teams building products that surface real-time freight data to operations and customer service teams, FourKites is a priority integration target: enterprise shippers that have standardized on its visibility platform expect their adjacent analytics and operations tools to pull tracking and ETA data from it programmatically.

API access to FourKites requires an enterprise agreement and formal onboarding process before credentials are issued. There is no self-serve developer portal, no sandbox environment outside the enterprise relationship, and no documented path to production API access without completing a contract negotiation with FourKites' commercial team. The enterprise agreement reflects FourKites' go-to-market model as a platform for large shippers and carriers, and the process involves commercial terms, technical onboarding, and minimum commitments that are sized for enterprise relationships rather than for a freight tech startup building a new analytics product on FourKites data. Freight tech and analytics platforms that want to pull real-time tracking and ETA data programmatically need an enterprise relationship in place before they can begin building, which means the development timeline cannot start until the commercial process finishes.

Integuru generates a production-ready HTTP API for FourKites using direct HTTP requests against the same endpoints the FourKites web application uses internally for shipment tracking, ETA retrieval, exception management, and carrier operations. The ten planned actions cover the supply chain visibility data surfaces that freight tech and analytics teams need: predictive ETA and tracking queries, real-time exception alerts, active shipment monitoring, carrier network data, and load records, without an enterprise agreement or commercial onboarding process blocking access to the visibility data that supply chain tech is built around.

---

Why Teams Need This Integration

FourKites' contract-gated access model creates hard dependencies for freight tech teams across several categories of supply chain visibility and analytics product.

Supply chain visibility dashboards and operations tools. Shipper-facing visibility platforms that aggregate real-time tracking data across carrier networks need get_shipment_tracking and get_shipment_eta as on-demand queries against the FourKites visibility layer, because ETA accuracy depends on pulling the current predicted arrival rather than relying on a cached data export that may be hours out of date. A visibility dashboard that polls FourKites ETA data on a 15-minute batch schedule cannot give a shipper's customer service team the real-time information they need to answer customer inquiries about specific shipment delays. list_active_shipments feeds the real-time shipment monitor views that operations teams use to track their full freight portfolio across carriers and lanes.

AI exception management and delay triage tools. AI-powered exception management tools that identify, classify, and route delivery exceptions to the appropriate carrier or shipper contact need get_exception_alerts as a real-time feed of delay events with severity classifications and carrier response status. A tool that receives exception data only through a scheduled FourKites report export cannot respond to a developing delay within the window where carrier action can still affect the delivery outcome. get_shipment_tracking gives the AI tool the position history it needs to distinguish between a carrier running slightly behind schedule and one that has stopped in an unexpected location, which affects both the exception severity classification and the appropriate escalation path.

Freight analytics and carrier performance platforms. Freight analytics tools that build carrier performance scorecards, on-time delivery reports, and lane reliability metrics for shipper clients need list_active_shipments, get_load_detail, and get_shipment_eta to pull the tracking and arrival data that carrier performance calculations depend on. list_carriers provides the carrier network data that analytics platforms use to segment performance metrics by carrier, mode, and lane for shipper procurement teams managing carrier relationships and rate negotiations. get_settlement and list_invoices extend the analytics surface to freight cost and audit data for platforms that connect visibility metrics to financial performance.

Carrier onboarding and network management tools. Freight tech platforms that manage carrier onboarding and tracking compliance for shipper visibility programs need list_carriers and update_location to monitor carrier tracking coverage and push location updates for carriers whose native ELD or GPS data does not flow into FourKites automatically. The tracking coverage gap between carriers using native ELD integrations and those requiring manual check-ins is one of the most common data quality problems in enterprise visibility programs, and tools that manage that gap need write access to push location data into the FourKites network.

---

Logistics Workflows This Integration Covers

The ten planned actions cover the supply chain visibility and freight tracking data surfaces that logistics technology teams need from FourKites:

• Predictive ETA and exception management: get_shipment_eta and get_exception_alerts surface predicted arrival data with confidence scores and real-time delay alerts with severity classifications for AI exception management tools and shipper visibility dashboards.
• Active shipment monitoring: list_active_shipments and get_shipment_tracking provide the real-time shipment portfolio view and per-shipment tracking history that operations teams and visibility platform subscribers need to monitor freight in motion.
• Carrier network and tracking coverage: list_carriers surfaces carrier network data with tracking coverage and onboarding status for platforms managing carrier compliance and tracking quality across enterprise shipper visibility programs.
• Load records and detail: list_loads and get_load_detail provide shipment records with shipper, carrier, and routing data for freight analytics platforms building carrier performance and lane reliability metrics.
• Location updates and tracking data: update_location supports carrier location pushes for platforms managing tracking coverage gaps in enterprise visibility networks.
• Freight audit and cost data: get_settlement and list_invoices extend the integration to freight cost and invoice records for analytics platforms connecting visibility data to financial performance metrics.

---

Adjacent Integrations

Integuru already operates in the logistics space in production. The uShip integration delivers live invoice listing for freight and large-item shipping marketplace workflows, demonstrating Integuru's direct HTTP approach on a logistics platform where no official developer API provides self-serve access to the data that freight tech teams need. The FourKites integration follows the same architecture: direct HTTP requests against the internal visibility platform API layer, without browser automation or enterprise agreement dependency, delivering sub-3-second response times and 24/7 on-call maintenance on Production plan accounts. uShip is Integuru's only live logistics integration today, making the FourKites build an expansion into the supply chain visibility layer that enterprise freight analytics and operations platforms depend on.