Amazon Hosting Webinar to Guide Sellers Through MWS to SP-API Migration
Amazon will retire Marketplace Web Service (MWS) by the end of 2024, making the shift to the Selling Partner API (SP‑API) mandatory. A live webinar in early May will demo the new developer console, OAuth 2.0 authentication and sandbox testing. Rate‑limit enforcement will move from a single aggregate limit to per‑operation caps.
Overview
Amazon is hosting a live webinar to guide sellers and developers through the required shift from the legacy Marketplace Web Service (MWS) to the newer Selling Partner API (SP‑API). The session, scheduled for early May, will outline migration schedules, demonstrate the new developer console, and walk participants through sandbox testing. Sellers who rely on automated feeds for inventory, orders, or reporting should attend to avoid future service interruptions.
Key Points
- Migration deadline — Amazon has announced that MWS will be fully retired by the end of 2024, making the transition to SP‑API mandatory for all active integrations.
- Security upgrade — SP‑API uses OAuth 2.0 and fine‑grained role permissions, providing stronger protection than the key‑based authentication used by MWS.
- Rate‑limit changes — The new API enforces per‑operation throttling limits that differ from MWS’s aggregate limits, requiring developers to redesign request pacing.
- Developer console demo — The webinar includes a live walkthrough of the SP‑API console, showing how to create an application, generate access tokens, and view usage metrics.
- Sandbox validation — Attendees will see a step‑by‑step example of submitting a test order retrieval request in Amazon’s sandbox before moving to production.
- Live Q&A — Both business leaders and technical staff can pose real‑world migration questions, from timeline concerns to third‑party tool compatibility.
How the Migration Works
- Register a new SP‑API application — In the developer console, create an app profile, select the required APIs (e.g., Orders, Listings), and obtain a client ID and client secret. Example: A seller who previously used the MWS “GetOrder” endpoint creates an SP‑API “Orders” app and receives a client ID of
ABC123. - Implement OAuth 2.0 authentication — Replace the MWS access key/secret pair with an OAuth flow that exchanges the client ID/secret for an access token and refresh token.
Analysis & Recommendations
Why This Matters
If sellers do not migrate before the 2024 cutoff, automated feeds will fail, causing order processing delays and loss of reporting data. SP‑API’s OAuth 2.0 and finer rate limits require code changes and monitoring, so early preparation avoids service interruptions.
Key Takeaways
- MWS retirement deadline is the end of 2024, requiring all active integrations to move to SP‑API.
- The webinar scheduled for early May will show how to create an SP‑API app, generate OAuth tokens, and use the sandbox.
- SP‑API replaces key‑based auth with OAuth 2.0 and introduces fine‑grained role permissions.
- Rate limits are now per‑operation, e.g., 2 rps for report listings and 5 rps for report generation.
Recommended Actions
- →Register a new SP‑API application in Seller Central > Developer Console before the end of Q2 and note the client ID/secret.
- →Replace MWS key/secret authentication with OAuth 2.0 token flow using the new client credentials; update code to store refresh tokens.
- →Run end‑to‑end tests in Seller Central > SP‑API Sandbox for all used endpoints, then switch URLs to production and monitor throttling alerts.
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!