Reference · built on requestConnectorShipping & logistics

FourKites

Load tracking, ETAs, callbacks, and delivery documents from FourKites across truckload, LTL, parcel, ocean, air, and rail.

Request accessPricing ↗

About

FourKites is a supply chain visibility platform. Shippers create loads; carriers connect through FourKites Connect with an ELD or GPS provider, the CarrierLink driver app, files, or an API; FourKites then tracks each load, calculates ETAs, and fires callbacks as it moves. The platform covers Full Truck Load, LTL, courier and parcel, ocean, air, and rail, with Appointment Manager and Dynamic Yard alongside.

Through Fibric, an operator reads those callbacks and load records and proposes the next step: a truck assignment before pickup, a dock slot change when an ETA moves, or the upload of a proof of delivery once the carrier sends it. You approve. The connector calls FourKites once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from FourKites and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Load status, position, and ETA for Full Truck Load, LTL/Courier/Parcel, Ocean, Air, and Rail loads, produced by FourKites' Tracking and ETA Calculation services
  • Callbacks, FourKites' push notifications, for load events on truckload, LTL and parcel, Appointment Manager, and the application platform
  • Each carrier's tracking method and assignment state from FourKites Connect: GPS via ELD, the CarrierLink mobile app, Super File or Location File, or API
  • Documents on a load stop by type: Bill of Lading, Delivery Receipt/Proof of Delivery, Packing Slip, Customs Document, Invoice, Freight Bill, and others
  • Appointment Manager Load Sync and Dynamic Yard activity, which FourKites lists as platform services with their own callbacks
  • Tracking that begins a few hours before the pickup appointment and ends once the load is marked delivered, per FourKites' carrier documentation

Proposed actions

  • Target capability: propose assigning a tractor or trailer to a load through POST /api/v1/tracking/truck_assignment on tracking-api.fourkites.com, with shipper, billOfLading, tractorNumber, and trailerNumber
  • Target capability: propose attaching a PDF or JPEG to a load stop through the Document Upload API, keyed by loadNumber, proNumber, trackingNumber, or loadReferenceNumber
  • Target capability: propose creating a load for tracking through the Shipment Creation service for its mode, using the endpoint your subscribed API bundle documents

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Chase the missing proof of delivery

    When a load is delivered but its stop has no Delivery Receipt/Proof of Delivery document, the operator asks the carrier for it and, once a file arrives, proposes the upload with the right load and stop identifiers.

    With Delivery Proof

  • Assign the truck before the pickup window

    For a load with no tractor or trailer assigned as its pickup appointment nears, the operator proposes the assignment from the carrier's dispatch record through the truck assignment API.

    With Tracking Sync

  • Re-plan the dock when the ETA moves

    An ETA change on an inbound truckload triggers a proposal to shift the Appointment Manager slot and to tell the receiving team, with the callback that caused it attached.

    With Dock Schedule

  • Flag a load that went quiet

    If positions stop arriving from a carrier's ELD or CarrierLink feed while the load is in transit, the operator checks the carrier's tracking method in FourKites Connect and proposes a check-in.

    With Stalled Shipment

Requirements

  • A FourKites shipper, broker, or carrier account and access to the developer portal at developer.fourkites.com, requested through its access form
  • An API key generated in the portal, subscribed to at least one API bundle and bound to the static IP address your requests come from
  • For the truck assignment API, a username and password from FourKites Support, sent as HTTP Basic or Digest (Nonce) authentication
  • Carriers connected through FourKites Connect with a tracking method in place, since positions come from their ELD, CarrierLink, file, or API feed
  • Bill-to codes from each carrier when assignment is automated, so FourKites can match their loads to yours
Authentication
API keys issued in the FourKites developer portal per subscribed bundle and static IP address, plus HTTP Basic or Digest credentials from FourKites Support for the tracking assignment API.

Limits

  • The API reference at docs.fourkites.com/api-reference sits behind a FourKites sign-in; this listing draws on the developer portal, public knowledge base, and GitHub samples.
  • Document uploads take at most 2 MB per call, are asynchronous, and FourKites does not validate load details before accepting them.
  • The truck assignment sample accepts one vehicle per request.
  • API keys are tied to a static IP address and to the bundles you subscribe, and the portal caps the number of active keys.

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request FourKites ↗

Questions and answers

Where does FourKites get a load's position?
From the carrier's tracking method. FourKites Connect lists four: GPS through the carrier's ELD provider, the driver's CarrierLink app, files such as the Super File or Location File, and the carrier's own API. When several exist, the primary method follows the order API, File, GPS, Mobile.
How do you attach a proof of delivery to a load?
Through the Document Upload API: a load identifier (loadNumber, proNumber, trackingNumber, or loadReferenceNumber), a stop identifier (stopReference, stopId, locationId, or stopSequence), the type (jpeg or pdf), a document_type code such as DR for Delivery Receipt/Proof of Delivery, and base64_content. Each call takes at most 2 MB.
Is the FourKites API reference public?
No. docs.fourkites.com/api-reference asks for a FourKites sign-in, and the developer portal issues keys only to accounts it approves. What is public: the portal's key and bundle model, the truck assignment sample on GitHub, the Document Upload fields in the knowledge base, and the service list on the status page.
Ask about FourKites

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with FourKites through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy