Amazon's Final MWS Shutdown Is Coming: Migrate Your Private Apps to SP-API Now
Amazon will deactivate the final MWS endpoints in early 2024, forcing all private integrations to switch to the Selling Partner API. The migration requires registering as a developer, creating an OAuth 2.0 client, and remapping calls such as ListOrders to the new /orders/v0/orders JSON endpoint.
Overview
Amazon will deactivate the final Marketplace Web Service (MWS) endpoints in early 2024, ending support for the legacy API that many sellers still use for private integrations. Any custom‑built tool that relies on MWS will stop working once the shutdown occurs, threatening inventory syncs, order processing, and reporting. Sellers must migrate those applications to the Selling Partner API (SP‑API) or replace them with an Amazon‑approved third‑party solution immediately.
Key Points
- MWS shutdown date announced — Amazon has set a firm cut‑off for the remaining MWS endpoints, after a multi‑year deprecation schedule.
- Private apps will fail — Custom scripts that pull orders, update stock, or generate dashboards will return authentication errors once MWS is disabled.
- Two migration routes — Sellers can either rebuild their integration on SP‑API or adopt a ready‑made app from the Amazon Appstore that already uses SP‑API.
- Third‑party apps are safe — Vendors such as Helium 10, Jungle Scout and SellerBoard completed their migrations, so users of those platforms face no interruption.
- High‑volume sellers at greatest risk – Those who depend on bespoke automation to handle thousands of SKUs or daily order spikes will experience the most severe disruption if they do not act.
How SP‑API Migration Works
- Register as a developer — Log into Seller Central, navigate to the “Developer Profile” page, and create a new developer account. Example: A seller who previously used a freelance developer registers themselves, receives a developer ID, and can now create SP‑API applications.
- Create a new SP‑API application — Within the developer console, click “Add a new application,” provide a name (e.g., “MyInventorySync”), and generate the required OAuth 2.0 client credentials. Example: The generated client ID and client secret replace the old MWS access key and secret key in the code base.
- Configure OAuth 2.0 permissions — Select the specific scopes needed for your workflow, such as , , or .
Analysis & Recommendations
Why This Matters
Private scripts that pull orders, update inventory, or generate reports will return authentication errors once MWS is disabled, risking lost sales and inventory mismatches. High‑volume sellers handling thousands of SKUs are especially vulnerable, as any downtime can quickly affect Buy Box eligibility and order defect rates.
Key Takeaways
- MWS shutdown is set for early 2024, ending all legacy endpoint access.
- SP-API uses OAuth 2.0 client ID and secret instead of MWS access keys.
- New rate limit is 6 calls per second per marketplace, with scoped permissions like sellingpartnerapi::orders.
- Third‑party tools such as Helium 10, Jungle Scout and SellerBoard have already completed the migration.
Recommended Actions
- →Log into Seller Central > Settings > Developer Profile and register a new developer account to obtain a developer ID.
- →In the developer console, click ‘Add a new application’, enter a name (e.g., MyInventorySync), and generate OAuth 2.0 client ID and secret.
- →Map each MWS call (e.g., ListOrders) to its SP‑API counterpart (/orders/v0/orders), update code for JSON responses and pagination, then test in the...
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!