Today, we’re announcing two upcoming changes to our API:
We’re introducing a new requirement that all API users set a user agent
We’re retiring the “current_commission_rate” field (on the “account” method) and the “rate” field (on the “recent sales” method).
From October 1, 2014, both changes will apply to ALL versions of our API.
Why are we introducing the user agent requirement?
Several times during the past few months, we experienced surges in traffic which required us to temporarily route traffic through a Denial of Service filtering system. One of the filters rejects all HTTP traffic without a user agent in the header, as this is a common “attack vector” for malicious traffic.
Unfortunately, many users of our API do not currently set a user agent when making API requests, and their traffic was blocked on these occasions. This led to a poor experience for our API users, which we want to avoid in future.
Why are we removing the “current_commission_rate” and “rate” fields?
We’re retiring these fields because they no longer accurately represent our fee structure following today’s changes to our business model. Please see our business model announcement for more information.
What do I need to do?
Before October 1, 2014, please modify any programs, scripts, apps or plugins that use the API to:
Ensure they have a user agent
No longer rely on calls to the “current_commission_rate” or “rate” fields.
If these changes have not been made by October 1, any programs, scripts, apps or plugins that use our API may stop working as expected. We apologize for any inconvenience, and appreciate your understanding.
API survey
While we’re on the subject, we’d love to know how you use the API, what you use it for and how we can make it better. Please fill out the following form if you’d like to help us and/or receive future updates about the API.
The post Changes to Our API appeared first on Market Blog.
The post Changes to Our API appeared first on DICKLEUNG DESIGN 2014.
沒有留言:
張貼留言