Carriers / CCFS

Handle CCFS shipments through one Unified API

If CCFS 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

6 workflows

CCFS carrier code

LTL freight shipment type

Carrier-specific handling

What ShipPeek handles for CCFS

ShipPeek is not asking your team to buy a standalone CCFS API. CCFS 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 CCFS and your enabled carrier-account configuration from one place instead of hardcoding CCFS rules into every product workflow.

Workflow mapping

ShipPeek maps CCFS 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 CCFS in ShipPeek

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

Tracking

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

Rates

Request eligible CCFS rates without creating a carrier-specific quoting path.

Booking

Create supported CCFS shipments from the same integration surface when your account is enabled.

Labels

Return carrier-issued CCFS labels where that workflow is enabled.

Documents

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

Integration model

One API contract, CCFS-aware routing

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

Track CCFS shipments and status events without portal checks
Request eligible CCFS rates through the Unified API
Create CCFS bookings where your carrier account allows it
Retrieve carrier-issued CCFS labels when enabled
Pull CCFS BOLs and delivery documents into your system
Keep CCFS inside the same API contract as the rest of your carriers

Unified API example

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

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

How it works

How a CCFS request moves through ShipPeek

Send one request

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

Apply carrier setup

ShipPeek uses the enabled CCFS configuration, including carrier identifier ccfs, 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 CCFS fits in your operation

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

Quote eligible CCFS lanes in checkout, OMS, TMS, or WMS flows

Track CCFS shipments and surface status changes to operators or customers

Create CCFS bookings when your account and service rules allow it

Retrieve CCFS labels without a carrier-specific backend path

Pull CCFS BOLs, delivery receipts, and shipment documents into support workflows

Compare CCFS with other enabled carriers from the same request model

Reduce portal checks, email attachments, and spreadsheet handoffs

Add more carriers without redesigning the CCFS integration

FAQ

Questions about CCFS

How does ShipPeek support CCFS?

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

Can I track CCFS shipments?

Yes. ShipPeek normalizes CCFS 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 CCFS 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 CCFS bookings?

Yes, where enabled through ShipPeek's Unified API. Booking still depends on your carrier account, service, permissions, and CCFS rules.

Can I get CCFS labels or documents?

ShipPeek can return carrier-issued CCFS labels, BOLs, delivery receipts, or documents where available through enabled Unified API workflows.

What does ShipPeek handle for CCFS?

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

Is ShipPeek an official CCFS API?

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

Start with Unified API Book demo