Carrier Integration
AAA Cooper Transportation
in Salesforce
Rates, pickup scheduling, shipment tracking, document imaging, and cargo claims, seven SOAP/XML Web Services and a complete EDI suite, unified inside your CRM.
SOAP/XML Web Services
EDI 204/210/211/214/820/997
~180 Terminals
Southeast & South Central
Shipment Lifecycle
Rate Estimate
SOAP/XML rate quote with class-based LTL pricing
Transit Time
Separate SOAP/XML call returning estimated transit days
Pickup Request
SOAP/XML or EDI 204, architecturally independent
Tracking
SOAP/XML Web Service + EDI 214 status updates
Document Imaging
Retrieve POD, BOL, and delivery images via SOAP/XML
Cargo Claims
Create and update cargo claims, two dedicated Web Services
4.9★
Integration Rating
46+
Carriers Connected
7
SOAP/XML Web Services
6
EDI Transaction Sets
~180
Terminal Network
Rate Estimate + Transit Time Web Services
LTL Quotes Before the Order Leaves Salesforce
- Class-based LTL pricing with origin, destination, weight, and freight class inputs
- Transit time retrieved via a separate, dedicated Transit Time Web Service call
- Multi-carrier rate comparison within Salesforce, present AAA Cooper alongside other LTL options
- Quote continuity, rates logged to the Salesforce record for audit and rebooking
SOAP/XML Web Service
Separate Transit Time Call
OriginBirmingham, AL 35201
DestinationNashville, TN 37201
Weight500 lbs
Freight Class85
Estimated Charge
$194.40 LTL
Birmingham, AL → Nashville, TN
Illustrative, field names and values shown for reference only
Pickup Scheduling
Schedule Pickups Two Ways
AAA Cooper supports both SOAP/XML Web Service and EDI 204 for pickup scheduling, architecturally independent paths that can coexist.
SOAP/XML Pickup Web Service
AAA Cooper’s Pickup Web Service supports programmatic scheduling via SOAP/XML requests. FTM can integrate this Web Service to initiate pickup requests directly from Salesforce without manual carrier portal access.
EDI 204 Motor Carrier Load Tender
For EDI-enabled trading partners, AAA Cooper supports the 204 transaction set for shipment instructions and pickup requests. The 204 is bidirectional, both AACT and trading partners transmit and receive the transaction.
BOL Note: No separate BOL SOAP/XML Web Service is documented by AAA Cooper Transportation. BOL creation is handled through EDI 211 (Motor Carrier Bill of Lading), which is transmitted inbound to AACT and includes a pre-assigned PRO number.
Tracking Web Service + EDI 214
Shipment Visibility Inside Every Record
AAA Cooper’s Tracking Web Service provides programmatic access to shipment status. EDI 214 Transportation Carrier Shipment Status Message delivers updates on a configurable schedule.
- PRO number-based SOAP/XML tracking queries surfaced on Salesforce records
- EDI 214 three-schedule delivery: once daily (2:30 AM CST), twice daily (2:30 AM + 1:00 PM CST), or every 30 minutes (7:00 AM through midnight CST)
- Both paths are architecturally independent, SOAP/XML and EDI can operate simultaneously
PRO: 123-456789
640 LB · Class 85 · BHM → BNA
Picked Up
Birmingham, AL · 08:14 AM
In Transit
Birmingham Terminal · 11:42 AM
Out for Delivery
Nashville Terminal · 07:30 AM
Delivered
Nashville, TN · 01:07 PM
Imaging + Cargo Claims Web Services
Documents and Claims Without the Portal
AAA Cooper provides three additional Web Services covering document retrieval, claim creation, and claim updates, all accessible via SOAP/XML.
Imaging Web Service
Retrieve POD signatures, BOL copies, and delivery confirmation images programmatically. FTM can integrate the Imaging Web Service to surface these documents on Salesforce shipment records without manual portal retrieval.
Create Cargo Claim
AAA Cooper’s Create Cargo Claim Web Service supports programmatic claim submission. FTM can integrate this Web Service to initiate claims directly from Salesforce exception or damage records.
Update Cargo Claim
A dedicated Update Cargo Claim Web Service allows post-submission updates, including attaching supporting documents. Scoped to claim data and supporting documentation; settlement processing is handled by AAA Cooper internally.
Claim Flow
01
Detect Exception
02
Retrieve Imaging
03
File Claim
04
Update Claim
EDI Integration
Full ANSI X12 EDI Suite
AAA Cooper Transportation supports six ANSI X12 EDI transaction sets. FTM can integrate the complete EDI suite alongside or independent of the SOAP/XML Web Services.
Set
Name
Direction & Notes
204
Motor Carrier Load Tender
⇄ Transmit + Receive
⇄ Transmit + Receive
Shipper transmits pickup requests and shipment instructions to AACT; AACT also transmits 204s to trading partners.
210
Motor Carrier Freight Invoice
← Outbound from AACT
← Outbound from AACT
AACT sends freight invoice to the shipper. Built from accounts receivable files.
211
Motor Carrier Bill of Lading
→ Inbound to AACT
→ Inbound to AACT
Shipper sends BOL to AACT; includes pre-assigned PRO number. This is the documented path for BOL creation, no separate BOL SOAP/XML Web Service is documented.
214
Shipment Status Message
⇄ Transmit + Receive
⇄ Transmit + Receive
AACT transmits status updates on a configurable schedule, once daily at 2:30 AM CST; twice daily at 2:30 AM and 1:00 PM CST; or every 30 minutes from 7:00 AM through midnight CST. Also received by AACT.
820
Payment Order / Remittance
→ Inbound to AACT
→ Inbound to AACT
Shipper sends payment remittance advice to AACT. Processed via Gentran.
997
Functional Acknowledgment
⇄ Transmit + Receive
⇄ Transmit + Receive
Both AACT and trading partners transmit and receive functional acknowledgments confirming receipt of EDI transaction sets.
Connectivity: AAA Cooper supports EDI transmission via FTP, SFTP, and AS2, as well as approved Value-Added Networks (VANs) including Descartes and Kleinschmidt.
Integration Architecture
What Each Party Handles
AAA Cooper provides the carrier-side infrastructure and documented interfaces. FTM provides the Salesforce integration layer.
AAA Cooper Provides
7 SOAP/XML Web Services (Rate, Transit Time, Pickup, Tracking, Imaging, Create Claim, Update Claim)
EDI suite: 204, 210, 211, 214, 820, 997 via FTP/SFTP/AS2 or approved VAN
Security Token IDs, one per Web Service for authentication
~180 terminal network across Southeast, South Central, and Southwest
EDI 214 status updates on three configurable schedules (daily, twice daily, every 30 min)
FTM Can Integrate
Rate Estimate and Transit Time Web Services surfaced on Salesforce records and opportunities
Pickup scheduling via SOAP/XML Web Service or EDI 204, both paths independently configurable
Tracking Web Service queries linked to Salesforce shipment records by PRO number
Imaging Web Service for POD, BOL, and delivery document retrieval inside Salesforce
Cargo claim lifecycle (Create + Update) linked to Salesforce exception records
Full EDI suite mapping through Salesforce, 204, 210, 211, 214, 820, 997
Why AAA Cooper
Built for the Southeast and South Central
AAA Cooper’s regional density, dual-path API architecture, and dedicated cargo claim Web Services make this integration particularly well-suited for shippers concentrated in AACT’s coverage footprint.
Southeast & South Central Strength
~180 terminals across the Southeast, South Central, and Southwest provide density that national carriers often can’t match in these lanes. AAA Cooper consistently serves these markets as a primary carrier.
Cargo Claim Management End to End
Most LTL carrier APIs expose a single claim submission endpoint. AAA Cooper documents both a Create Cargo Claim and an Update Cargo Claim Web Service, enabling a full claim lifecycle from Salesforce without portal handoffs.
Dual-Path Architecture
SOAP/XML Web Services and EDI are architecturally independent in AAA Cooper’s platform. Shippers can use both simultaneously, SOAP/XML for transactional queries and EDI for batch document exchange, without one path conflicting with the other.
Before & After
What Changes With the Integration
Without FTM Integration
Rate quotes pulled manually from AAA Cooper’s web portal, then re-entered into Salesforce
Pickups scheduled through the carrier portal, no Salesforce record linkage
Shipment status checked by logging into the portal and searching by PRO
POD and BOL images downloaded individually, stored outside the CRM
Cargo claims filed through the AAA Cooper portal, no automated linkage to exception records
Supporting documents uploaded manually per claim, no Salesforce audit trail
With FTM + AAA Cooper Integration
AACT rate quotes can be retrieved and logged to Salesforce records without portal access
Pickups can be scheduled via SOAP/XML Web Service or EDI 204 from within Salesforce
Current shipment status from the Tracking Web Service can be surfaced on Salesforce records by PRO number
POD and BOL images can be retrieved via the Imaging Web Service and attached to Salesforce records
Cargo claims can be submitted via the Create Cargo Claim Web Service linked to Salesforce exception records
Supporting documents can be attached to claims via the Update Cargo Claim Web Service, with Salesforce audit trail
Integration Outcomes
By the Numbers
7
SOAP/XML Web Services available for integration
1
Stop for rates, pickup, tracking, imaging, and claims
0
Manual portal logins required for integrated workflows
6
EDI transaction sets supported (204, 210, 211, 214, 820, 997)
~180
Terminal network in Southeast, South Central & Southwest
2
Dedicated cargo claim Web Services (Create + Update)
Related Integrations
Other LTL Carriers
FTM connects Salesforce to a growing network of LTL carriers. Explore other integrations in the Southeast and South Central lanes.
Frequently Asked Questions
Technical details about AAA Cooper’s integration architecture, Web Services, EDI transactions, and authentication.
AAA Cooper Transportation documents SOAP/XML Web Services as its programmatic integration interface. These are not REST APIs, each call uses an XML request envelope and returns an XML response. FTM integrates using the documented SOAP/XML Web Services, not REST endpoints.
AAA Cooper documents seven SOAP/XML Web Services: (1) Rate Estimate, (2) Transit Time, (3) Pickup, (4) Tracking, (5) Imaging, (6) Create Cargo Claim, and (7) Update Cargo Claim. Each Web Service uses a separate Security Token ID for authentication.
No. AAA Cooper does not document a separate BOL SOAP/XML Web Service. Bill of Lading creation is handled through EDI 211 (Motor Carrier Bill of Lading), which is transmitted inbound to AACT and includes a pre-assigned PRO number. FTM does not describe a BOL API unless AAA Cooper independently documents one.
AAA Cooper supports six ANSI X12 EDI transaction sets: 204, 210, 211, 214, 820, and 997. EDI transmission is supported via FTP, SFTP, and AS2, as well as approved Value-Added Networks (VANs) including Descartes and Kleinschmidt. EDI 820 payments are processed through AAA Cooper’s Gentran system.
AAA Cooper uses Security Token IDs for Web Service authentication. Each of the seven SOAP/XML Web Services uses a separate Security Token ID, Rate, Transit Time, Pickup, Tracking, Imaging, Create Cargo Claim, and Update Cargo Claim each require their own credential. These are provisioned by AAA Cooper for authorized trading partners.
Yes. AAA Cooper’s SOAP/XML Web Services and EDI integration are architecturally independent. A shipper can use SOAP/XML for transactional queries (rates, tracking, claims) and EDI for batch document exchange (204, 211, 214) simultaneously, without one path interfering with the other.
Most LTL carrier APIs expose only a single claim submission endpoint. AAA Cooper documents both a Create Cargo Claim and an Update Cargo Claim Web Service, enabling a full claim lifecycle, including attaching supporting documents after initial submission. The Update Cargo Claim Web Service is scoped to claim data and supporting documentation; settlement processing is handled internally by AAA Cooper.
AAA Cooper supports three configurable EDI 214 delivery schedules: (1) once daily at 2:30 AM CST; (2) twice daily at 2:30 AM CST and 1:00 PM CST; or (3) every 30 minutes from 7:00 AM CST through midnight CST. The schedule is configured at the trading partner level.
AAA Cooper Transportation operates approximately 180 terminals, with service concentrated in the Southeast, South Central, and Southwest United States. This regional density makes AAA Cooper particularly well-suited as a primary carrier for shippers with freight lanes concentrated in these markets.
Get Started
Connect Salesforce to AAA Cooper, Rates, Pickup, Tracking & Claims
Seven SOAP/XML Web Services and a complete EDI suite, integrated into your CRM workflows.
