Amazon Selling Partner API (SP-API): What Replaced MWS and Why It Matters

Table of Contents

• Amazon MWS Is Dead - Here’s What Replaced It
• What SP-API Actually Does for Your Business
• The Tools That Run on SP-API
• SP-API Access: What You Need to Know
• 2026 Fee Changes and What They Mean for Sellers
• When Direct API Access Makes Sense
• FAQ

If you’re still hearing about Amazon Marketplace Web Service (MWS), you’re reading outdated information. MWS was fully sunset on March 31, 2024, after a phased deprecation that started in 2021. Its replacement - the Selling Partner API (SP-API) - has been live since 2020, and every tool, integration, and automation that touches your seller account now runs through it.

Here’s what most sellers get wrong about this transition: they think it doesn’t affect them because they never used MWS directly. It does. The shift to SP-API fundamentally changed what third-party tools can do - and how fast they can do it. If your repricer, inventory tool, or analytics dashboard got noticeably better in the last three years, SP-API is the reason.

What SP-API Actually Does for Your Business

The biggest upgrade for sellers wasn’t the technology - it was the security model. MWS used a single static token that gave broad access to your entire account. Every tool you authorized got the same all-or-nothing key. SP-API uses OAuth 2.0, which forces apps to request only the specific permissions they need. You can see exactly what each tool accesses from your Seller Account Settings, and revoke access with one click.

But the speed improvement matters more to your bottom line. Under MWS, repricing tools polled Amazon for competitor changes on a delay - typically 10-15 minutes between checks. SP-API’s Notifications API pushes changes to tools instantly. At 10,000 SKUs, that 10-minute delay meant missing 60+ competitor price moves per hour. Cut that to seconds and your Buy Box win rate shifts 2-4 points - which, on a catalog doing $500K/month, translates to real revenue.

SP-API also opened up data that MWS never exposed. The Data Kiosk API delivers custom analytics via GraphQL. The Reports API now provides hourly sales and traffic granularity instead of daily snapshots. Search Terms Reports reveal exactly which keywords drive traffic to your listings. These aren’t theoretical improvements - they’re the reason modern seller tools can do things like adjusting ad bids the same afternoon that conversion rates drop, instead of discovering the problem the next morning.

The Tools That Run on SP-API

If your ops team uses a repricer, inventory sync, or ads tool, you’re already on SP-API - even if no one on your team writes code.

Repricing is where the API change hit hardest. Tools like Feedvisor and Seller Snap connect to the Pricing API for real-time Buy Box prices and fee estimates, then push thousands of price adjustments per hour through the Listings Items API. The difference from the MWS era isn’t just speed - it’s the data behind each decision. A repricing tool can now factor in hourly traffic trends, competitor stock levels, and advertising costs in the same pricing loop. That wasn’t possible when data arrived in daily batches.

Inventory management tools gained hourly visibility into sellable units, stranded inventory, and inventory health metrics. If a stockout costs you roughly $150/day per ASIN - a reasonable estimate for a product doing 10 units/day at $15 margin - then catching a stock issue six hours earlier saves you $37 per incident. Across a 500-SKU catalog with even occasional stockout risk, that adds up.

Bulk listing migrated to the JSON_LISTINGS_FEED format after Amazon deprecated legacy XML and flat file feed types through the API in July 2025. The new format is 30-40% more efficient in data transmission with better error messages. If you manage listings through Seller Central’s upload interface, nothing changed for you - flat file uploads through the Seller Central UI still work. The deprecation only hit API-submitted feeds.

The Orders API and FBA APIs handle real-time order tracking, shipment confirmation, and returns. For sellers using Multi-Channel Fulfillment, these APIs route orders from Shopify or Walmart through Amazon’s fulfillment centers without manual intervention.

SP-API Access: What You Need to Know

Most sellers interact with SP-API through third-party tools and never think about the API itself. You install a tool, authorize it through Amazon’s OAuth flow - which shows you exactly what permissions you’re granting - and the tool handles the rest. That’s fine. That’s how it should work.

For sellers who want to build custom integrations, you need a Professional seller account ($39.99/month), developer registration through Amazon’s portal, an AWS account for credentials, and the technical ability to work with REST APIs and JSON. For your own account, there are no additional API fees beyond the Professional plan.

Don’t go this route unless you have a genuinely unique workflow that no existing tool covers and the development resources to maintain it long-term. The initial setup takes weeks, and Amazon’s rate limits mean you’ll need robust retry logic. At $39.99/month for Professional plus roughly $5,000-$15,000 in initial development costs for a basic integration, the breakeven against a $200/month SaaS tool is 2-6 years. Most sellers don’t have workflows unique enough to justify that.

2026 Fee Changes and What They Mean for Sellers

Amazon started charging third-party developers for SP-API access in 2026:

Fee	Amount	Effective Date
Annual developer subscription	$1,400/year	January 31, 2026
Basic tier (2.5M GET calls/month)	Included	April 30, 2026
Pro tier (25M GET calls/month)	$1,000/month	April 30, 2026
Plus tier (250M GET calls/month)	$10,000/month	April 30, 2026
Overage beyond tier	$0.40 per 1,000 calls	April 30, 2026

PUT, PATCH, and POST requests remain unmetered.

You won’t pay these fees directly - but the tools you use will, and you’ll see it in subscription pricing. Here’s where the math gets interesting for sellers running multiple tools: a repricing tool monitoring 50,000 ASINs across a provider’s client base might make 5 million GET calls/month - pushing into the Pro tier at $1,000/month. Spread across clients, that’s maybe $20-$50/month added per seller. Stack three or four tools that each pull overlapping data, and the redundant API costs add up.

The practical takeaway: consolidating onto fewer, more capable platforms saves you more money in 2026 than it did before. One platform that handles repricing, inventory, and analytics makes one set of API calls. Three separate tools make three.

Sellers using SP-API for their own accounts are exempt from these fees entirely.

When Direct API Access Makes Sense

Three scenarios justify the development investment:

You’re managing 10,000+ SKUs with frequent catalog changes and flat file uploads through Seller Central are taking your team hours per week. At that volume, SP-API’s JSON_LISTINGS_FEED with automated error handling pays for itself in labor savings within months.

You sell across Amazon, Shopify, Walmart, and your own site, and inventory discrepancies are costing you oversells and stockouts. A custom SP-API integration (or a multichannel tool built on it) keeps quantities synchronized in near-real-time across all channels.

Your pricing strategy depends on proprietary data that no off-the-shelf repricer can incorporate - supplier cost fluctuations, seasonal demand models, or custom margin calculations by category.

If none of these apply, spend your time optimizing your listings and cleaning up your inventory instead. The API isn’t where most sellers gain their edge - and that’s not going to change.

FAQ

Is Amazon MWS still available?

No. MWS was fully sunset on March 31, 2024. All API functionality runs through SP-API now. If a tool still references MWS, it hasn’t been updated in over two years - and that should concern you.

Do I need SP-API access to sell on Amazon?

Not directly. You manage your business through Seller Central, and SP-API works behind the scenes through whatever tools you install. Most sellers use SP-API without ever knowing it.

Does SP-API cost money for sellers?

Not for sellers using it for their own accounts - just the $39.99/month Professional plan. The 2026 developer fees ($1,400/year plus usage tiers) apply to third-party tool providers, who may pass costs through as subscription increases.

What happened to Amazon Webstore and Checkout by Amazon?

Amazon Webstore shut down in 2015. Checkout by Amazon is also gone. Brand-registered sellers now use Amazon Brand Stores for custom storefronts - a completely different system unrelated to SP-API.

Can Individual sellers use SP-API?

Not directly. Developer registration requires a Professional seller account. But Individual sellers can use third-party tools that connect via SP-API - the tools handle the API connection on their behalf.