Overview Amazon SP-API New Program And Usage Fees

Starting January 31, 2026, Amazon is implementing fees for using the Selling Partner API (SP-API).

Amazon will start charging for access to the SP-API and usage fees for API GET requests. What are GET requests? A GET request is used to retrieve data (reports, transactions…) from the SP-API.

Amazon is charging a $1400 yearly program fee and API usage fees. The API usage fees have a base rate of .40 CPM (cost per thousand) for GET API calls.

The more data you are collecting, the more GET requests and the great the charges from Amazon.

Given the variability involved in usage fees, we outlined a few examples below to highlight different scenarios:

Our first example is the Amazon SQP ASIN reports. If you have 1000 ASINs, to get the 1000 ASIN SQP reports will require at least 1000 GET requests, one for each ASIN report, per market. If you have 4 markets, that would be at least 4000 GET requests.

The caveat here is it will typically require more than one GET request for this data, so the actual GET requests for those 1000 ASIN reports would be closer to 1200-1500.

Another example is the Orders API. If you have 500 orders in a given hour in the US marketplace for July 10th, here the approximate number of GET calls:

Over the course of 24 hours for July 10th, the number of GET requests for the US marketplace would be 12,120 to 36,120 GET requests. This number will be higher when adding more marketplaces into the requests and attempting a retry any time Amazon has an error.

If you have 20 seller accounts, in the US market, averaging the same volume of orders, the GET counts would be 240,000 to 720,000 per day. Using the base .40 CPM pricing the cost basis will be $96 to $288 per day.

As we highlighted in our previous examples, the number of GET requests will vary based on the Amazon system. For transactional APIs, like Orders API, the number of requests is directly connected to the volume of orders/transactions.

The Orders API, by design, requires more GET requests than, say, a daily Order Report By Date, which may require 2-3 GET requests per seller, per market, for the same July 10th date.

While the Order API and Order Report serve different purposes, this highlights the variations and choices to be made. You may decide that the Order Report is sufficient or it is missing key data points that the Order API provides, so you need both. Amazon is placing direct costs on these choices.

First, it is important to understand that there are three types of applications within the SP-API:

As an Openbridge customer, you have a few options for access to the Amazon SP-API:

We refer to option 2 and 3 as "Bring Your Own App" or BYOA.

We handle everything. No Amazon developer registration, no application reviews, no fee management. This is how it has worked in the past, the only difference will be Openbridge will implement a new metered Amazon SP-API usage billing.

We have not finalized pricing as we are awaiting feedback from Amazon about changes to their pricing and tiers based on community feedback. However, we do plan on charging a rate lower than that base rate Amazon's charges given our opportunity to operate at scale.
​
We hope to have this finalized in the coming weeks. If you want to discuss, please schedule a call.

You swap our app for yours. This means you use your own Amazon public or private app credentials. You manage the Amazon relationship; we power the pipeline using your app.

In the case of “private” apps, Amazon has stated the SP-API fees “affect global third-party developers offering applications to other selling partners. Sellers and vendors using private apps to access the SP-API directly for only their business will not incur additional SP-API fees”.

To put it simply, any public app will be charged by Amazon for program and usage fees, private apps will not.

Payments for the Amazon SP-API program and usage fees would be paid directly to Amazon. There are no additional charges from Openbridge for BYOA.

Amazon places limits when using private apps. A private app allows a limited number of self-authorizations (e.g., up to ten), primarily for connecting to the developer's own accounts across different marketplaces. They do not support authorizations from external sellers or vendors.

If you are an agency, consultant, solutions provider or software service, private apps are most likely not viable. It would require each of your seller or vendor customers to register an app themselves, then grant you access. This can be a blocker to onboarding, and ongoing management, since each private app has its own requirements for Amazon LWA credential rotations.

It is also possible that Amazon rejects a private app registration, which may be more likely given the new SP-API program and usage fees. As a result, you will likely need to create your own Public app, similar to Openbridge, and use that for your customers.

Contact your Openbridge account representative to discuss which option is right for your organization.