Skip to content
Home » R+L Carriers

R+L Carriers

R+L Carriers Integration

R+L Carriers LTL Rates, BOL, Pickup, Shipment Tracking, Documents, and Notifications – Available for Integration with FTM in Salesforce.

R+L Carriers documents a broad API suite across the LTL shipment lifecycle – ten named API tools covering rate quote, BOL, pickup, tracking, documents, notifications, claim status, and more, plus EDI. FTM can integrate each so the R+L carrier workflow lives on the Salesforce transportation record, based on your account configuration and integration scope.

Rate Quote API BOL + Pickup Shipment Tracing Documents Notifications EDI 204/210/211/214/216
R+L + FTM shipment lifecycle
Rate Quote + Transit Times
Customer-specific LTL rate + ETA returned to Lane Quote
Rate Quote API + Transit Times API. Pallet Rates endpoint also available.
Bill of Lading
BOL creation, PDF, and shipping labels via BOL API
eBOL API. 13 label styles available. Accessorials carry through from rate quote.
Pickup Request
Pickup scheduled and linked to the FTM shipment record
Pickup Request API. Supports dimensions, quote number, and a Pickup Request History endpoint (April 2026).
Shipment Tracing + Notifications
Up-to-date statuses and EDD via Tracing API; push notifications via Notification API
Trace by PRO, BOL, PO. Real-time push notifications. Service Center lookup available.
Document Retrieval
Shipment documents retrieved to the FTM record
Document Retrieval API. Activity History API for shipment activity reports.
Claim Status
Claim status surfaced on the FTM record by PRO or claim number
Claim Status API.
4.9
AppExchange rating
46+
FTM carrier integrations
Salesforce
Native FTM platform
10
R+L REST APIs available for integration
Rate Quote + Transit Times

Customer-Specific R+L Rates and Transit ETAs, Returned to the FTM Lane Quote in Salesforce.

R+L’s Rate Quote API returns customer-specific LTL rates based on freight class, weight, origin, destination, and accessorials. The Transit Times API returns ZIP-to-ZIP ETAs. FTM can integrate both so rate and ETA are returned together on the Lane Quote without leaving Salesforce.

Origin + Destination
ZIP codes sent to both Rate Quote and Transit Times APIs
Freight Class + Weight
FAK class required for all Rate Quote requests as of April 2026
Accessorials
Residential pickup/delivery (RPU/RC), limited access pickup/delivery (LPU/LD), and more
Pickup Date
Must be within 30 days of request; dimensions accepted without length restriction
Previously submitted quotes can be retrieved
As of April 2026, the Rate Quote API supports retrieval of previously submitted quotes, eliminating the need to resubmit identical requests. Pallet Rates are available via a separate endpoint.
FTM Lane Quote
R+L Rate Retrieved
Shipment details
Origin
Atlanta, GA 30349
Destination
Dallas, TX 75201
Weight
720 LB
Freight Class
Class 70
Routing
Direct
R+L rate response
Net Charge
$218.40
Transit Days
2 business days
Estimated Delivery
Oct 3, 2026
Service
Standard LTL

All values are illustrative. Actual rates and transit times are returned by R+L at time of request based on your account and freight profile. Rates are not guaranteed; a new request may be needed to confirm pricing before tendering. ETAs are estimates, not guaranteed delivery dates.

Bill of Lading + Pickup

BOL Creation, Shipping Labels, and Pickup Scheduling – All Available via R+L’s eBOL and Pickup APIs.

R+L’s eBOL API creates the Bill of Lading, generates the PDF, and produces shipping labels in 13 available styles. The Pickup Request API schedules the pickup and links a quote number. As of April 2026, a Pickup Request History endpoint provides chronological pickup event history.

Bill of Lading (eBOL) API
Available

R+L’s eBOL API creates, prints, and edits Bills of Lading. FTM can integrate BOL creation from the shipment record, generating the BOL document and shipping labels without navigating to MyRLC separately.

BOL creation and PDF generation via API
13 shipping label styles available; start position configurable
Accessorials carry through from Rate Quote (residential, limited access)
Handling Units array supported (Oct 2025); DWOS processing (April 2026)
Pickup Request API
Available

R+L’s Pickup Request API schedules pickups directly with the terminal that services the origin location. FTM can integrate pickup scheduling from the shipment record, linking the quote number and tracking the pickup lifecycle.

Schedule pickup with the originating R+L terminal
Pickup dimensions and quote number included on request (March 2026)
Pickup Request History: a newer endpoint within the Pickup Request API providing chronological pickup event history (April 2026)
EDI path: 204, 211, and 216 for load tender, BOL, and pickup notification
R+L documents EDI 204 (Load Tender / Pickup Request), EDI 211 (Bill of Lading), and EDI 216 (Pickup Notification) as documented transaction sets. For customers whose operations require EDI, FTM can be configured for EDI data exchange with R+L as an alternative or complementary path to the REST APIs.
Shipment Tracing + Notifications

R+L Shipment Status, Estimated Delivery Dates, and Real-Time Push Notifications – Available on the FTM Record.

R+L’s Shipment Tracing API returns up-to-date statuses and estimated delivery dates. Their Notification API delivers real-time push notifications for shipment events. FTM can integrate both so R+L carrier status is visible on the transportation record in Salesforce without logging into MyRLC separately.

Shipment Tracing API
Available

R+L describes this API as returning “up to date statuses, Estimated Delivery Dates” on shipments. FTM can integrate tracing to surface R+L carrier status on the FTM transportation record.

Trace by PRO number, BOL number, or PO number
Trace by Pickup Number also available (beta, Jan 2026 – results may not always be fully accurate)
Estimated Delivery Date returned alongside shipment status
EDI 214 available as a parallel status update path
Notification API
Available

R+L describes their Notification API as “a robust system for creating and managing push notifications.” R+L explicitly confirms real-time push notifications. FTM can integrate this to trigger notifications on shipment events without polling the Tracing API continuously.

Real-time push notifications – R+L’s own description
Create and manage notification subscriptions via API
FTM Shipment Record
R+L Status
Trace info
PRO Number
027-38291
Status
Out for Delivery
Est. Delivery
Oct 3, 2026
Event history
Picked up – Atlanta, GA
Oct 1 08:14
Departed origin terminal
Oct 1 20:42
Out for delivery – Dallas, TX
Oct 3 07:08
Delivered
Est. Oct 3

Illustrative only. R+L’s Shipment Tracing API returns “up to date statuses and Estimated Delivery Dates” – not a guaranteed delivery window. Pickup Number tracing is in beta (Jan 2026) and may not always return fully accurate results.

Documents, Claims, and Activity History

Shipment Documents, Claim Status, and Activity Reports – Retrievable via API and Available on the FTM Record.

R+L’s Document Retrieval API retrieves shipment-related documents. The Claim Status API returns claim status by PRO or claim number. The Activity History API returns a shipment activity report. FTM can integrate each so this data surfaces on the Salesforce transportation record rather than requiring a MyRLC portal login.

Document Retrieval API
Available

R+L’s Document Retrieval API retrieves documents related to a shipment, including BOL, delivery receipt, and other shipping documents. FTM can integrate document retrieval so documents are accessible from the FTM record without navigating to MyRLC.

Retrieve shipment documents by PRO or reference number
BOL, delivery receipt, and related shipping documents
Available for integration based on account document access
Claim Status API
Available

R+L’s Claim Status API returns the status of a cargo claim by PRO or claim number. FTM can integrate claim status retrieval to surface claim information on the FTM record – not to file or resolve claims, but to surface status.

Check claim status by PRO or claim number
Status information surfaced on the FTM shipment record
Does not file, adjudicate, or resolve claims
Activity History API
Available

R+L’s Activity History API returns a report of shipment activity. FTM can integrate activity history retrieval to surface shipment event records on the FTM transportation record, supporting audit and operations review.

Shipment activity report by reference
Available for integration based on account configuration
Service Center API
Available

R+L’s Service Center API locates R+L service centers and service points based on ZIP code. FTM can integrate this to surface the servicing terminal for a given shipment origin or destination.

Service center lookup by ZIP code
Useful for displaying the R+L terminal handling a shipment
EDI path: 210 and 214 for invoice and status
R+L documents EDI 210 (Freight Invoice) and EDI 214 (Shipment Status) as confirmed transaction sets. EDI is a separate integration path from the REST APIs and is configured independently. FTM can be set up for EDI exchange with R+L where the customer account includes EDI capability.
Two systems, one workflow

R+L Manages the LTL Network. FTM Manages the Transportation Record in Salesforce.

R+L provides the LTL infrastructure – rates, BOL, pickup, tracking, documents, and claims. FTM provides the Salesforce-native layer where all that carrier data connects to the transportation record that drives quoting, dispatch, and operations.

R+L Carriers Provides
Customer-specific LTL rate quotes via Rate Quote API
ZIP-to-ZIP transit ETAs via Transit Times API (not guaranteed delivery)
BOL creation, PDF document, and shipping labels (13 styles) via eBOL API
Pickup scheduling with the originating terminal via Pickup Request API
Up-to-date shipment status and EDD via Shipment Tracing API
Real-time push notifications via Notification API
Shipment documents via Document Retrieval API
Claim status by PRO or claim number via Claim Status API
EDI: 204, 210, 211, 214, 216 as confirmed transaction sets
FTM Can Integrate
R+L rate and transit ETA on the Lane Quote in Salesforce
Direct vs indirect routing visibility from the Rate Quote API
BOL creation and shipping label generation from the FTM shipment record
Pickup request and pickup event history on the FTM record
R+L shipment status and estimated delivery date on the FTM record
R+L push notifications routed through Salesforce workflows
Shipment documents and activity history linked to the FTM record
R+L claim status surfaced on the FTM shipment record
EDI data exchange with R+L where account EDI is configured
Why R+L in FTM

R+L Documents a Broad REST API Suite Across the LTL Shipment Lifecycle. FTM Brings Every Layer into Salesforce.

R+L officially documents APIs for Rate Quote, Transit Times, Bill of Lading, Pickup Request, Shipment Tracing, Document Retrieval, Service Center, Notification, Claim Status, and Activity History – ten named API tools covering the shipment lifecycle from quote to claim, plus a documented EDI suite. FTM can integrate each layer so R+L is fully managed from the Salesforce transportation record.

Ten documented REST APIs
Rate Quote, Transit Times, Bill of Lading, Pickup Request, Shipment Tracing, Document Retrieval, Service Center, Notification, Claim Status, and Activity History – ten named API tools independently documented on technology.rlcarriers.com. FTM can integrate any combination based on customer requirements.
EDI suite alongside REST
R+L documents EDI 204, 210, 211, 214, and 216 as confirmed transaction sets. EDI is a separate path for customers whose operations require it. FTM can be configured for EDI exchange with R+L, running independently from or alongside the REST API integration.
Real-time push notifications
R+L explicitly describes their Notification API as delivering real-time push notifications. This is a different architecture from polling the Tracing API – events push to FTM when they happen, enabling Salesforce workflow triggers based on R+L shipment events without continuous polling.
Before and after

What Changes When R+L is Connected to FTM in Salesforce

Without FTM integration, R+L data lives in MyRLC – looked up separately from Salesforce. With FTM, R+L rate, status, documents, and notifications connect to the transportation record where operations run.

Without R+L connected to FTM
Log into MyRLC separately to get R+L rates for each shipment
Create the BOL in MyRLC and copy PRO number back to Salesforce
Poll MyRLC for shipment status and update Salesforce manually
Download documents from MyRLC and attach to the Salesforce record manually
Check claim status in MyRLC and note it manually on the shipment
With R+L capabilities integrated into FTM
R+L rate and transit ETA returned to the Lane Quote in Salesforce
BOL created and shipping labels generated from the FTM shipment record
R+L shipment status and EDD updated on the FTM record; push notifications available
Shipment documents retrieved and linked to the FTM record
Claim status visible on the FTM shipment record without a MyRLC login
Outcomes

What Connecting R+L to FTM Makes Possible

R+L rates on the Lane Quote without leaving Salesforce
Customer-specific R+L LTL rates are returned directly to the FTM Lane Quote when integrated, with accessorials and direct vs indirect routing visibility – no MyRLC login required to quote.
BOL and shipping labels from the FTM record
When BOL integration is configured, the R+L Bill of Lading and shipping labels in your preferred style are created from the FTM shipment record – keeping the BOL step connected to the Salesforce workflow.
Shipment status and EDD on the Salesforce record
R+L’s up-to-date shipment status and estimated delivery date are surfaced on the FTM transportation record when tracing integration is enabled, reducing manual lookups against MyRLC during transit.
Push notifications without polling
R+L’s Notification API delivers real-time push events. When integrated, Salesforce workflows can trigger on R+L shipment events as they happen, rather than relying on periodic status polling.
Documents and claim status on the FTM record
When document retrieval and claim status integration are configured, R+L shipment documents and claim status information are accessible from the FTM record – without navigating to MyRLC for each one.
EDI path for customers who need it
For R+L accounts that operate on EDI, FTM can be configured for 204, 210, 211, 214, and 216 exchange – supporting structured EDI workflows as an alternative or complement to the REST API integration.
R+L FAQ

Common questions about R+L Carriers integration in FTM.

The FTM team can discuss which APIs are right for your R+L account.

R+L documents ten named API tools available for FTM integration: Rate Quote, Transit Times, Bill of Lading (eBOL), Pickup Request, Shipment Tracing, Document Retrieval, Service Center, Notification, Claim Status, and Activity History. Pickup Request History is a newer endpoint within the Pickup Request API, not a separate top-level API. R+L also documents EDI transactions including 204, 210, 211, 214, and 216. The specific capabilities active for a given FTM customer depend on account configuration and the integration scope configured for the deployment.
Yes – this is available for integration. R+L’s Rate Quote API returns customer-specific LTL rates based on freight class, weight, origin, destination, accessorials, and pickup date. The Transit Times API returns ZIP-to-ZIP ETAs. FTM can integrate both to surface rate and ETA on the Lane Quote in Salesforce. Note that as of April 2026, FAK (Freight All Kinds) class is required for all Rate Quote requests. Rates are not guaranteed; a new request may be needed before tendering.
Yes – available for integration. R+L’s eBOL API creates Bills of Lading, generates PDF documents, and produces shipping labels. R+L supports 13 label styles with configurable start positions. The BOL API carries through accessorials from the Rate Quote (including residential and limited access). FTM can integrate BOL creation from the shipment record so the BOL is generated without navigating to MyRLC separately.
R+L’s Shipment Tracing API supports tracing by PRO number, BOL number, and PO number. As of January 2026, tracing by Pickup Number (TraceType=PickupID) was added, though R+L notes this trace type is in beta and results may not always be fully accurate. The API returns up-to-date statuses and Estimated Delivery Dates – not guaranteed delivery windows. FTM can integrate tracing to surface R+L status on the FTM transportation record in Salesforce.
R+L describes their Notification API as “a robust system for creating and managing push notifications” and confirms real-time push notifications. This is architecturally different from the Shipment Tracing API: rather than FTM polling R+L for status updates on a schedule, R+L pushes shipment events to a configured endpoint when they occur. When integrated with FTM, this enables Salesforce workflows to trigger on R+L events in closer to real time, without continuous polling.
Yes. R+L documents EDI transaction sets including EDI 204 (Load Tender / Pickup Request), EDI 210 (Freight Invoice), EDI 211 (Bill of Lading), EDI 214 (Shipment Status), and EDI 216 (Pickup Notification). R+L also documents 990, 997, and 820 as part of their EDI suite. EDI is a separate integration path from R+L’s REST APIs and is configured independently. Both REST and SOAP endpoints are available through R+L’s developer portal, though REST is the primary path. FTM can be configured for EDI exchange with R+L where the customer account includes EDI capability.
Both are available for integration. R+L’s Claim Status API returns the status of a cargo claim by PRO or claim number – FTM can integrate this to surface claim status on the FTM record. R+L’s Document Retrieval API retrieves shipment-related documents including BOL and delivery receipt. Note that FTM integration surfaces claim status information; it does not file, adjudicate, or resolve claims with R+L.
R+L published four release notes through April 2026 from their developer portal at technology.rlcarriers.com. January 2026: Pickup Number tracing (beta), residential/limited access accessorials split into four distinct codes (RPU/RC/LPU/LD), 20-ft length restriction removed from Rate Quote, 30-day pickup date limit enforced. March 2026: Pickup dimensions and quote number added to Pickup Request. April 2026: new Pickup Request History endpoint added to the Pickup Request API (not a separate top-level API), FAK class now required for all Rate Quote requests, previously submitted quotes now retrievable. Existing integrations may need updates to include FAK class.
No. Each R+L API is independently configurable and requires a MyRLC account and API key for access. Not every account will have access to every API – for example, Document Retrieval depends on what documents are available for the account. FTM can be configured for any combination of R+L APIs based on customer requirements and account access. Contact the FTM team to discuss which APIs are relevant to your R+L account and how to scope the integration for your deployment.
No. R+L rates returned by the Rate Quote API are customer-specific quotes at the time of request and are not guaranteed. A new rate request may be needed to confirm current pricing before tendering a shipment. Transit times returned by the Transit Times API are estimates based on ZIP code pairs and are not guaranteed delivery dates. Estimated Delivery Dates from the Shipment Tracing API are also estimates, not delivery commitments. Actual rates and delivery timing depend on shipment specifics and R+L network conditions at time of dispatch.
R+L Carriers + FTM

Connect R+L Rates, BOL, Pickup, Tracking, Documents, and Notifications to FTM – and Manage the Full LTL Lifecycle from the Salesforce Transportation Record.

Tell us which R+L APIs matter most to your operation – rate quoting, BOL creation, shipment tracking, push notifications, document retrieval, or the full lifecycle. We will walk through which capabilities are available for your R+L account and how to configure them in FTM.

A MyRLC account and R+L API key are required. Each API is independently configurable. Contact [email protected] to discuss integration scope for your R+L account.

Leave a Reply

Your email address will not be published. Required fields are marked *

Let's Talk!

Thanks for stopping by! We're here to help, please don't hesitate to reach out.

Watch 3-Min Demo
↑