Carriers / Priority1

Handle Priority1 shipments through one Unified API

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

PRIORITY1 carrier code

LTL freight shipment type

Carrier-specific handling

What ShipPeek handles for Priority1

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

Workflow mapping

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

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

Tracking

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

Rates

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

Booking

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

Labels

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

Documents

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

Integration model

One API contract, Priority1-aware routing

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

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

Unified API example

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

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

How it works

How a Priority1 request moves through ShipPeek

Send one request

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

Apply carrier setup

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

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

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

Track Priority1 shipments and surface status changes to operators or customers

Create Priority1 bookings when your account and service rules allow it

Retrieve Priority1 labels without a carrier-specific backend path

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

Compare Priority1 with other enabled carriers from the same request model

Reduce portal checks, email attachments, and spreadsheet handoffs

Add more carriers without redesigning the Priority1 integration

FAQ

Questions about Priority1

How does ShipPeek support Priority1?

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

Can I track Priority1 shipments?

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

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

Can I get Priority1 labels or documents?

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

What does ShipPeek handle for Priority1?

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

Is ShipPeek an official Priority1 API?

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

Start with Unified API Book demo