SP-API implementation

Vendor Shipments API payloads, preflighted before the 202 response

Schema validity is the first gate. Shipment type, identifiers, carton tracking, quantities, timing, and physical reconciliation are the next ones.

Reviewed 2026-07-16Rule pack 2026.07.16Independent research

Direct answer

The Vendor Retail Procurement Shipments API exchanges shipment documents for Amazon vendors. SubmitShipmentConfirmations accepts a request containing one or more shipment confirmation objects. The current public model requires party, identifier, confirmation date, type, and shipped-item data; Amazon’s tutorial adds operational rules such as pre-receipt timing, BOL requirements for FTL/LTL, small-parcel carton confirmation, and SSCC handling.

Run this check on your own 856 or API payload

Validate against the current model first

The application repository stores the current upstream `vendorShipments.json` research fixture. The runtime validator enforces the high-value required fields and enum values directly, while the fixture makes future model changes reviewable in source control.

The tool reports JSON Pointer-style locations such as `$.shipmentConfirmations[0].sellingParty.partyId`, so a developer can fix the payload without searching a generic error list.

Business rules that are not just JSON schema

Shipment confirmations must arrive before the product is received.
FTL and LTL confirmations require a BOL value that matches the shipment document.
Small-parcel confirmations are required for each package/carton; carton tracking is checked when carton detail is supplied.
Shipment and SSCC identifiers have documented uniqueness periods.
Replacement submissions reuse the original shipment identifier and selling party.
Perishable item details belong at the relevant packed-item level.

Treat 202 as acceptance for processing, not proof of receiving accuracy

The operation returns HTTP 202 when the request is accepted for processing. Amazon documents verifying the resulting status in Vendor Central or through the Transaction Status API. A successful HTTP response does not reconcile the message to the physical shipment.

Keep the preflight result ID and content hash with your submission log. That gives support teams a stable link between the file that was checked and the payload that was sent without retaining raw document content by default.

Questions

Common implementation questions

Does Shipment Sentry call the Amazon API?

No. The current product validates the request before submission. It does not require SP-API credentials.

Is the official OpenAPI model included?

A research copy of Amazon’s public model is stored with source attribution. Production validation code enforces a curated, tested subset plus documented business rules.

Primary sources

Public sources cannot establish every account-specific EDI rule. Current Vendor Central documentation and your trading-partner agreement remain controlling.