Posted on November 29, 2025 by Mike

Amazon’s Selling Partner API (SP-API) has been a game-changer for sellers, enabling seamless integrations for inventory management, pricing, and analytics. However, big changes are on the horizon starting in 2026. On November 3, 2025, Amazon announced a new fee structure that ends the era of free access for third-party developers. As a seller or developer building tools for sellers, this could impact how you integrate and what it costs.

What Are the Key Changes?

The new model introduces charges specifically for third-party developers—those building public applications or platforms that serve multiple sellers. Here’s a breakdown:

  • Annual Subscription Fee: Starting January 31, 2026, third-party developers must pay $1,400 USD per year. This covers access to the Solution Provider Portal, support, and production SP-API usage.
  • Usage-Based Fees: From April 30, 2026, monthly fees apply for GET API calls exceeding the included 2.5 million per month (Basic tier). Overages cost $0.40 per 1,000 calls. PUT, PATCH, and POST requests remain unlimited (subject to rate limits).
  • Billing Setup Deadline: Developers must provide payment and tax info by February 16, 2026, or risk losing SP-API access.

Important: Sellers Are Not Directly Affected

If you’re an Amazon seller using SP-API directly for your own account—through private, self-authorized applications—you won’t face these fees. This applies to custom scripts or tools you build solely for your business. No subscription or usage charges for private use!

However, if you rely on third-party tools (like SaaS platforms for repricing or analytics), expect potential price hikes as developers pass on these costs. Amazon’s move supports ongoing API improvements but squeezes margins in the e-commerce ecosystem.

What This Means for Your Applications

For developers and agencies like us at Mike’s Blog Design, this shift encourages a reevaluation of integration strategies. Going forward, for all the applications we build, we’re recommending (and implementing) a model where sellers authorize and use their own SP-API credentials. This keeps things private and fee-free:

  • Private Integrations: Each seller generates their own developer credentials and LWA (Login with Amazon) tokens.
  • Self-Authorization: No public app registration—avoiding third-party developer status.
  • Cost Savings: Zero fees for sellers, and we optimize code to minimize API calls.
  • Compliance: Ensures data privacy and aligns with Amazon’s roles-based access.

This approach not only dodges the $1,400 annual hit but also empowers sellers with full control over their data. If you’re building or using tools now, it’s the perfect time to migrate to direct SP-API setups.

How to Prepare

  1. Audit Your Tools: Check if your integrations are third-party or private.
  2. Optimize Calls: Reduce redundant GET requests—use webhooks and caching where possible.
  3. Migrate Early: Switch to seller-direct auth to avoid disruptions.
  4. Stay Informed: Monitor Amazon’s Developer Portal for updates.

At Mike’s Blog Design, we’re here to help with custom SP-API setups. Drop a comment or reach out if you need guidance on making the switch.

Further Reading