Hey everyone,
Last week we let you know that we would soon be removing the search.twitter.com/trends endpoints [1]. Next Tuesday (12th April) is when will turn these endpoints off so please make sure you are using api.twitter.com/1/ for trends before then.
We've noticed some of you are also using the wrong host for other requests to the API. To avoid problems or outages with your applications please ensure you are making requests to the correct hosts (and base paths) for the Twitter API you want to use. Even if your code is working now, you should check the hosts match those listed below:
REST API:
OAuth:
Streaming (Track):
Userstreams:
Sitestreams Beta:
Search:
Tweet Button:
Web Intents
@anywhere:
Web Widgets:
Some common errors include:
* Incorrectly using http://twitter.com instead of http://api.twitter.com/1/
* Incorrectly making requests like http://api.twitter.com/account/verify_credentials.json instead of http://api.twitter.com/1/account/verify_credentials.json
* Incorrectly directing users to http://twitter.com/oauth/authorize instead of http://api.twitter.com/oauth/authorize
* Incorrectly querying http://199.16.156.11/search.json instead of http://search.twitter.com/search.json
SSL (https) is supported on some but not all hosts. You can use SSL on:
Best,
@themattharris
-- Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: http://groups.google.com/group/twitter-development-talk
No comments:
Post a Comment