Overview

Amazon will begin charging third‑party developers a $1,400 yearly subscription for access to the Selling Partner API (SP‑API) starting in mid‑2026, with additional per‑call fees for high‑volume GET requests slated for shortly after. The change does not affect sellers who use the API solely for their own accounts, but it could reshape the pricing of many third‑party tools that Amazon merchants rely on.

Key Points

• Annual subscription introduced — Effective around June 2026, any external developer or software vendor that offers SP‑API‑powered solutions must pay a flat $1,400 fee each calendar year, regardless of the number of sellers they serve.
• Usage‑based charges follow — Beginning roughly two months after the subscription launch, Amazon will add per‑call fees that scale with the volume of GET requests, meaning a tool that makes millions of calls per month could see a sizable incremental cost.
• Self‑use exemption remains — Sellers and brands that connect the SP‑API only to their own Amazon accounts will continue to enjoy free access, preserving the ability for businesses to build internal dashboards or inventory syncs without paying.
• Phased rollout — The subscription requirement is the first phase; the usage‑based tier is introduced later, giving developers a short window to assess their call patterns before the second cost component takes effect.
• Potential market consolidation — Smaller niche developers may find the $1,400 baseline disproportionate to their revenue streams, while larger platforms with deep pockets are likely to absorb the fee and pass only marginal price adjustments to end users.

How the New Pricing Model Works

1. Subscription activation — A developer registers for the paid tier in the Amazon Developer Portal, pays the $1,400 fee for the upcoming fiscal year, and receives a “paid‑partner” badge that unlocks unrestricted SP‑API endpoints; for example, a repricing SaaS that previously operated on a free tier must now submit a payment before its November release.
2. Call‑volume tracking — Amazon’s monitoring dashboard begins logging every GET request made by the developer’s applications, categorizing them by endpoint (e.g., /orders, /listings), and provides a real‑time usage meter; a tool that pulls order data every five minutes for 10,000 sellers will see its monthly call count displayed in the portal.