Carriers / CrossCountry Freight Solutions

Handle CrossCountry Freight Solutions shipments through one Unified API

If CrossCountry Freight Solutions 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

5 workflows

CCYQ carrier code

LTL freight shipment type

Carrier-specific handling

What ShipPeek handles for CrossCountry Freight Solutions

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

Workflow mapping

ShipPeek maps CrossCountry Freight Solutions 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 CrossCountry Freight Solutions in ShipPeek

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

Tracking

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

Rates

Request eligible CrossCountry Freight Solutions rates without creating a carrier-specific quoting path.

Booking

Create supported CrossCountry Freight Solutions shipments from the same integration surface when your account is enabled.

Documents

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

Integration model

One API contract, CrossCountry Freight Solutions-aware routing

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

Track CrossCountry Freight Solutions shipments and status events without portal checks
Request eligible CrossCountry Freight Solutions rates through the Unified API
Create CrossCountry Freight Solutions bookings where your carrier account allows it
Pull CrossCountry Freight Solutions BOLs and delivery documents into your system
Keep CrossCountry Freight Solutions inside the same API contract as the rest of your carriers

Unified API example

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

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

How it works

How a CrossCountry Freight Solutions request moves through ShipPeek

Send one request

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

Apply carrier setup

ShipPeek uses the enabled CrossCountry Freight Solutions configuration, including carrier identifier ccyq, 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 CrossCountry Freight Solutions fits in your operation

Confirm how CrossCountry Freight Solutions can fit into quoting, operations, customer support, and shipment visibility workflows.

Quote eligible CrossCountry Freight Solutions lanes in checkout, OMS, TMS, or WMS flows

Track CrossCountry Freight Solutions shipments and surface status changes to operators or customers

Create CrossCountry Freight Solutions bookings when your account and service rules allow it

Pull CrossCountry Freight Solutions BOLs, delivery receipts, and shipment documents into support workflows

Compare CrossCountry Freight Solutions with other enabled carriers from the same request model

Reduce portal checks, email attachments, and spreadsheet handoffs

Add more carriers without redesigning the CrossCountry Freight Solutions integration

FAQ

Questions about CrossCountry Freight Solutions

How does ShipPeek support CrossCountry Freight Solutions?

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

Can I track CrossCountry Freight Solutions shipments?

Yes. ShipPeek normalizes CrossCountry Freight Solutions 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 CrossCountry Freight Solutions 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 CrossCountry Freight Solutions bookings?

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

Can I get CrossCountry Freight Solutions labels or documents?

ShipPeek can return CrossCountry Freight Solutions BOLs, delivery receipts, or carrier documents where available through enabled Unified API workflows.

What does ShipPeek handle for CrossCountry Freight Solutions?

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 CrossCountry Freight Solutions and your carrier account setup.

Is ShipPeek an official CrossCountry Freight Solutions API?

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

Start with Unified API Book demo