Carriers / Metropolitan Warehouse & Delivery

Handle Metropolitan Warehouse & Delivery shipments through one Unified API

If Metropolitan Warehouse & Delivery 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

MWDP carrier code

LTL freight shipment type

Carrier-specific handling

What ShipPeek handles for Metropolitan Warehouse & Delivery

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

Workflow mapping

ShipPeek maps Metropolitan Warehouse & Delivery 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 Metropolitan Warehouse & Delivery in ShipPeek

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

Rates

Request eligible Metropolitan Warehouse & Delivery rates without creating a carrier-specific quoting path.

Booking

Create supported Metropolitan Warehouse & Delivery 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, Metropolitan Warehouse & Delivery-aware routing

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

Request eligible Metropolitan Warehouse & Delivery rates through the Unified API
Create Metropolitan Warehouse & Delivery bookings where your carrier account allows it
Pull Metropolitan Warehouse & Delivery BOLs and delivery documents into your system
Keep Metropolitan Warehouse & Delivery inside the same API contract as the rest of your carriers

Unified API example

# Use carrier identifier mwdp
# inside ShipPeek's standard rate,
# booking, or shipment workflows.

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

How it works

How a Metropolitan Warehouse & Delivery request moves through ShipPeek

Send one request

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

Apply carrier setup

ShipPeek uses the enabled Metropolitan Warehouse & Delivery configuration, including carrier identifier mwdp, 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 Metropolitan Warehouse & Delivery fits in your operation

Confirm how Metropolitan Warehouse & Delivery can fit into quoting, operations, customer support, and shipment visibility workflows.

Quote eligible Metropolitan Warehouse & Delivery lanes in checkout, OMS, TMS, or WMS flows

Create Metropolitan Warehouse & Delivery bookings when your account and service rules allow it

Pull Metropolitan Warehouse & Delivery BOLs, delivery receipts, and shipment documents into support workflows

Compare Metropolitan Warehouse & Delivery with other enabled carriers from the same request model

Reduce portal checks, email attachments, and spreadsheet handoffs

Add more carriers without redesigning the Metropolitan Warehouse & Delivery integration

FAQ

Questions about Metropolitan Warehouse & Delivery

How does ShipPeek support Metropolitan Warehouse & Delivery?

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

Can I track Metropolitan Warehouse & Delivery shipments?

Tracking is not currently listed for this carrier profile. Other enabled workflows are shown above.

Can ShipPeek get Metropolitan Warehouse & Delivery 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 Metropolitan Warehouse & Delivery bookings?

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

Can I get Metropolitan Warehouse & Delivery labels or documents?

ShipPeek can return Metropolitan Warehouse & Delivery BOLs, delivery receipts, or carrier documents where available through enabled Unified API workflows.

What does ShipPeek handle for Metropolitan Warehouse & Delivery?

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 Metropolitan Warehouse & Delivery and your carrier account setup.

Is ShipPeek an official Metropolitan Warehouse & Delivery API?

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

Start with Unified API Book demo