April 2022 SP-API Release Announcement
In April 2022 Amazon released a new SP‑API generation that replaces MWS, adds OAuth 2.0 (Login with Amazon) authentication, and enforces per‑resource throttling (e.g., 10 calls/sec for ListingsItems). Legacy MWS calls stop working after the September 30 2022 deadline, returning 404 errors. The new endpoints return richer payloads such as line‑item tax breakdowns and shipment‑tracking events.
Overview
In April 2022 Amazon launched a new generation of its Selling Partner API (SP‑API), retiring many of the long‑standing MWS endpoints that sellers and third‑party developers have relied on for years. The upgrade brings OAuth 2.0 authentication, richer data structures, and stricter throttling rules, meaning that anyone still using the legacy MWS calls must migrate quickly to avoid service interruptions. Sellers who fail to transition before the September 30 2022 deadline risk losing access to order, inventory, and financial data essential for daily operations.
Key Points
- Unified OAuth 2.0 login — The SP‑API now authenticates exclusively with Login with Amazon (LWA) tokens, so merchants no longer need to manage separate AWS access keys for each marketplace, a relief for operators handling dozens of accounts.
- Expanded payloads — Endpoints such as
GET /orders/v0/ordersreturn nested shipment‑tracking events, line‑item tax breakdowns, and item‑level fee details that were unavailable in the older MWS responses, enabling finer‑grained analytics. - Per‑resource throttling — Amazon enforces a rolling‑second limit on each API resource (for example, 10 calls per second for ListingsItems), and includes
Retry‑Afterguidance when the limit is exceeded, forcing integrations to implement back‑off logic. - Standardized error schema — All error responses now contain a structured
errorsarray with a machine‑readablecode, a human‑friendlymessage, and optionaldetails, allowing developers to differentiate transient network glitches from permanent permission issues. - Hard migration deadline — Amazon has set September 30 2022 as the final cut‑off; after that date any request to a legacy MWS endpoint returns a 404 error, making the SP‑API the sole gateway for marketplace data.
- Sandbox‑first testing — The updated platform provides a dedicated sandbox environment that mirrors production rate limits and data models, encouraging sellers to validate their code before going live.
Analysis & Recommendations
Why This Matters
If a seller continues using MWS after September 30 2022, API calls will fail, halting order imports and inventory syncs. The OAuth 2.0 flow simplifies credential management across marketplaces, while the stricter throttling and Retry‑After headers require back‑off logic to avoid 429 errors, directly affecting integration reliability.
Key Takeaways
- OAuth 2.0 (Login with Amazon) is now the only authentication method for SP‑API.
- Legacy MWS endpoints return 404 after September 30 2022, making migration mandatory.
- Per‑resource throttling limits, e.g., 10 calls/sec for ListingsItems, with Retry‑After guidance on 429 responses.
- New payloads include nested shipment‑tracking events, line‑item tax breakdowns, and fee details.
Recommended Actions
- →In Seller Central > Developer Central, register LWA credentials and note the client ID/secret.
- →Update integration code to replace MWS keys with a token fetch to the OAuth token endpoint and add logic to read x-amzn-RateLimit headers and Retry...
- →Test all changed endpoints in the SP‑API sandbox (Developer Console > SP‑API Sandbox) before deploying to production.
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!