API v2 Update (consider it ready)
249 views
Skip to first unread message
jesse
Aug 5, 2013, 2:23:22 PM8/5/13
to
API v2 is essentially done and being frozen outside of any actual bug fixes that are necessary - ie, input/output parameters, behavior, method signatures, and the such are not going to be changed after this point unless someone finds something that is just totally and completely wrong.
The "beta" label on the docs will be peeled back in the next few days when full release notes and a comparison to API v1.3 are totally ready.
In the meantime, following our recent release of the official API 2.0 clients/wrappers, today we've also posted them to the standard pypi, npm, and rubygems sites.
And, since we're note the only game in town when it comes to wrappers/clients you may want to use, we've also updated out downloads page to include all the v2 wrappers we've seen in the wild.
Finally, I say "seen" and not been told about because our register script was broken. Doh. It has been fixed, so feel free to let us know about your work if we don't have it listed. Apologies!
The "beta" label on the docs will be peeled back in the next few days when full release notes and a comparison to API v1.3 are totally ready.
In the meantime, following our recent release of the official API 2.0 clients/wrappers, today we've also posted them to the standard pypi, npm, and rubygems sites.
And, since we're note the only game in town when it comes to wrappers/clients you may want to use, we've also updated out downloads page to include all the v2 wrappers we've seen in the wild.
Finally, I say "seen" and not been told about because our register script was broken. Doh. It has been fixed, so feel free to let us know about your work if we don't have it listed. Apologies!
Reply all
Reply to author
Forward
0 new messages