Carriers / ShipEngine LTL

Handle ShipEngine LTL shipments through one Unified API

If ShipEngine LTL 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

SHIPENGINE_LTL carrier code

LTL freight shipment type

Carrier-specific handling

What ShipPeek handles for ShipEngine LTL

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

Workflow mapping

ShipPeek maps ShipEngine LTL 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 ShipEngine LTL in ShipPeek

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

Tracking

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

Rates

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

Booking

Create supported ShipEngine LTL 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, ShipEngine LTL-aware routing

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

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

Unified API example

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

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

How it works

How a ShipEngine LTL request moves through ShipPeek

Send one request

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

Apply carrier setup

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

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

Quote eligible ShipEngine LTL lanes in checkout, OMS, TMS, or WMS flows

Track ShipEngine LTL shipments and surface status changes to operators or customers

Create ShipEngine LTL bookings when your account and service rules allow it

Pull ShipEngine LTL BOLs, delivery receipts, and shipment documents into support workflows

Compare ShipEngine LTL with other enabled carriers from the same request model

Reduce portal checks, email attachments, and spreadsheet handoffs

Add more carriers without redesigning the ShipEngine LTL integration

FAQ

Questions about ShipEngine LTL

How does ShipPeek support ShipEngine LTL?

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

Can I track ShipEngine LTL shipments?

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

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

Can I get ShipEngine LTL labels or documents?

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

What does ShipPeek handle for ShipEngine LTL?

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

Is ShipPeek an official ShipEngine LTL API?

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

Start with Unified API Book demo