Carriers / Central Transport

Handle Central Transport shipments through one Unified API

If Central Transport 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

4 workflows

CTII carrier code

LTL freight shipment type

Carrier-specific handling

What ShipPeek handles for Central Transport

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

Workflow mapping

ShipPeek maps Central Transport 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 Central Transport in ShipPeek

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

Tracking

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

Rates

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

Documents

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

Integration model

One API contract, Central Transport-aware routing

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

Track Central Transport shipments and status events without portal checks
Request eligible Central Transport rates through the Unified API
Pull Central Transport BOLs and delivery documents into your system
Keep Central Transport inside the same API contract as the rest of your carriers

Unified API example

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

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

How it works

How a Central Transport request moves through ShipPeek

Send one request

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

Apply carrier setup

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

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

Quote eligible Central Transport lanes in checkout, OMS, TMS, or WMS flows

Track Central Transport shipments and surface status changes to operators or customers

Pull Central Transport BOLs, delivery receipts, and shipment documents into support workflows

Compare Central Transport with other enabled carriers from the same request model

Reduce portal checks, email attachments, and spreadsheet handoffs

Add more carriers without redesigning the Central Transport integration

FAQ

Questions about Central Transport

How does ShipPeek support Central Transport?

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

Can I track Central Transport shipments?

Yes. ShipPeek normalizes Central Transport 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 Central Transport 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 Central Transport 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 Central Transport labels or documents?

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

What does ShipPeek handle for Central Transport?

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

Is ShipPeek an official Central Transport API?

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

Start with Unified API Book demo