Handle XPO Logistics shipments through one Unified API
If XPO Logistics is part of your shipping mix, ShipPeek gives your team one place to request enabled rates, bookings, tracking, labels, and documents. You keep ShipPeek's Unified API; ShipPeek handles the carrier-specific codes, credentials, mappings, and response differences.
- 6 workflows
- XPOL carrier code
- LTL freight shipment type
Carrier-specific handling
What ShipPeek handles for XPO Logistics
ShipPeek is not asking your team to buy a standalone XPO Logistics API. XPO Logistics runs as an enabled carrier workflow inside ShipPeek's Unified API, with carrier-specific setup, mapping, and response handling kept behind one contract.
Carrier setup
01Use XPOL and your enabled carrier-account configuration from one place instead of hardcoding XPO Logistics rules into every product workflow.
Workflow mapping
02ShipPeek maps XPO Logistics rates, tracking events, bookings, labels, and documents into normalized objects where those workflows are enabled.
Operational accountability
03Carrier responses and exceptions come back through the Unified API so your team can tell whether an issue is credentials, lane/service eligibility, missing documents, or carrier-side availability.
Carrier workflows
What you can do with XPO Logistics in ShipPeek
Capabilities are enabled per account and carrier configuration, so this page shows the XPO Logistics workflows ShipPeek can route through the Unified API — not a promise that every lane or service is available for every account.
Tracking
XPO Logistics tracking events come back in the same shipment status model you use across every supported carrier.
Rates
Request eligible XPO Logistics rates without creating a carrier-specific quoting path.
Booking
Create supported XPO Logistics shipments from the same integration surface when your account is enabled.
Labels
Return carrier-issued XPO Logistics labels where that workflow is enabled.
Documents
Pull BOLs, delivery receipts, and other shipment documents into normalized workflows.
Integration model
One API contract, XPO Logistics-aware routing
Keep ShipPeek's Unified API as the integration surface. Use carrier identifier xpol to route eligible workflows to XPO Logistics; ShipPeek keeps carrier-specific request fields, credentials, and response mappings out of your product code.
- Track XPO Logistics shipments and status events without portal checks
- Request eligible XPO Logistics rates through the Unified API
- Create XPO Logistics bookings where your carrier account allows it
- Retrieve carrier-issued XPO Logistics labels when enabled
- Pull XPO Logistics BOLs and delivery documents into your system
- Keep XPO Logistics inside the same API contract as the rest of your carriers
Unified API example
curl "https://api.shippeek.com/track/619-344051?carrier=xpol" \
-H "Authorization: Bearer YOUR_TOKEN"The carrier identifier selects an enabled workflow. It does not create a separate XPO Logistics product surface; ShipPeek's Unified API remains the contract.
How it works
How a XPO Logistics request moves through ShipPeek
Send one request
01Your app sends a standard ShipPeek request for the workflow it needs and includes XPO Logistics only when that carrier should handle the shipment.
Apply carrier setup
02ShipPeek uses the enabled XPO Logistics configuration, including carrier identifier xpol, credentials, and available workflow rules.
Translate the response
03Carrier rates, tracking events, labels, or documents are mapped back into ShipPeek's normalized fields where available.
Act on one model
04Your team gets a consistent response shape with enough carrier context to route support, exceptions, and downstream automation.
Use cases
Where XPO Logistics fits in your operation
Confirm how XPO Logistics can fit into quoting, operations, customer support, and shipment visibility workflows.
Quote eligible XPO Logistics lanes in checkout, OMS, TMS, or WMS flows
Track XPO Logistics shipments and surface status changes to operators or customers
Create XPO Logistics bookings when your account and service rules allow it
Retrieve XPO Logistics labels without a carrier-specific backend path
Pull XPO Logistics BOLs, delivery receipts, and shipment documents into support workflows
Compare XPO Logistics with other enabled carriers from the same request model
Reduce portal checks, email attachments, and spreadsheet handoffs
Add more carriers without redesigning the XPO Logistics integration
FAQ
Questions about XPO Logistics
How does ShipPeek support XPO Logistics?
ShipPeek supports XPO Logistics as a carrier workflow inside the ShipPeek Unified API. It is not a separate XPO Logistics-only product or an official XPO Logistics-owned API; enabled capabilities depend on your account, region, credentials, and carrier permissions.
Can I track XPO Logistics shipments?
Yes. ShipPeek normalizes XPO Logistics tracking events into the same shipment status model used across supported carriers, so operations and support teams are not forced back into a carrier portal for every update.
Can ShipPeek get XPO Logistics rates?
Yes, where your carrier account, lane, service, and credentials are enabled. The request still uses ShipPeek's Unified API; ShipPeek handles the carrier-specific mapping.
Can ShipPeek create XPO Logistics bookings?
Yes, where enabled through ShipPeek's Unified API. Booking still depends on your carrier account, service, permissions, and XPO Logistics rules.
Can I get XPO Logistics labels or documents?
ShipPeek can return carrier-issued XPO Logistics labels, BOLs, delivery receipts, or documents where available through enabled Unified API workflows.
What does ShipPeek handle for XPO Logistics?
For enabled workflows, ShipPeek handles the Unified API contract, carrier identifier, request and response mapping, status normalization, and document workflow shape. Carrier acceptance, service availability, rates, and document availability still depend on XPO Logistics and your carrier account setup.
Is ShipPeek an official XPO Logistics API?
No. ShipPeek is a unified logistics API platform that connects to supported carrier integrations. ShipPeek is not XPO Logistics or a XPO Logistics-owned API.
Still have questions? Book a call with the ShipPeek team.
Related carriers
Same API, more carrier coverage
Ready to bring this carrier into one workflow?
Use ShipPeek's Unified API for XPO Logistics without making XPO Logistics a one-off integration.
Bring enabled rates, tracking, booking, labels, and documents into one carrier-aware API contract, with ShipPeek handling the carrier-specific differences behind the scenes.
What ShipPeek helps centralize
- One integration surface for enabled XPO Logistics rating, tracking, booking, and documents
- Carrier codes, credentials, status mappings, and exception handling behind the Unified API
- A path to add more carriers without copying the XPO Logistics implementation