Amazon drops SP-API fees after developer pushback
Amazon cancels its Selling Partner API usage and annual fees for third-party developers after community feedback, reversing plans announced in November 2025.
Data
Amazon this week reversed its decision to charge third-party developers for access to the Selling Partner API (SP-API), cancelling both the annual subscription fee and usage-based charges that had been scheduled to take effect in 2026. The company posted the announcement on the SP-API developer portal, stating it "will not move forward with the SP-API usage and annual fees at this time."
The reversal ends a months-long standoff between Amazon and a developer community that had grown increasingly vocal about the financial consequences of the planned fee structure. According to the announcement published directly on the SP-API portal, Amazon cited developer feedback as the decisive factor: "We previously announced changes to developer fees related to SP-API usage, and we value your feedback on those planned changes."
What the fees would have cost
The original plan, announced on November 3, 2025, would have imposed an annual subscription fee of $1,400 starting January 31, 2026, plus monthly GET API call-based charges beginning April 30, 2026. Four tiers were defined. The Basic tier included 2.5 million GET calls per month at no additional charge beyond the annual subscription. The Pro tier was priced at $1,000 per month for 25 million GET calls, while the Plus tier reached $10,000 per month for 250 million calls. An Enterprise tier existed for developers exceeding Plus-tier volumes, with pricing negotiated directly with Amazon. Overage charges were set at $0.40 per thousand API calls.
The financial exposure was not trivial. A developer in the Pro tier generating 28 million GET calls in a single month would have faced a total bill of $2,200 - the $1,000 base fee plus $1,200 in overage charges. Across a full year, including the annual subscription, a mid-size software provider running consistently above the Basic tier threshold could have faced annual costs running into tens of thousands of dollars. Smaller independent developers, particularly those building single-function tools for niche selling categories, faced a starker choice: absorb the fees, pass them through to sellers, or exit the ecosystem entirely.
The Solution Provider Portal changes
With the fee cancellation confirmed, Amazon says it will update the Solution Provider Portal (SPP) in the coming weeks. Specifically, the fee preview dashboard - a feature that gave developers a simulated view of what they would owe under the new structure - will be removed. Developers who had already submitted credit card information through the SPP in anticipation of the charges can delete that payment method immediately through a link provided inside the portal.
According to the announcement, no further action is required from developers beyond optionally removing their stored credit card. The update to the SPP is described as a technical cleanup following the policy reversal rather than a procedural requirement for developers to complete.
A developer ecosystem that spans 2,500+ applications
The SP-API serves as the primary programmatic interface between third-party software providers and Amazon's marketplace infrastructure. The Selling Partner Appstore, which lists applications built on the API, currently features more than 2,500 applications across more than 20 countries serving over 1.4 million sellers. Applications span product listing management, automated pricing, inventory and order management, advertising optimization, promotions, e-commerce connectors, analytics, and full-service solutions.
The API replaced its predecessor, Marketplace Web Services (MWS), which Amazon introduced in 2009. MWS and subsequently SP-API provided free access for over a decade, establishing a development culture built on the assumption that API access was a cost of doing business Amazon would absorb. The November 2025 announcement broke that assumption explicitly. According to the coverage by PPC Land at the time, the announcement "signals a fundamental shift in how Amazon monetizes its developer ecosystem."
That shift has now been reversed - at least for the time being. The "at this time" phrasing in Amazon's announcement leaves open the possibility of revisiting the fee structure in the future. The company did not indicate whether it plans a revised model, a lower fee scale, or a different approach to cost recovery.
What developers faced under the original timeline
The original implementation schedule was aggressive. Amazon opened billing setup in the SPP on November 3, 2025 - the same day as the announcement. Developers were required to submit charge method information, billing addresses, and tax information by January 31, 2026. Those whose applications lacked valid payment methods faced removal from the Selling Partner Appstore on February 9, 2026, with new seller authorizations blocked from that date forward. By February 16, 2026, applications without valid charge information were set to lose all SP-API access entirely. Amazon had stated it would contact sellers who had authorized affected applications to notify them of potential service disruptions.
Monthly utilization fees were scheduled to begin April 30, 2026 - a six-month gap after the annual subscription implementation that Amazon framed as giving developers time to optimize API call patterns. Amazon had published call optimization guidance covering best practices for structuring requests, avoiding redundant calls, and implementing efficient data handling to reduce potential fees under the metered structure.
PUT, PATCH, and POST requests were to remain unmetered and unlimited under the original plan, subject to standard rate limits. Only GET calls - the read operations that power inventory queries, order lookups, listing retrievals, and reporting - would have counted toward the monthly usage tiers.
Industry context and downstream pressure on sellers
The SP-API fees never existed in isolation. Third-party software companies absorbing the API costs were widely expected to pass them through to the Amazon sellers who subscribe to their tools. PPC Land coverage from November 2025 cited Jon Elder, founder of Black Label Advisor, who stated publicly that sellers should expect software costs to rise: "Every software com[pany]" would pass the costs through. For smaller sellers operating on thin margins and relying on several software subscriptions simultaneously, the cumulative impact could have been meaningful.
This dynamic made the SP-API fees a seller-facing cost as much as a developer-facing one - a fact that likely contributed to the volume and tone of feedback Amazon received. Amazon's marketplace has already been subject to a series of fee and policy changes throughout 2025 and into 2026. Mandatory prepaid return labels for US sellers took effect February 8, 2026. FBA removal and disposal fees shifted to per-unit billing in February 2026. Each change added incremental complexity and cost to marketplace operations.
Layering API costs on top of that environment - costs that would filter through to sellers via software subscriptions - created conditions in which even a relatively modest annual fee could carry outsized political weight within the Amazon seller community.
The broader API monetization question
The SP-API reversal sits inside a broader debate across the advertising and e-commerce technology industry about whether platform APIs should be free, subsidized, or priced at market rates. Amazon's attempt and subsequent withdrawal is not the first such case. Microsoft Advertising announced in April 2026 the retirement of its legacy SOAP API, consolidating developers onto the REST API by January 2027 - a structural change rather than a monetization one. Twitter, now X, moved to paid API access in 2023, triggering significant developer attrition and third-party tool closures. Reddit followed with its own API pricing changes in 2023, resulting in protests from developers and communities alike.
Amazon's situation differs in one important respect: the SP-API underpins commercial software used directly in live selling operations. This is not a data or research API supporting analytics dashboards or social media clients. Disrupting access means disrupting active order management, pricing automation, and inventory workflows for sellers who depend on those tools daily. That operational dependency gave developers - and by extension sellers - unusual leverage. The feedback Amazon received was presumably not just critical but specific about the business consequences that would follow.
The one-sidedness of the original structure
One notable asymmetry in the original fee plan was that it did not affect all API users equally. According to the November 2025 announcement, sellers and vendors using SP-API exclusively for their own business operations - not building applications for other selling partners - would not face additional SP-API fees. The charges applied only to third-party developers whose applications served multiple selling partners. This distinction is commercially rational, but it meant the cost burden landed entirely on the software ecosystem rather than being distributed across the full base of API users.
Amazon also announced alongside the original November 2025 fee structure that third-party developers would no longer be required to maintain Professional selling plans in Seller Central, removing a separate monthly cost. However, developers choosing to maintain active Seller Central accounts for testing or business purposes would still incur standard selling fees. Whether that offset meaningfully reduced the net impact on smaller developers is unclear, but the fee plan's opponents focused primarily on the gross new costs rather than the partial offset.
Practical steps following the reversal
For developers who submitted credit card details through the SPP in anticipation of the January 31, 2026 billing deadline, Amazon has confirmed that stored payment information can be deleted immediately via the SPP. The fee preview dashboard will be removed in the coming weeks as part of the portal cleanup. No other administrative steps appear to be required by developers to restore or maintain their existing SP-API access.
Amazon's statement closes with a forward-looking commitment: "We are committed to supporting you as you build the next generation of solutions for selling partners." Whether that commitment translates into a permanent abandonment of API monetization, a revised and more limited fee structure, or a temporary pause remains to be seen.
Timeline
- 2009: Amazon launches Marketplace Web Services (MWS), providing free API access to third-party developers for the first time
- November 3, 2025: Amazon announces SP-API fee structure - $1,400 annual subscription starting January 31, 2026, plus monthly usage fees from April 30, 2026; billing setup opens in the Solution Provider Portal on the same day
- November 9, 2025: PPC Land publishes detailed analysis of the fee tiers and implementation timeline
- January 31, 2026: Original deadline for developers to submit payment information; annual subscription charges were set to begin
- February 9, 2026: Applications without valid payment methods were to be removed from the Selling Partner Appstore, with new authorizations blocked
- February 16, 2026: Applications lacking valid charge information were set to lose all SP-API access
- February 17, 2026: Amazon announces Business Solutions Agreement update including formal Agent Policy effective March 4, 2026, adding further compliance requirements for developers
- February 22, 2026: Amazon Brand Stores API exits beta, part of broader Amazon API ecosystem expansion
- April 30, 2026: Monthly utilization fees based on GET call volume were originally scheduled to begin
- May 14, 2026: Amazon cancels all SP-API usage and annual fees, citing developer feedback; announces removal of fee preview dashboard from the SPP
Summary
Who: Amazon, third-party developers building applications on the Selling Partner API (SP-API), and the Amazon sellers who use those applications across more than 20 countries.
What: Amazon has cancelled its planned SP-API fee structure, including a $1,400 annual subscription fee and monthly GET-call-based usage fees that had been scheduled to take effect in January and April 2026 respectively. The company will update the Solution Provider Portal to remove the fee preview dashboard, and developers who submitted credit card details can delete them immediately.
When: The cancellation was announced today, May 14, 2026. The original fees were first announced November 3, 2025, with annual billing set to begin January 31, 2026, and monthly usage fees from April 30, 2026.
Where: The announcement was published on the Amazon Selling Partner API developer portal. The affected ecosystem spans the Selling Partner Appstore, which lists more than 2,500 applications serving over 1.4 million sellers in more than 20 countries.
Why: According to Amazon's own statement, the decision followed developer feedback on the planned changes. The fee structure had drawn criticism from third-party software providers concerned about direct costs and from the broader seller community, which anticipated those costs being passed through via higher software subscription prices.