Twitter API Versioning
The Twitter API supports versioning, which means that Twitter will be able to provide beta functionality without compromising stable code. There are currently two method address conventions: one for search methods, http://search.twitter.com/; and one for other methods, https://api.twitter.com/<<version>>/. In the second case, you can replace <<version>> with the version number that you intend to use, which should be set to 2 (the latest release version as of this writing). Twitter expects that deprecation between old and
new versions will take approximately six months, and so you have plenty of time to update code before changes become permanent.
The Twitter API supports versioning, which means that Twitter will be able to provide beta functionality without compromising stable code. There are currently two method address conventions: one for search methods, http://search.twitter.com/; and one for other methods, https://api.twitter.com/<<version>>/. In the second case, you can replace <<version>> with the version number that you intend to use, which should be set to 2 (the latest release version as of this writing). Twitter expects that deprecation between old and
new versions will take approximately six months, and so you have plenty of time to update code before changes become permanent.