New: Introducing Amazon Warehousing and Distribution API v2024-05-09
Amazon released the AWD API version 2024‑05‑09, activating on June 21. It adds GET /awd/inventory/v2024-05-09/sku/{sellerSku} returning exact availableQuantity and GET /awd/shipments/v2024-05-09/shipment/{shipmentId} returning ordered status codes. Calls are capped at 10 requests/second per account.
Overview
Amazon has released a refreshed version of its Warehousing and Distribution (AWD) API, identified as version 2024‑05‑09. The new endpoints become publicly reachable on June 21, delivering live inventory counts from AWD fulfillment sites and granular status updates for inbound shipments. Sellers and third‑party developers can now pull these data streams into their own systems, allowing faster stock‑level decisions and tighter logistics oversight.
Key Points
- Live inventory query — The API returns the exact on‑hand quantity for any SKU stored in an AWD center; for instance, a seller can see that 1,250 units of a winter coat are presently stocked at the Dallas hub.
- Inbound shipment milestones — Each request provides a chronological list of events for a shipment, such as “Loaded on carrier” on May 30 and “Arrived at AWD facility” on June 2 for a pallet containing 500 new units.
- Unified access role — Both marketplace sellers and external software partners use the same AWD role, meaning a third‑party inventory‑optimization platform can retrieve data for a seller without needing a separate credential set.
- June 21 activation — All qualified accounts will see the new endpoints on this date, giving sellers a clear deadline to migrate before the legacy version is retired.
- Standard REST design — Calls follow the existing SP‑API pattern, using JSON bodies and OAuth 2.0 tokens, so current SDKs require only minor adjustments to accommodate the new version.
How the New AWD API Works
- Obtain an OAuth 2.0 token — The seller authenticates through the SP‑API login flow; for example, a vendor using the Java SDK invokes
loginWithRefreshToken()to receive a token that remains valid for 60 minutes. - Request inventory data — With the token, the seller sends a GET request to
/awd/inventory/v2024-05-09/sku/{sellerSku}. The response includes fields such aswarehouseId,availableQuantity, andlastUpdated. A sample payload might return .
Analysis & Recommendations
Why This Matters
The real‑time inventory feed lets sellers query exact stock (e.g., 1,250 units at Dallas) at the moment of a flash sale, preventing stockouts. Shipment milestone data enables automated alerts for delays, reducing manual follow‑up and improving replenishment timing.
Key Takeaways
- Version 2024‑05‑09 introduces live inventory endpoint /awd/inventory/v2024-05-09/sku/{sellerSku} with fields like availableQuantity.
- New inbound shipment endpoint /awd/shipments/v2024-05-09/shipment/{shipmentId} returns an ordered array of status codes and timestamps.
- All accounts gain access on June 21; legacy AWD endpoints will be retired thereafter.
- Rate limit is 10 calls per second per account; responses include nextToken for pagination and require exponential back‑off on throttling.
Recommended Actions
- →Update your SP‑API SDK to call /awd/inventory/v2024-05-09/sku/{sellerSku} and /awd/shipments/v2024-05-09/shipment/{shipmentId}.
- →Test OAuth 2.0 token flow in Seller Central > Developer Central and verify inventory payloads return availableQuantity.
- →Implement pagination handling with nextToken and add exponential back‑off to stay within the 10 req/sec limit.
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!