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