Estes Express Lines Integration

From Rate Quote to Delivered – the Estes LTL Lifecycle, Connected to FTM and Your Salesforce Transportation Record.

Estes Express Lines provides a documented API suite covering rate quotes, electronic BOL creation, pickup scheduling with real-time milestones, shipment tracking with Estimated Time of Arrival, and document retrieval. FTM can integrate each of these APIs to surface Estes carrier data on the FTM transportation record in Salesforce, based on your account configuration and integration scope.

Rate Quote API eBOL API Pickup API Shipment Tracking API Image Retrieval API

Book Executive Demo Explore FTM Platform

Estes + FTM shipment lifecycle

Quote

Rate Quote + Transit Information

Origin, destination, weight, class, dimensions – direct vs indirect

Prepare

eBOL Creation (NMFTA eBOL Standard)

Electronic BOL – earlier tracking enablement, billing accuracy

Pickup

Scheduled – Milestones – Stops Away – Driver

Create, modify, cancel, track. Real-time Stops Away, ETP, driver name returned by Estes

In Transit

Shipment Milestones + ETA

Real-time status milestones, Stops Away, Estimated Time of Arrival, GPS location during pickup and delivery

Delivered

Delivery Receipt + 14 Document Types

BOL, delivery receipt, and more – via the Estes Image Retrieval API

4.9

AppExchange rating

14 days

Typical core go-live

46+

FTM integrations

Salesforce

Native FTM platform

Estes Rate Quote API

Estes LTL Rate Quotes – Including Direct vs. Indirect Distinction – Available from the FTM Lane Quote.

Estes’ Rate Quote API delivers rate comparisons based on comprehensive freight details. FTM can integrate this API to retrieve Estes pricing directly from the Lane Quote in Salesforce, so your team evaluates Estes alongside other carriers without leaving your TMS.

Shipment details sent to Estes

Origin

City, state, ZIP

Destination

City, state, ZIP

Weight

Shipment weight in lbs

Freight Class

NMFC class from Lane Quote

Dimensions

Length, width, height per item

Shipment Type

LTL service type selection

Direct vs. Indirect Shipment Distinction

Estes’ Rate Quote API specifically returns a distinction between direct and indirect shipment routing – a service-level differentiation FTM can surface on the Lane Quote alongside the rate.

FTM Lane Quote

Estes Rate Retrieved

Shipment details

Origin

Richmond, VA 23225

Destination

Atlanta, GA 30303

Freight Class

Class 100

Weight

750 LB

Dimensions

48 x 40 x 48 in

Estes rate response

Estes Net Charge

$287.40

Routing Type

Direct

Accessorials

Included in rate

All values are illustrative. Actual rates and routing are returned by Estes at time of request and reflect your account pricing. A new request may be needed to confirm current pricing before tendering. Rates are not guaranteed delivery commitments.

From Quote to Shipment

Create an Estes eBOL and Schedule Pickup – All from the FTM Shipment Record.

Once a carrier is selected in FTM, the Estes eBOL API and Pickup API let the shipment move forward from the same Salesforce record – no portal switching for BOL creation or pickup scheduling.

Electronic BOL (eBOL) API

NMFTA eBOL Standard

Estes’ BOL API is built in compliance with the NMFTA Digital LTL Council’s eBOL standard. FTM can integrate this API to create an electronic BOL from shipment data already on the FTM record.

Electronic BOL created and transmitted digitally

Early digital data transmission enables earlier shipment tracking

Improved billing accuracy and freight bill automation

Compliant with industry eBOL standard

Pickup API – Create, Modify, Cancel, Track

Full Lifecycle Management

Estes’ Pickup API supports full pickup lifecycle operations that FTM can integrate. Pickups can be created, modified, or cancelled from the FTM shipment record, and once underway, the API returns real-time milestones.

Create, modify, cancel, or retrieve pickup requests

PRO number reconciled with Pickup Request Number once freight is scanned

Real-time milestones, Stops Away, and Estimated Time of Pickup

Driver name returned by Estes for the scheduled pickup

Pickup visibility

Estes’ Pickup API: Real-Time Stops Away, Driver Name, and Estimated Time of Pickup – Surfaced on the FTM Record.

Estes describes their Pickup API as providing “the industry’s most detailed pickup data.” Where Estes returns pickup milestone information, FTM can surface it on the shipment record in Salesforce – so your team has pickup status without calling Estes customer service.

Estes Pickup Visibility

Pickup in progress

Pickup milestones

Scheduled

Dispatched

En Route

Picked Up

Stops Away

3 stops

Est. Pickup Time

2:45 PM

Driver

J. Martinez

Pickup Ref.

PU-7741924

Pickup milestone data is illustrative. Actual milestones, Stops Away, ETP, and driver name are returned by Estes where available for the shipment. Estimated Time of Pickup is not a guaranteed delivery commitment.

Real-Time Stops Away

Estes’ Pickup API provides a real-time view of how many stops remain before the driver arrives. FTM can display Stops Away on the FTM shipment record where Estes returns this information.

Estimated Time of Pickup

Estes documents an Estimated Time of Pickup as part of the Pickup API response. FTM can surface this on the shipment record to give operations teams a pickup window without calling Estes customer service.

Driver Name from Estes

Estes explicitly documents that the Pickup API can return the name of the driver assigned to pick up the freight. FTM can surface this information on the FTM shipment record where Estes provides it.

PRO Number via Pickup Reconciliation

Estes’ API reconciles the PRO number with the Pickup Request Number once freight is scanned into the Estes system. FTM can capture the PRO number on the shipment record at that point for onward tracking.

Modify and Cancel Pickups from FTM

Estes’ Pickup API supports modification and cancellation in addition to creation. FTM can integrate these operations so pickup changes can be made from the Salesforce record rather than through the Estes portal.

Shipment Tracking API

Real-Time Shipment Milestones, Stops Away, ETA, and GPS Location – on the FTM Transportation Record.

Estes’ Shipment Tracking API provides real-time status updates as the shipment moves through the Estes network. FTM can integrate this to keep the FTM shipment record current without manual status lookups.

FTM Shipment Record – Estes Tracking

In Transit

Picked Up Departed In Transit Out for Delivery Delivered

PRO Number

059-88142

Stops Away

2 stops

Est. Arrival

Tomorrow by 5 PM

GPS Location

Charlotte, NC

Shipment events

Freight picked up

Richmond, VA

Day 1, 11:20 AM

Departed Estes Richmond

Richmond, VA service center

Day 1, 8:00 PM

In transit

Charlotte, NC

Day 2, 6:45 AM

Out for delivery

Estimated

Day 3

Tracking data is illustrative. Actual milestones, Stops Away, ETA, and GPS location are returned by Estes’ Tracking API where available. Estimated Time of Arrival is not a guaranteed delivery commitment.

Shipment Milestones with Progress Bar

Estes’ Tracking API provides a visual progress bar concept with important shipment milestones. FTM can surface each milestone on the shipment record as the freight moves through the Estes network.

Stops Away During Delivery

Estes’ Shipment Tracking API includes Stops Away information as a milestone, matching the same data available in the Pickup API. FTM can display this during the final delivery phase.

Estimated Time of Arrival

Estes documents an Estimated Time of Arrival as part of the Shipment Tracking API response. FTM can surface this on the FTM record where Estes provides it. ETA information is not a guaranteed delivery commitment.

GPS Location During Pickup and Delivery

Estes documents GPS location of the shipment during pickups and delivery as part of the Tracking API. FTM can integrate this where Estes provides location data for the shipment.

Delivery Exception Codes and Appointment History

Estes’ Tracking API includes delivery exception codes and Appointment History in its response. FTM can surface exception information on the FTM record to support customer service and exception management.

Image Retrieval API

14 Document Types – BOL, Delivery Receipt, and More – Retrievable from the FTM Shipment Record.

Estes’ Image Retrieval API supports 14 different types of document images. FTM can integrate this API so that shipping documents are accessible from the FTM shipment record rather than through a separate Estes portal login.

Estes Image Retrieval API

14 Document Types

Estes’ Image Retrieval API provides access to critical shipping records stored against the shipment. FTM can integrate document retrieval so that shipping paperwork is available from the FTM record without a separate portal login.

Bill of Lading (BOL)

Delivery receipt

Additional document types – 14 supported in total by Estes

Additional Estes REST API Capabilities

Available for Integration

Estes’ 2026 Digital Capabilities Matrix documents additional REST capabilities beyond the five core APIs. FTM can integrate these based on customer requirements and Estes account access.

Update BOL – modify a submitted BOL via REST

Pre-Pickup Visibility – pickup status before freight moves

Delivery ETA and Stops Away via dedicated REST endpoint

Recent Shipments – shipment history via REST

Invoice Retrieval on Demand – invoice documents via REST

Webhook support for select tracking and visibility events

Legacy SOAP APIs also supported

Estes continues to support their legacy SOAP APIs alongside the enhanced REST suite. FTM can work with either path based on your Estes account configuration.

Roles across the integration

Estes Operates the Freight Network. FTM Manages the Carrier Relationship in Salesforce.

Estes provides the LTL carrier infrastructure, APIs, and data. FTM provides the Salesforce-native transportation management layer that connects carrier data to the record where operations happen.

Estes Express Lines Provides

Rate quotes based on origin, destination, weight, class, and dimensions

eBOL creation per NMFTA Digital LTL Council standard

Pickup management with milestones, Stops Away, ETP, and driver name

Shipment tracking milestones, Stops Away, ETA, GPS, and exception codes

BOL, delivery receipt, and 14 document types via Image Retrieval API

Enhanced REST APIs covering the full shipment lifecycle; legacy SOAP also supported

FTM Can Integrate

Estes rate quotes and direct/indirect routing on the FTM Lane Quote

eBOL creation from the FTM shipment record

Pickup creation, modification, cancellation, and real-time milestone display

Shipment tracking status, milestones, ETA, and exception data on FTM record

Carrier document access from the FTM shipment record

PRO number, reference data, and carrier status on the FTM load record

Why Estes belongs in FTM

Estes Built One of the Most Detailed LTL API Suites in the Industry. FTM Can Connect It to Salesforce.

Estes’ API documentation is unusually specific – naming Stops Away, driver name, GPS location, ETA, delivery exception codes, and 14 document types explicitly. That level of detail gives FTM a richer carrier data story than most LTL integrations can offer.

Pickup visibility before the PRO exists

Estes’ Pickup API lets shippers track their pickup using the Pickup Request Number – before the PRO is assigned. That Stops Away and driver information covers the visibility gap that exists in most LTL workflows.

A lifecycle that extends from quote to delivered

Rate Quote, eBOL, Pickup, Shipment Tracking, and Image Retrieval are five separate, documented Estes APIs. FTM can integrate each so Estes carrier data flows onto the Salesforce transportation record based on your deployment scope.

Documents accessible without the Estes portal

Estes’ Image Retrieval API supports 14 document types. When integrated, BOLs, delivery receipts, and other shipping documents can be retrieved from Salesforce – reducing the need for separate portal logins to close out a shipment.

Before and after

What Changes When Estes Connects to FTM

Without FTM integration, Estes is managed through a separate carrier portal at each step of the shipment lifecycle. With FTM, Estes carrier data flows onto the Salesforce record where quoting, dispatch, and operations already happen.

Without Estes connected to FTM

Re-enter shipment details to create a BOL and schedule pickup

No pickup visibility until the PRO is assigned – call Estes for status

Manually check Estes tracking for shipment milestones and delivery status

Log back in to retrieve BOL and delivery receipt documents

Estes carrier data disconnected from the FTM transportation record

With Estes capabilities integrated into FTM

Estes rate quote retrieved from the FTM Lane Quote – direct vs indirect included

eBOL created and pickup scheduled from the FTM shipment record

Stops Away, ETP, and driver name surfaced before the PRO is assigned

Shipment milestones, ETA, and GPS location on the FTM record in transit

BOL, delivery receipt, and carrier documents accessible from Salesforce

Estes carrier lifecycle connected to the FTM transportation record end to end

Outcomes

What Connecting Estes to FTM Makes Possible

Estes rates on the Lane Quote including routing type

Account-specific Estes pricing with direct vs. indirect routing distinction is available from the Lane Quote in Salesforce, giving your team a more complete carrier comparison.

eBOL created per industry standard from FTM

When integrated, Estes eBOL creation from the FTM shipment record transmits data to Estes early, enabling earlier shipment tracking and improved billing accuracy without re-entering freight data.

Pickup visibility before the PRO is assigned

When pickup integration is enabled, Stops Away, Estimated Time of Pickup, and driver name from Estes can be surfaced on the FTM record – covering the visibility gap that exists before a PRO is issued.

Shipment milestones and ETA on the Salesforce record

When tracking is integrated, Estes shipment milestones, Stops Away during delivery, and Estimated Time of Arrival are visible on the FTM record – reducing manual status lookups and customer service calls.

Carrier documents accessible without the Estes portal

When document integration is configured, Estes BOLs, delivery receipts, and other documents can be retrieved from the FTM shipment record without logging into a separate carrier portal.

Estes lifecycle connected to FTM from quote to delivery

All five Estes APIs – Rate Quote, eBOL, Pickup, Tracking, and Image Retrieval – can be integrated with FTM, creating a connected Estes carrier experience from the initial quote through the final delivery document.

Related FTM LTL Integrations

Estes FAQ

Common questions about the Estes Express integration in FTM.

For integration planning and configuration, the FTM team can help.

Talk to a Specialist

What Estes APIs can FTM integrate?

Estes documents five core enhanced APIs: Rate Quote, Bill of Lading (eBOL), Pickup, Shipment Tracking, and Image Retrieval. Estes’ 2026 Digital Capabilities Matrix also documents additional REST capabilities including Update BOL, Pre-Pickup Visibility, Delivery ETA, Recent Shipments, and Invoice Retrieval on Demand. FTM can integrate any of these based on customer requirements and account configuration. Which capabilities are active for a given FTM deployment depends on Estes account access and the integration scope configured.

What does the Estes Pickup API return?

Estes’ Pickup API supports creation, modification, cancellation, and tracking of pickups. It provides a real-time view of pickup milestones and exceptions, including Stops Away and Estimated Time of Pickup. Estes also documents that the Pickup API can return the name of the driver who will be picking up the freight. Once freight is scanned into the Estes system, the API reconciles the PRO number with the Pickup Request Number. FTM can surface each of these data points on the FTM shipment record where Estes provides them.

Can FTM show pickup status before a PRO number is assigned?

Yes – this is one of the specific advantages of Estes’ Pickup API. Estes allows shippers to track a pickup using the Pickup Request Number before the freight has been scanned and a PRO assigned. The Stops Away count, Estimated Time of Pickup, and driver name can be available through the Pickup API at this stage. FTM can integrate this to surface pickup visibility on the FTM record from the moment the pickup is dispatched.

What does the Estes Shipment Tracking API return?

Estes’ Shipment Tracking API provides real-time status updates as freight moves through the Estes network. Documented features include shipment milestones with a visual progress bar concept, Stops Away information, Estimated Time of Arrival, GPS location of the shipment during pickups and delivery, delivery exception codes, and Appointment History. FTM can integrate this data to keep the FTM shipment record current as the shipment progresses. ETA information is not a guaranteed delivery commitment.

What is Estes’ eBOL API and why does it matter?

Estes’ BOL API is built in compliance with the NMFTA Digital LTL Council’s eBOL standard – the industry-standard format for electronic Bills of Lading. Estes notes that early digital data transmission via this API allows for earlier shipment tracking, improved billing accuracy, and freight bill automation. FTM can integrate the eBOL API to create an electronic BOL from the FTM shipment record without re-entering data into the Estes portal.

What documents can the Estes Image Retrieval API return?

Estes’ Image Retrieval API supports 14 different types of document images, including Bills of Lading, delivery receipts, and additional shipping documents. FTM can integrate the Image Retrieval API so that carrier documents are accessible from the FTM shipment record in Salesforce without logging into the Estes portal separately.

Does Estes support SOAP APIs alongside the enhanced REST suite?

Yes. Estes explicitly confirms continued support for their legacy SOAP APIs alongside the enhanced REST suite. The enhanced REST APIs are the primary integration path and provide the richest data – including Pickup milestones, ETA, GPS, and Image Retrieval. FTM can work with either path based on your Estes account configuration and requirements.

Does the Rate Quote API distinguish between direct and indirect shipments?

Yes – Estes specifically documents a distinction between direct and indirect shipment routing as part of the Rate Quote API response. This means FTM can surface not just the rate but also the routing type on the Lane Quote, giving your team a more complete carrier comparison alongside other LTL options.

What is needed to activate the Estes integration in FTM?

An active Estes Express account with access to Estes’ API services is required. The specific APIs available depend on your Estes account configuration. Contact the FTM team at [email protected] to discuss which Estes API capabilities are the right fit for your operation and how to configure them in your FTM deployment.

Estes Express Lines + FTM

Connect the Complete Estes LTL Lifecycle to FTM – From Rate Quote to Delivery Receipt.

Tell us about your Estes lanes and how much of the carrier lifecycle you want visible in Salesforce. We will show you how FTM can integrate Estes rate quotes, eBOL, pickup visibility with Stops Away and driver data, shipment tracking milestones, and document retrieval – all on the FTM transportation record.