Carrier’s official API

AAA Cooper Transportation API: integration guide

AAA Cooper Transportation is an LTL carrier headquartered in Dothan, Alabama, serving the US and Canada. Its web services cover rate estimates, transit times, pickup requests, shipment tracking and retrieval of shipment documents such as BOLs and delivery receipts. They are aimed at shippers, 3PLs and TMS vendors that already ship with AAA Cooper.

This guide covers AAA Cooper Transportation’s own API (api2.aaacooper.com:8200). Credentials come from AAA Cooper Transportation, not from FreightAPIs, and we are not affiliated with them.

Want one API key for carrier terminals, NMFC and ports instead? FreightAPIs API docs →

Interface SOAP/XML (SOAP 1.1, document/literal) · REST/JSON (Imaging)Endpoints 5Reviewed 2026-10-09Open in ChatGPT↗Open in Claude↗

At a glance

CarrierAAA Cooper Transportation
TypeLTL carrier
SCACAACT
InterfaceSOAP/XML (SOAP 1.1, document/literal), REST/JSON (Imaging)
AuthenticationStatic API token sent in the request
CapabilitiesRate quote, Transit time, Pickup request, Shipment tracking, Documents & images (BOL, delivery receipt, weight certificate)

Getting access

  • Log in to the AAA Cooper website with a customer web account and open the Web Services (API) page. Your organization's API token is shown on that page.
  • The same token works for every service: rate estimate, transit time, pickup, tracking and imaging.
  • A separate test environment exists for each service. You have to contact AAA Cooper so they can configure your API account for it before test calls will work.
  • The documentation does not mention fees, rate limits or a formal approval process.

Authentication

Static API token sent in the request.

  • There are no auth headers and no token exchange. The token goes inside each request, and it does not expire or need refreshing.
  • The element name differs by service: Token (rate estimate), TokenID (pickup and transit time), token in lower case (tracking).
  • The REST Imaging service takes the token as a query parameter named token.
  • The Imaging service returns HTTP 403 when the token is missing or invalid, or when the PRO number is not associated with your user.

Environments

Productionhttps://api2.aaacooper.com:8200/sapi30

Endpoints

Rate quote

Send origin, destination, freight lines and accessorial codes to get an estimate with total charges, discount, fuel surcharge and transit days. The returned EstimateNumber can be passed to the pickup request.

SOAPwsGenRateEstimateRate estimate (endpoint /wsGenEst): returns a priced LTL estimate.
Key inputsToken, CustomerNumberOriginCity / OriginState / OriginZip / OriginCountryCode (USA | CAN)DestinationCity / DestinationState / DestinationZip / DestinCountryCodeWhoAmI (S | C | T), PrePaidCollect (P | C), BillDateAccLine > AccCode (e.g. LGD liftgate delivery, RSD residential delivery, ISD inside delivery, NCM notify, PALET pallet pricing)RateEstimateRequestLine (Weight, Class, HandlingUnits, HandlingUnitType, Hazmat, CubeU, Length, Width, Height, NMFC, NMFCSub)FullCoverage / FullCoverageAmount, TotalPalletCount
Key outputsErrorMessage, EstimateNumberTotalCharges, MinimumCharge, Discount, Tariff, FuelSurchargePercentTotalActualWeight, TotalAsWeight, DensityOriginTerminal / DestinTerminal (+ phone), InterlineFlag, TotalTransitGuaranteedDeliveryFee, TotChgWGuarDelFee, TotChgWFVCFee, TotChgWFVCAndGDARateEstimateResponseLine (Class, Weight, Rate, Charges, Accessorial)

Transit time

Look up standard transit days and the expected delivery date between two points, plus the service centers and any interline partner at each end.

SOAPwsGetTranTimeTransit time (endpoint /wsTranTime): returns transit days and delivery date for a lane.
Key inputsTokenIDOriginCity / OriginState / OriginZip / OriginCountry (USA | CAN)DestinationCity / DestinationState / DestinationZip / DestinationCountryShipDate (MM/DD/YYYY, optional)Customer (9 digits, zero-padded, optional)
Key outputsMatch > TotalTransit, DeliveryDate, ShipDateOriginTerminal / DestinTerminal and their namesOriginSCAC / OriginCarrier, DestinSCAC / DestinCarrier (interline partner, if any)errmsgid, errmessage, severity

Pickup request

Create a pickup request for one pickup location. Each shipment going out from that location can be listed as a LineItem with its destination, weight and handling units. The response returns a confirmation number and the assigned service center.

SOAPwsPickUpRqPickup request (endpoint /wsPickUpRq): schedules a driver pickup.
Key inputsTokenIDPkupCompanyName, PkupCompanyAddress, PkupCompanyCity, PkupCompanyState, PkupCompanyZip, PkupCompanyCountryPkupCompanyContact, PkupCompanyEmail, PkupCompanyPhone (10 digits)PickupDate (MM/DD/YYYY), ReadyTime and CloseTime (HH:MM)LineItems > LineItem (EstimateNumber, BOLID, Pieces, HandlingUnitType, TotalWeight, IsHazmat, IsACTGuaranteedDay, Destination* fields)
Key outputsPickupRequestNumberACTTerminal, ACTTerminalPhoneErrorCode, ErrorMessage, AlertMessage, Severity

Shipment tracking

Track by exactly one of PRO number, BOL number or PO number. The response is a list of PROs, each with status, delivery details, appointment window, terminals and a dated status history.

SOAPWsGetTrackingTracking (endpoint /wsTracking): returns shipment details and status history.
Key inputstokenProNumber, BOLNumber or PONumber (only one)
Key outputsProLine[] > ProNumber, Status, DeliveryCode, DeliveryDate, DeliveryTime, SignedForPickupDate, Pieces, Weight, Terms, AmountDueOriginTerminal / DestinationTerminal (+ names and phones)AppointmentDate, AppointmentStartTimeSTD / UTC, AppointmentEndTimeSTD / UTCTracingLine[] (Description, Date, Time, TimeUTC)ErrorMessage

Documents & images (BOL, delivery receipt, weight certificate)

A REST endpoint that returns download URLs for a PRO's documents. You can ask for one document type or all freight documents, in PDF or TIF, and optionally merge them into a single file.

GET/documentsImaging: returns URLs for the requested document images of one PRO.
Key inputstoken, proNumbertype (BL, DR, WBILL or FREIGHT DOCUMENTS)format (PDF | TIF)single (Yes | No, default No)
Key outputsproNumberimages[] (url, type, format)On error: message, severity

Example request

Track a shipment by PRO number (SOAP)xml
POST https://api2.aaacooper.com:8200/sapi30/wsTracking Content-Type: text/xml; charset=utf-8 <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <GetTrackingRequest xmlns="http://tempuri.org/WsGetTracking/"> <token>YOUR_API_TOKEN</token> <ProNumber>YOUR_PRO_NUMBER</ProNumber> <BOLNumber /> <PONumber /> </GetTrackingRequest> </soap:Body> </soap:Envelope>

Leave BOLNumber and PONumber empty when you track by PRO. Each service has its own namespace under http://tempuri.org/ (for example wsGetTranTime/, wsPickUpRq/, wsGenRateEstimate/).

Integration notes

  • The token field is spelled three ways: Token (rate estimate), TokenID (pickup, transit time) and token (tracking and the Imaging query string). XML is case-sensitive, so a wrong spelling fails as an invalid token.
  • Date formats differ by service. Pickup and transit time use MM/DD/YYYY. The rate estimate BillDate uses MMDDYY or MMDDYYYY with no separators. Pickup ReadyTime and CloseTime are HH:MM.
  • SOAP responses come back as text/xml with charset ISO-8859-1. AAA Cooper notes that .NET WCF clients reject this by default and need a custom text message encoder.
  • The Imaging service is the newer REST version. AAA Cooper announced that the old SOAP imaging service is being retired and users must move to the REST endpoint by July 1, 2026.
  • In Imaging requests, URL-encode type values that contain a space, such as FREIGHT%20DOCUMENTS. The type must be BL, DR, WBILL or FREIGHT DOCUMENTS; format must be PDF or TIF.
  • A tracking lookup by BOL or PO can return several ProLine entries, because one reference can map to more than one PRO.
  • Pickup rules worth validating before you send: PickupDate cannot be in the past (ERR0000334), and a Guaranteed Day line (IsACTGuaranteedDay) cannot be hazmat or interline (ERR0000366, ERR0000367). Rely on ErrorCode, not message text, which can vary.
  • Field length limits are tight in the pickup request: company name, address and contact are 30 characters max, city is 20, and phone numbers must be exactly 10 digits.

FAQ

Does AAA Cooper have an API?

Yes. AAA Cooper offers SOAP web services for rate estimates, transit times, pickup requests and tracking, plus a REST Imaging API for BOLs, delivery receipts and weight certificates.

How do I get an AAA Cooper API token?

Log in to your AAA Cooper customer web account and open the Web Services (API) page, where your organization's token is displayed. To use the test environment, contact AAA Cooper to have your API account configured.

Can I track AAA Cooper shipments by BOL or PO number?

Yes. The tracking service accepts a PRO number, a BOL number or a PO number, but only one per request. BOL and PO lookups can return more than one PRO.

How do I download a delivery receipt from the AAA Cooper API?

Call the REST Imaging endpoint with your token, the PRO number, type=DR and format=PDF or TIF. The response contains URLs where the documents can be downloaded.

On FreightAPIs

Freight class calculator →Density and estimated class before you request a quote.Accessorial codes by carrier →Liftgate, residential, limited access — each carrier’s code.

Official resources

Written from AAA Cooper Transportation’s published API documentation and last checked 2026-10-09. FreightAPIs is not affiliated with AAA Cooper Transportation; endpoints and access rules can change, so confirm details in the carrier’s own documentation before going live.

Other carrier API guides

ABF Freight · Estes Express Lines · Saia LTL Freight · TForce Freight · Old Dominion Freight Line · XPO (LTL) · AIT Worldwide Logistics · Amazon Freight