Handle Roadrunner Freight shipments through one Unified API
If Roadrunner Freight 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
- RDFS carrier code
- LTL freight shipment type
Carrier-specific handling
What ShipPeek handles for Roadrunner Freight
ShipPeek is not asking your team to buy a standalone Roadrunner Freight API. Roadrunner Freight 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 RDFS and your enabled carrier-account configuration from one place instead of hardcoding Roadrunner Freight rules into every product workflow.
Workflow mapping
02ShipPeek maps Roadrunner Freight 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 Roadrunner Freight in ShipPeek
Capabilities are enabled per account and carrier configuration, so this page shows the Roadrunner Freight workflows ShipPeek can route through the Unified API — not a promise that every lane or service is available for every account.
Tracking
Roadrunner Freight tracking events come back in the same shipment status model you use across every supported carrier.
Rates
Request eligible Roadrunner Freight rates without creating a carrier-specific quoting path.
Booking
Create supported Roadrunner Freight shipments from the same integration surface when your account is enabled.
Labels
Return carrier-issued Roadrunner Freight labels where that workflow is enabled.
Documents
Pull BOLs, delivery receipts, and other shipment documents into normalized workflows.
Integration model
One API contract, Roadrunner Freight-aware routing
Keep ShipPeek's Unified API as the integration surface. Use carrier identifier rdfs to route eligible workflows to Roadrunner Freight; ShipPeek keeps carrier-specific request fields, credentials, and response mappings out of your product code.
- Track Roadrunner Freight shipments and status events without portal checks
- Request eligible Roadrunner Freight rates through the Unified API
- Create Roadrunner Freight bookings where your carrier account allows it
- Retrieve carrier-issued Roadrunner Freight labels when enabled
- Pull Roadrunner Freight BOLs and delivery documents into your system
- Keep Roadrunner Freight inside the same API contract as the rest of your carriers
Unified API example
curl "https://api.shippeek.com/track/444444444?carrier=rdfs" \
-H "Authorization: Bearer YOUR_TOKEN"The carrier identifier selects an enabled workflow. It does not create a separate Roadrunner Freight product surface; ShipPeek's Unified API remains the contract.
How it works
How a Roadrunner Freight request moves through ShipPeek
Send one request
01Your app sends a standard ShipPeek request for the workflow it needs and includes Roadrunner Freight only when that carrier should handle the shipment.
Apply carrier setup
02ShipPeek uses the enabled Roadrunner Freight configuration, including carrier identifier rdfs, 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 Roadrunner Freight fits in your operation
Confirm how Roadrunner Freight can fit into quoting, operations, customer support, and shipment visibility workflows.
Quote eligible Roadrunner Freight lanes in checkout, OMS, TMS, or WMS flows
Track Roadrunner Freight shipments and surface status changes to operators or customers
Create Roadrunner Freight bookings when your account and service rules allow it
Retrieve Roadrunner Freight labels without a carrier-specific backend path
Pull Roadrunner Freight BOLs, delivery receipts, and shipment documents into support workflows
Compare Roadrunner Freight with other enabled carriers from the same request model
Reduce portal checks, email attachments, and spreadsheet handoffs
Add more carriers without redesigning the Roadrunner Freight integration
FAQ
Questions about Roadrunner Freight
How does ShipPeek support Roadrunner Freight?
ShipPeek supports Roadrunner Freight as a carrier workflow inside the ShipPeek Unified API. It is not a separate Roadrunner Freight-only product or an official Roadrunner Freight-owned API; enabled capabilities depend on your account, region, credentials, and carrier permissions.
Can I track Roadrunner Freight shipments?
Yes. ShipPeek normalizes Roadrunner Freight 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 Roadrunner Freight 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 Roadrunner Freight bookings?
Yes, where enabled through ShipPeek's Unified API. Booking still depends on your carrier account, service, permissions, and Roadrunner Freight rules.
Can I get Roadrunner Freight labels or documents?
ShipPeek can return carrier-issued Roadrunner Freight labels, BOLs, delivery receipts, or documents where available through enabled Unified API workflows.
What does ShipPeek handle for Roadrunner Freight?
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 Roadrunner Freight and your carrier account setup.
Is ShipPeek an official Roadrunner Freight API?
No. ShipPeek is a unified logistics API platform that connects to supported carrier integrations. ShipPeek is not Roadrunner Freight or a Roadrunner Freight-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 Roadrunner Freight without making Roadrunner Freight 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 Roadrunner Freight 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 Roadrunner Freight implementation