The update is triggered when any load expires.

This document offers a comprehensive overview of a system update that occurs when a load expires. It features a detailed JSON example showcasing numerous crucial fields, including message type, load identifier, shipment identifier, total distance, shipper

Fast Track Scan

Load Not Reachable/Stale

Load Started Tracking

FourKites API Reference

Ocean Tracking Subscription

Insights API Subscription

Subscriptions

FourKites® API Reference

API Credentials

Authentication

DateTime Format

Idempotency Protection

Pagination

Rate Limits

Versioning

Making Requests

Status Codes

Errors

Request ID

Performance & Timeout

Interpreting Responses

Create Shipment

Shipments _All Modes_

Truckload (TL)

Parcel

Ocean - Update Shipment

Ocean

Rail / Intermodal

Update Shipment

Real-Time Transportation Visibility

Mark Shipment Hot

Mark Shipment Delivered

Get Shipments

Get Shipment Details

Delete Shipment

User Message Creation API Using Load Number

User Message Creation API

Get API Metrics

Upload Document

Get Document

Documents

Get Shipment E-URL

Stop E-URL

Share Shipment Status _E-URL_

Tracking Quality & Analytics

Insights API

Simple Update in GS1 API

Async Order Create

Async Delivery API

Sync Delivery API

Order Update API

Delivery Exist

Get Delivery E-URL

Get Delivery

Get Order Existence

Get Order Tracking URL

Get Orders

Order Lifecycle Visibility

Demand Forecast Inventory

Supply Forecast Inventory

WMS Current Inventory

Inventory Visibility

(Legacy) Dispatcher Update

Assignment Update

Dispatcher Update - Asynchronous (All Key-Value)

Error Handling

ETA Update

Event Update

Load Information Updates

Location Update

Stop level updates

Success Scenario Samples

Temperature Update

Assets

Dispatcher Update - Asynchronous

For Carriers

Create Shipment with Pallets

Specify Appointment Calendar

Update Shipment (Full)

Get Slots

Reserve Slots

Reschedule Appointments

Check-In/Out

Unblock Reserve Slots

Manage Loads & Appointments

Tracking to Appointment Manager Data Flow

Appointment Manager to Tracking Data Flow

Interoperability

Appointment Manager

Callbacks Count API

Callbacks Data Dictionary

Enabling Webhooks

FourKites X

Late Reason Code

Load Updates

Network Visibility

Ocean Events

Stop Updates

Temperature

Tracking Updates

User Message

Shipments

Delivery Events

Order Events

Order Risk

Shipment Events

Orders

Stop Doc/File Upload

Dynamic Yard

Facilities

New Carrier Added

Stop/Address Geofence Update

Entities _ Networks

Webhooks

Field Name	Description	Key Always Present?	Conditions for the Key to be Present	Data Type	Max Length
FourKitesLoadId	Unique load identifier from FourKites system	Yes	N/A	Number	20
LoadNumber	Unique shipment identifier from shipper's system	Yes	N/A	String	65535
TotalDistance	The total distance (in meters) from the initial pickup stop to the final delivery stop. This is calculated after all the stops on the load are geocoded.	Yes	N/A
Shipper	Unique shipper ID from FourKites	Yes	N/A	String	No max, but realistically, not longer than 200 characters
Carrier	Unique carrier identifier from FourKites system	Yes	N/A	String	1024
Status	The status of load corresponding to the tracking update done. For example, "Expired".	Yes	N/A	String	100 max
Timestamp	The time (ISO 8601 format) when the Geofence was updated in UTC.	Yes	N/A	String in DateTime format	30
Timezone	The timezone in UTC.	Yes	N/A	String	50
TimezoneShortName	Will be hard coded to "UTC"	Yes	N/A	String	5
TimezoneOffset	Number of seconds the time zone is ahead of UTC time. For western hemisphere, time zones will be represented in negative values indicating that the time is behind UTC.	Yes	N/A	[+/-]Digits	10
TerminationTime		Yes	N/A
CreatedBy	This applies only for FourKites X loads.	Yes, if it's a FourKites X load.	The CreatedBy field will be available and sent only for FourKites X licensed customers — this is to identify between FourKites X and non FourKites X loads.	String	1024

Load Not Reachable/Stale

Field Definitions