Carriers / CRH Transportation

Handle CRH Transportation shipments through one Unified API

If CRH Transportation 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

CRHM carrier code

LTL freight shipment type

Carrier-specific handling

What ShipPeek handles for CRH Transportation

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

Workflow mapping

ShipPeek maps CRH Transportation 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 CRH Transportation in ShipPeek

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

Tracking

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

Rates

Request eligible CRH Transportation 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, CRH Transportation-aware routing

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

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

Unified API example

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

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

How it works

How a CRH Transportation request moves through ShipPeek

Send one request

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

Apply carrier setup

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

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

Quote eligible CRH Transportation lanes in checkout, OMS, TMS, or WMS flows

Track CRH Transportation shipments and surface status changes to operators or customers

Pull CRH Transportation BOLs, delivery receipts, and shipment documents into support workflows

Compare CRH Transportation with other enabled carriers from the same request model

Reduce portal checks, email attachments, and spreadsheet handoffs

Add more carriers without redesigning the CRH Transportation integration

FAQ

Questions about CRH Transportation

How does ShipPeek support CRH Transportation?

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

Can I track CRH Transportation shipments?

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

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

What does ShipPeek handle for CRH Transportation?

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

Is ShipPeek an official CRH Transportation API?

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

Start with Unified API Book demo