คงได้รับ email กับบ้างแล้วนะครับ ซึ่งจะเริ่มใช้ 15 ตุลานี้ ซึ่งจะมีผลกระทบหนัก กับนักปั่น amazon อย่างผม แต่ถ้าทำน้อยๆ ก็ไม่ต้องห่วงครับ เหลือเฟือ
โดยสรุปได้ดังนี้
ใน 1 ชม จะอนุญาติให้ เรียกใช้งาน search ผ่าน API ได้ แค่ 2,000 ครั้ง
และจะเพิ่มให้ 500 ครั้ง ถ้ามีการจัดส่งสินค้าทุกๆ $1 (ซึ่งจะได้สูงสุดไม่เกิน 25,000 ครั้ง/ชม)
ที่สำคัญนะครับ ต้องใช้ url + trackingID ที่ได้จาก search api ด้วย ไอประเภทที่มาจัดลิงก์ใหม่ (
http://www.amazon.com/dp/ASIN?tag=myID-20 ) ทำ redirect ซึ่งไม่ใช่ลิงก์ที่ได้จาก search API พวกนั้นจะไม่เอามาคิดด้วยนะครับ
Dear Product Advertising API Developer,
As you know, the Amazon Product Advertising API is a service that enables Associates to make money by advertising Amazon products in their websites and applications and sending traffic back to Amazon. We recently conducted a usage review of the Amazon Product Advertising API and found that some developers are using the API inefficiently. We’re introducing new guidelines that will help developers make more efficient use of the Amazon Product Advertising API. Starting October 15, 2010, developers using data from the API should refer at least $1 of sales to Amazon.com for every 500 calls made in excess of 2,000 calls per hour.
On October 15, 2010, we will begin instituting controls to ensure that all developers are using the service efficiently. These controls may vary over time or across developers as we evaluate the efficiency of applications on a case-by-case basis. These guidelines are designed to promote efficient use of the API while providing the most effective advertising functionality and feature-set for application developers like you. Please refer to the “Efficiency Guidelines” section on the Amazon Product Advertising API home page for more information.
Thank you for advertising products for sale on Amazon.com.
Sincerely,
The Product Advertising API Team
Dear Developer,
We are introducing efficiency guidelines for high volume users related to API usage. These guidelines are designed to promote efficient use of the API while providing the most effective advertising functionality and feature-set for application developers like you. Starting October 15 all usage will be subject to the efficiency guidelines. In addition, due to low usage, we plan to deprecate a subset of API operations and response groups. Please refer to the "Efficiency Guidelines" and "API Changes" sections below for details on the efficiency guidelines and API operations/response groups slated for deprecation. The efficiency guidelines will be phased in over a period of three months, starting July 15, and by October 15 all usage will be subject to these guidelines.
The Product Advertising API Team.
Efficiency Guidelines
The purpose of the Product Advertising API is to advertise Amazon Products and thereby enable Associates to make money by creating Amazon advertisements and sending traffic back to Amazon. A small number of users are requesting very large amounts of product data while generating a very small amount of product sales. The Product Advertising API efficiency guidelines are designed to promote efficient use of the API. Each account used to access the Product Advertising API will be allowed an initial usage limit of 2,000 requests per hour. Each account will receive an additional 500 requests per hour (up to a maximum of 25,000 requests per hour) for every $1 of shipped item revenue driven per hour in a trailing 30-day period. Usage thresholds are recalculated daily based on revenue performance. To ensure that each account qualifies for the additional threshold increase, the URLs served by the Product Advertising API must be used when linking back to Amazon and the Associate tags used must belong to the account owner.
API Changes
Due to low usage, the Product Advertising API operations and response groups listed below will not be supported after October 15, 2010:
* Operations: CustomerContentLookup, CustomerContentSearch, Help, ListLookup, ListSearch, TagLookup, TransactionLookup, VehiclePartLookup, VehiclePartSearch, VehicleSearch.
* Response Group: ListmaniaLists, MerchantItemAttributes, PromotionDetails, Subjects, Tags, TagsSummary, VariationMinimum
Additionally, due to low usage, we will be discontinuing Multiple Operation Requests and the TextStream search parameter. If you require continued access to these APIs, please contact us to discuss your use case.