Effective August 31, 2022, we will be adjusting the rates across select API operations within the Catalog Items API, Product Fees API, and Product Pricing API. These adjustments will lower the rates of the 1x1 APIs. We encourage you to call the equivalent batch APIs for use cases requiring a higher volume of data.
What is changing?
-
listCatalogCategories
will change from rate/burst of 1/40 to 1/2. -
getCatalogItem
(GET /catalog/2020-12-01/items/{asin}
andGET /catalog/2022-04-01/items/{asin}
) will change from rate/burst of 5/5 to 2/2. -
searchCatalogItems
(GET /catalog/2020-12-01/items
andGET /catalog/2022-04-01/items
) will change from rate/burst of 5/5 to 2/2. For high-volume use cases, use the multi-query capability inGET /catalog/2022-04-01/items
. -
getMyFeesEstimateForSKU
andgetMyFeesEstimateForASIN
will change from rate/burst of 10/20 to 1/2. For high-volume use cases, usegetMyFeesEstimates
, which accepts batch sizes up to 20. -
getPricing
andgetCompetitivePricing
will change from rate/burst of 10/20 to 0.5/1. These operations accept a list of up to 20 items. -
getListingOffers
andgetItemOffers
will change from rate/burst of 5/10 to 1/2. For high-volume use cases, usegetListingOffersBatch
andgetItemOffersBatch
, which accepts batch sizes up to 20. - The Catalog Items v0 operations
listCatalogItems
(GET /catalog/v0/items
) andgetCatalogItem
(GET /catalog/v0/items/{asin}
) will be deprecated on September 30, 2022.
Change summary table:
Operation | Path | From Rate | From Burst | To Rate | To Burst |
---|---|---|---|---|---|
listCatalogItems |
GET /catalog/v0/items |
6 | 40 | deprecated | deprecated |
getCatalogItem |
GET /catalog/v0/items/{asin} |
2 | 20 | deprecated | deprecated |
listCatalogCategories |
GET /catalog/v0/categories |
1 | 40 | 1 | 2 |
searchCatalogItems |
GET /catalog/2020-12-01/items |
5 | 5 | 2 | 2 |
getCatalogItem |
GET /catalog/2020-12-01/items/{asin} |
5 | 5 | 2 | 2 |
searchCatalogItems |
GET /catalog/2022-04-01/items |
5 | 5 | 2 | 2 |
getCatalogItem |
GET /catalog/2022-04-01/items/{asin} |
5 | 5 | 2 | 2 |
getMyFeesEstimateForSKU |
POST /products/fees/v0/listings/{SellerSKU}/feesEstimate |
10 | 20 | 1 | 2 |
getMyFeesEstimateForASIN |
POST /products/fees/v0/listings/{ASIN}/feesEstimate |
10 | 20 | 1 | 2 |
getMyFeesEstimates |
POST /products/fees/v0/listings/{SellerSKU}/feesEstimate |
1 | 1 | 0.5 | 1 |
getPricing |
GET /products/pricing/v0/price |
10 | 20 | .5 | 1 |
getCompetitivePricing |
GET /products/pricing/v0/CompetitivePrice |
10 | 20 | .5 | 1 |
getListingOffers |
GET /products/pricing/v0/listings/{SellerSKU}/offers |
5 | 10 | 1 | 2 |
getItemOffers |
GET /products/pricing/v0/items/{asin}/offers |
10 | 20 | .5 | 1 |
getItemOffersBatch |
POST /batches/products/pricing/v0/itemOffers |
.5 | 1 | .5 | 1 |
getListingOffersBatch |
POST /batches/products/pricing/v0/listingOffers |
.5 | 1 | .5 | 1 |
Which marketplaces are affected?
This change affects all marketplaces.
Who is affected?
Developers who use the operations listed in the change summary table.
What action is required?
If you use the above operations, you must make the necessary changes to your application to accommodate these new rate limits prior to August 31, 2022.
Best regards,
The Amazon MWS Migration Support team