Amazon SP-API Fees: The $1,400 Plan Amazon Cancelled
Amazon planned a $1,400 yearly SP-API fee plus usage fees for third-party developers in 2026, then dropped it in May. What it means for your tool costs.
On this page
Subscribe to my YouTube channel
Live walkthroughs, listing teardowns and answers to seller questions.
Update, October 2026: the paid SP-API plan is off. In mid-May 2026 Amazon published a notice titled “Cancellation of Third-Party Developer Selling Partner API (SP-API) Fees”, saying it “will not move forward with the SP-API usage and annual fees at this time.” This article explains what was planned, what changed, and what it means for the tools you pay for.
In November 2025, Amazon announced that the Selling Partner API (SP-API) would stop being free for third-party developers: a $1,400 annual subscription from January 31, 2026, plus monthly usage fees based on API calls from April 30, 2026. The fees would have been paid by the companies behind repricers, analytics dashboards and other seller tools — not by sellers directly — which is why many sellers expected their software subscriptions to go up.
Key Takeaways
- Amazon’s plan: $1,400 per year for every third-party developer, plus tiered fees for GET calls above an included allowance.
- Sellers and vendors using the SP-API only for their own business were not going to be charged.
- In mid-May 2026 Amazon cancelled both the annual and the usage fees “at this time”.
- As of October 2026 there is no SP-API fee, so it is not a valid reason for a tool vendor to raise prices.
- “At this time” leaves the door open. A different monetization plan could come back later.
What the SP-API Is
The Selling Partner API is Amazon’s official interface for outside software to read and write seller data: orders, inventory, listings, reports and fees. You can always log into Seller Central and download a report by hand. The API is the automated version: your tools request the same data on a schedule and act on it.
Most of a typical tool stack depends on it — repricers, profit dashboards, inventory and replenishment planners, listing tools. Advertising data is different: PPC tools work through the separate Amazon Ads API, which was not part of the fee plan.
What Amazon Had Planned
According to coverage of the November 3, 2025 announcement:
| Element | Planned terms |
|---|---|
| Annual subscription | $1,400 per year per third-party developer, from January 31, 2026 |
| Basic usage tier | 2.5 million GET calls per month included |
| Pro tier | $1,000 per month for 25 million GET calls |
| Plus tier | $10,000 per month for 250 million GET calls |
| Enterprise | Negotiated with Amazon |
| Overage | $0.40 per 1,000 calls above the tier limit |
| Usage fees start | April 30, 2026 |
Only GET calls (reading data) were to be metered. Write calls such as PUT, PATCH and POST stayed outside the tiers, subject to normal rate limits. Sellers who build their own integration for their own store were exempt.
For a large vendor, $1,400 a year is negligible. The usage tiers were the bigger issue for data-heavy tools that poll Amazon constantly. Small tools with few customers were the most exposed.
What Happened Next
After pushback from developers, Amazon published its cancellation notice in mid-May 2026. The key line: Amazon “will not move forward with the SP-API usage and annual fees at this time.” It also said it would remove the fee preview dashboard from the Solution Provider Portal, and that developers who had already added a credit card could delete it there.
So, as of October 2026, third-party developers do not pay Amazon for SP-API access, and neither do sellers.
What This Means for Your Tool Costs
No SP-API fee means no SP-API surcharge. If a vendor raised your price or added a line item and pointed to Amazon’s API fees, ask what that charge covers now. The cost they were planning for does not exist.
Price changes still happen for other reasons. Hosting, AI features, support and plain repricing of the product are legitimate reasons for a vendor to charge more. Judge the tool on what it delivers, not on the label of the increase.
Plan for a possible return. “At this time” is not “never”. Amazon has shown it is willing to charge for the software layer, and a revised plan could come back in a different form. Small tools with thin margins would again be the most exposed.
For how I think about recurring software costs in unit economics, see my true cost per unit breakdown: small monthly charges add up the same way small per-unit fees do.
Why Amazon Proposed It (My Take)
Amazon did not need $1,400 a year from developers as revenue; the amount is tiny for a company of its size. Two explanations seem more plausible to me — both my opinion, not Amazon’s statements:
- Load and quality control. Building a working Amazon tool has become much easier, and usage-based pricing is a clean way to discourage inefficient, high-volume polling.
- Testing a data business. Charging for data access is high-margin revenue. The plan may have been a first, cautious step, and the cancellation does not mean the idea is gone.
Why Doesn’t Amazon Build These Tools Itself?
This genuinely puzzles me. Amazon has the data and the engineers, yet a large third-party industry sells repricers, profit dashboards and PPC managers. My two guesses: polished seller tooling is simply not a priority compared with fees and ads, and a radically simpler native PPC tool could reduce the ad spend that newer sellers burn while learning. I am not claiming the second is the reason — only that the incentive is worth noticing. My Amazon PPC strategy guide covers how to run campaigns without overspending.
What Sellers Should Do Now
- Audit your tool stack. List every paid service that touches your Seller Central or Ads data and what you pay for each. Overlapping tools are common; these productivity habits for Amazon sellers cover running a leaner stack.
- Question API-related price increases. If a vendor cited Amazon’s SP-API fees, ask whether the charge will be removed now that the fees are cancelled.
- Keep a small buffer for software. Amazon can change developer terms again, and vendors pass costs on. Recheck your worst-margin SKUs with realistic software costs included. For the cost side, see practical FBA fee-saving tactics and the 2026 FBA fee changes.
FAQ: Amazon SP-API Paid Changes
What is the Amazon SP-API and why does it matter?
The Selling Partner API is Amazon’s official interface that lets software read and update your seller data — orders, inventory, listings, reports and fees — automatically. Most seller tools depend on it, so any change to its terms reaches your software bills.
How much does the Amazon SP-API cost now?
Nothing extra. Amazon had planned a $1,400 annual fee per third-party developer plus usage fees for GET calls, but cancelled both in mid-May 2026. As of October 2026 there is no SP-API fee.
Will my Helium 10 or Jungle Scout subscription go up because of this?
Not because of SP-API fees, since they were cancelled. Large vendors could have absorbed the annual fee anyway; smaller tools with few customers were the most exposed. My Helium 10 review covers what that subscription includes.
Has Amazon delayed or cancelled the SP-API paid rollout?
Cancelled, for now. Amazon’s notice says it “will not move forward with the SP-API usage and annual fees at this time.” A revised plan could still be announced in the future.
Can I still download reports from Seller Central for free?
Yes. Manual report downloads in Seller Central were never part of the plan, and sellers using the API only for their own business were exempt.
How do I prepare my Amazon business for future API changes?
Know which tools touch your data, what each costs, and which ones you could drop. If a vendor raises prices, ask why, and compare alternatives before renewing.
The Bottom Line on Amazon SP-API Paid Changes 2026
The paid SP-API plan was announced, contested and cancelled within about six months. For sellers, the practical result is simple: no new API cost to absorb, and a good reason to question any price increase blamed on it. The lesson is that Amazon can change the economics of the tool ecosystem quickly, so know what your stack costs and what each tool earns you.
Watch the video above for my original reaction to the announcement, and subscribe to @AmazonFBAGirl for ongoing coverage of Amazon policy changes.
Sources
The tool behind this article
I don't run my PPC by hand — Daniks.AI does
Daniks.AI is the automation I built for my own listings: it sets bids, mines keywords, adds negatives, and holds your target ACoS 24/7. It now runs hundreds of other brands.
14 days free, up to 100 SKUs · no card games · cancel anytime.
Disclosure: I own Daniks.AI.
Written by
Ekaterina Rubtcova
Amazon seller since 2018 · Founder of Daniks cookware · Founder of Daniks.AI
My Daniks cookware reached Top-1 in Germany and is currently Top-20 in the USA. To run its PPC I built Daniks.AI — now used by hundreds of Amazon brands. On this blog I share how I actually operate, no courses, no upsells.

