Update: Vendor Shipments API v1 now supports the ability to retrieve small parcel labels
Amazon's Vendor Shipments API v1 now includes a GetShipmentLabels endpoint (/vendor/shipping/v1/shipments/{shipmentId}/labels) that returns UPS, FedEx, etc. small‑parcel labels as PDF or PNG via a pre‑signed URL or Base64. Access requires the Amazon Fulfillment Role (sellingpartnerapi::vendor_fulfillment scope).
Overview
Amazon has expanded the Vendor Shipments API v1 with a new operation that returns small‑parcel shipping labels on demand. The GetShipmentLabels endpoint went live in the latest release and is gated by the Amazon Fulfillment Role. Vendors that ship inventory to Amazon fulfillment centers can now generate carrier‑specific labels programmatically, cutting manual steps and keeping outbound logistics aligned with Amazon’s receiving standards.
Key Points
- New endpoint added — The API now offers a
GetShipmentLabelscall that delivers printable small‑parcel labels for UPS, FedEx, and other carriers. - Role‑based access — Only IAM users or applications granted the Amazon Fulfillment Role can invoke the endpoint; missing the role triggers a permission error.
- Multiple formats — Labels are returned as PDF or PNG files, either via a pre‑signed URL or as a Base64‑encoded payload, ready for immediate printing.
- Seamless integration — Existing workflows that already use Vendor Retail Procurement APIs can insert a single additional request to fetch labels, eliminating the need for a separate shipping system.
- On‑demand generation — Labels are created at the moment of request, allowing vendors to request them minutes before a carrier pickup and thereby tighten shipment windows.
How GetShipmentLabels Works
-
Authenticate and authorize — The vendor’s application obtains an LWA access token and includes the
sellingpartnerapi::vendor_fulfillmentscope, which reflects the Amazon Fulfillment Role.- Example: A Java service calls the LWA token endpoint, receives a token, and adds
sellingpartnerapi::vendor_fulfillmentto the Authorization header before any API call.
- Example: A Java service calls the LWA token endpoint, receives a token, and adds
-
Submit the label request — A POST request is sent to
/vendor/shipping/v1/shipments/{shipmentId}/labels, supplying the shipment identifier, desired carrier code, and label format.
Analysis & Recommendations
Why This Matters
Vendors can programmatically generate carrier‑specific labels minutes before pickup, eliminating manual label creation in Seller Central. This reduces delays, lowers mis‑label risk, and aligns outbound shipments with carrier schedules, freeing staff for higher‑value tasks.
Key Takeaways
- GetShipmentLabels is a new POST call at /vendor/shipping/v1/shipments/{shipmentId}/labels.
- The endpoint is gated by the Amazon Fulfillment Role; missing the role returns a permission error.
- Labels are returned as PDF or PNG via a temporary S3 URL or Base64 payload.
- Supports major carriers such as UPS and FedEx and can be invoked on‑demand shortly before carrier pickup.
Recommended Actions
- →Open the AWS IAM console, attach the AmazonFulfillmentFullAccess policy to the service account used for SP‑API calls, and verify the token includes...
- →Update your integration to POST to /vendor/shipping/v1/shipments/{shipmentId}/labels with JSON fields carrierCode and labelFormat, then handle the ...
- →Switch the base URL to sandbox.api.amazon.com, run end‑to‑end tests with the sandbox shipment IDs, and confirm label retrieval before deploying to ...
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!