Carriers / Standard Forwarding

Handle Standard Forwarding shipments through one Unified API

If Standard Forwarding 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.

Start with Unified API API docs

3 workflows

STDF carrier code

LTL freight shipment type

Carrier-specific handling

What ShipPeek handles for Standard Forwarding

ShipPeek is not asking your team to buy a standalone Standard Forwarding API. Standard Forwarding 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

Use STDF and your enabled carrier-account configuration from one place instead of hardcoding Standard Forwarding rules into every product workflow.

Workflow mapping

ShipPeek maps Standard Forwarding rates, tracking events, bookings, labels, and documents into normalized objects where those workflows are enabled.

Operational accountability

Carrier 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 Standard Forwarding in ShipPeek

Capabilities are enabled per account and carrier configuration, so this page shows the Standard Forwarding workflows ShipPeek can route through the Unified API — not a promise that every lane or service is available for every account.

Tracking

Standard Forwarding tracking events come back in the same shipment status model you use across every supported carrier.

Documents

Pull BOLs, delivery receipts, and other shipment documents into normalized workflows.

Integration model

One API contract, Standard Forwarding-aware routing

Keep ShipPeek's Unified API as the integration surface. Use carrier identifier stdf to route eligible workflows to Standard Forwarding; ShipPeek keeps carrier-specific request fields, credentials, and response mappings out of your product code.

Track Standard Forwarding shipments and status events without portal checks
Pull Standard Forwarding BOLs and delivery documents into your system
Keep Standard Forwarding inside the same API contract as the rest of your carriers

Unified API example

curl "https://api.shippeek.com/track/TRACKING_NUMBER?carrier=stdf" \
  -H "Authorization: Bearer YOUR_TOKEN"

The carrier identifier selects an enabled workflow. It does not create a separate Standard Forwarding product surface; ShipPeek's Unified API remains the contract.

How it works

How a Standard Forwarding request moves through ShipPeek

Send one request

Your app sends a standard ShipPeek request for the workflow it needs and includes Standard Forwarding only when that carrier should handle the shipment.

Apply carrier setup

ShipPeek uses the enabled Standard Forwarding configuration, including carrier identifier stdf, credentials, and available workflow rules.

Translate the response

Carrier rates, tracking events, labels, or documents are mapped back into ShipPeek's normalized fields where available.

Act on one model

Your team gets a consistent response shape with enough carrier context to route support, exceptions, and downstream automation.

Use cases

Where Standard Forwarding fits in your operation

Confirm how Standard Forwarding can fit into quoting, operations, customer support, and shipment visibility workflows.

Track Standard Forwarding shipments and surface status changes to operators or customers

Pull Standard Forwarding BOLs, delivery receipts, and shipment documents into support workflows

Compare Standard Forwarding with other enabled carriers from the same request model

Reduce portal checks, email attachments, and spreadsheet handoffs

Add more carriers without redesigning the Standard Forwarding integration

FAQ

Questions about Standard Forwarding

How does ShipPeek support Standard Forwarding?

ShipPeek supports Standard Forwarding as a carrier workflow inside the ShipPeek Unified API. It is not a separate Standard Forwarding-only product or an official Standard Forwarding-owned API; enabled capabilities depend on your account, region, credentials, and carrier permissions.

Can I track Standard Forwarding shipments?

Yes. ShipPeek normalizes Standard Forwarding 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 Standard Forwarding rates?

Rating is not currently listed for this carrier profile. Availability varies by integration setup.

Can ShipPeek create Standard Forwarding bookings?

Booking is not currently listed for this carrier profile. Contact ShipPeek to review whether this workflow can be enabled through the Unified API.

Can I get Standard Forwarding labels or documents?

ShipPeek can return Standard Forwarding BOLs, delivery receipts, or carrier documents where available through enabled Unified API workflows.

What does ShipPeek handle for Standard Forwarding?

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 Standard Forwarding and your carrier account setup.

Is ShipPeek an official Standard Forwarding API?

No. ShipPeek is a unified logistics API platform that connects to supported carrier integrations. ShipPeek is not Standard Forwarding or a Standard Forwarding-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 Standard Forwarding without making Standard Forwarding 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 Standard Forwarding 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 Standard Forwarding implementation

Start with Unified API Book demo