Carrier Integrations

How deep the integration goes decides what it costs you

A rating-only integration still leaves you re-keying tenders, chasing portals for status, and reconciling invoices by hand. We take it end to end — rating, tender, tracking, documents, webhooks and EDI.

100+

US trucking companies

Nationwide

coverage

API + EDI

dual-channel integration

What each channel supports

// capability coverage by integration type

National 3PL / Broker APIs

Rating (incl. volume LTL)
API tender with carrier reference returned
End-to-end status tracking
Automated BOL / POD retrieval (a few channels still require manual portal pickup)
Signed webhooks for live events

EDI Carriers

204 tender
214 status
990 response
Online rating
Document retrieval

Parcel / Fulfillment APIs

Multi-service rating
API shipment creation
Label generation
Tracking
Address validation & residential detection

Local Delivery APIs

On-demand dispatch
Same-day / next-day windows
Same order flow as line-haul

Every capability is wired carrier by carrier. Carrier API maturity varies widely — some push live status, some expose documents only, some run on EDI. We adapt per carrier, automate everything that can be automated, and cover the rest with process rather than manual re-keying.

Why carriers are not named here: You will be connecting your own carrier contracts, not ours. What decides the outcome is how deep these layers go — not who we happen to have agreements with. The specific integration list, and whether your existing accounts and rates can be wired in, is shared during evaluation.

How the costs land on one order: Finance →

Why each layer matters

each missing layer maps to a real cost

Rating: one wrong class, repriced downstream

Density, NMFC, stackability, linear feet, residential flags — get any of them wrong and the carrier reprices and rebills. Validating before tender is far cheaper than disputing after.

Tender: re-keying is where incidents start

Copying a quote into a tender by hand eventually corrupts addresses, time windows or accessorials. API tendering returns the carrier reference immediately, so both ledgers agree from the start.

Tracking: where support time goes

Scheduled polling plus webhook push, written back onto the order timeline. Without it, every "where is my freight" costs someone a portal login.

Documents & EDI: the basis for reconciliation

BOL and POD are retrieved and filed automatically. The EDI channel runs 204/214/990 — tender, status and confirmation move as transactions, not email attachments.

If you hold the authorization, we can wire it in

integration and customization is its own service line — no capacity purchase required

Your own carriers and vendors

Any counterparty you already hold a contract and API credentials with — carrier, customs broker, warehouse, insurer — we build the adapter against their actual interface and run it on your account and your negotiated rates. Every channel in the system today was built exactly this way.

Open API: into the systems you already run

Rating, tender and tracking can be called directly from your own code, authenticated with a separately issued API key. Access is granted per module — only what you need, revocable at any time. Wire in an ERP, WMS or storefront instead of asking someone to re-enter it in a portal.

White-label: your customers see you

Your own domain and brand, with your entity, remittance details and contacts on the paperwork. From order to invoice, your customers never see us.

Built around your process

Pricing rules, approval gates, report definitions, document layouts and accounting hookups (QuickBooks two-way sync, for one) are shaped to how you already work, rather than forcing your process into someone else's defaults.

We only integrate what you are authorized to use. The accounts and agreements stay in your name. We do not hold them on your behalf, resell them, or work around a provider's API terms. Revoke access and the integration stops.