Carriers / XGS

Handle XGS shipments through one Unified API

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

XGSI carrier code

LTL freight shipment type

Carrier-specific handling

What ShipPeek handles for XGS

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

Workflow mapping

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

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

Tracking

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

Rates

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

Booking

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

Labels

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

Documents

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

Integration model

One API contract, XGS-aware routing

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

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

Unified API example

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

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

How it works

How a XGS request moves through ShipPeek

Send one request

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

Apply carrier setup

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

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

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

Track XGS shipments and surface status changes to operators or customers

Create XGS bookings when your account and service rules allow it

Retrieve XGS labels without a carrier-specific backend path

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

Compare XGS with other enabled carriers from the same request model

Reduce portal checks, email attachments, and spreadsheet handoffs

Add more carriers without redesigning the XGS integration

FAQ

Questions about XGS

How does ShipPeek support XGS?

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

Can I track XGS shipments?

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

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

Can I get XGS labels or documents?

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

What does ShipPeek handle for XGS?

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

Is ShipPeek an official XGS API?

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

Start with Unified API Book demo