Create Parcels

This endpoint is not available

POST /api/parcel/push-parcel-orders is not currently served. The path is not registered, so requests to it fail at the routing layer — you will receive a 404, not the standard {Code, Message, Data} envelope.

Use Create Single Parcel instead: it registers a parcel synchronously and returns its WMG tracking number in the same response, which removes the need for a separate Get Tracking No call.

This page is kept for reference only. Do not build against it, and contact tech@wmg-group.com before planning any integration around batch creation.

API Overview

The batch endpoint was intended to pre-populate parcel data asynchronously so that labels could be produced faster afterwards, in a three-step flow: create parcels in bulk, look up each WMG tracking number, then fetch the labels.

That flow is superseded. Create Single Parcel returns the WMG tracking number immediately, so the two-step lookup is unnecessary:

1. Create Single Parcel — returns Data.WmgTrackingNo
2. Get Shipping Label PDF — using that tracking number

Request Information

• Method: POST
• Path: /api/parcel/push-parcel-orders — not registered
• Authentication: Bearer Token

Migrating to Create Single Parcel

If you previously integrated against the batch endpoint, the migration is mechanical:

Batch flow	Replacement
One request carrying an Orders array	One Create Single Parcel request per parcel
Get Tracking No to resolve each WMG tracking number afterwards	Not needed — Data.WmgTrackingNo is returned by the create call
Per-item errors collected in the response	Each parcel succeeds or fails on its own request, with Code and Message for that parcel

The field names of a single parcel are unchanged, so an element of the old Orders array can be sent as the body of Create Single Parcel as-is. Send the requests with a small amount of concurrency and handle each result individually.

Notes

• Because the route is not registered, no authentication, validation or business error from this documentation applies — the request never reaches the application.
• Nothing about your account or data changes as a result of calling it.
• If batch ingestion matters for your volumes, raise it with tech@wmg-group.com rather than retrying this path.