Re: [twitter-dev] Please check you are using the correct API and host

2010-12-16 Thread Abraham Williams 
https should be preferred on many of these especially anything that
is transferring protected data.

Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham  | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Thu, Dec 16, 2010 at 16:54, Matt Harris wrote:

> Hey Developers,
>
> We recently reviewed a sample of your API requests, emails and support
> tickets and found that some of you were not using the correct domains.
>
> While undocumented domains and endpoints may respond with data, you should
> avoid using them as they may be disabled or changed without notice.
>
> Our network infrastructure is also updated from time to time. These changes
> are required for capacity planning or load balancing, but are generally
> transparent to you if you use the correct API host.
>
> To avoid problems or outages with your applications you need to ensure you
> are using 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:
> http://api.twitter.com/1/RESOURCE
> OAuth:
> http://api.twitter.com/oauth/RESOURCE
> Streaming (Track):
> http://stream.twitter.com/1/RESOURCE
> Userstreams:
> http://userstream.twitter.com/2/user.json
> SiteStreams Beta:
> http://betastream.twitter.com/2b/site.json
> Search:
> http://search.twitter.com/search.json
> Tweet Button:
> http://platform.twitter.com/widgets.js
> @anywhere:
> http://platform.twitter.com/anywhere.js
> Web Widgets:
> http://widgets.twimg.com/j/2/widget.js
>
> Some common errors include:
> * Incorrectly using http://twitter.com instead of
> http://api.twitter.com/1/
> * Incorrectly using 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/authorizeinstead of
> http://api.twitter.com/oauth/authorize
> * Incorrectly querying http://199.16.156.11/search.json instead of
> http://search.twitter.com/search.json
>
> You can find the documented endpoints on our developer resources site:
> http://dev.twitter.com
>
> Best,
> @themattharris
> Developer Advocate, Twitter
> http://twitter.com/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
>

-- 
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

[twitter-dev] Please check you are using the correct API and host

2010-12-16 Thread Matt Harris 
Hey Developers,

We recently reviewed a sample of your API requests, emails and support
tickets and found that some of you were not using the correct domains.

While undocumented domains and endpoints may respond with data, you should
avoid using them as they may be disabled or changed without notice.

Our network infrastructure is also updated from time to time. These changes
are required for capacity planning or load balancing, but are generally
transparent to you if you use the correct API host.

To avoid problems or outages with your applications you need to ensure you
are using 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:
http://api.twitter.com/1/RESOURCE
OAuth:
http://api.twitter.com/oauth/RESOURCE
Streaming (Track):
http://stream.twitter.com/1/RESOURCE
Userstreams:
http://userstream.twitter.com/2/user.json
SiteStreams Beta:
http://betastream.twitter.com/2b/site.json
Search:
http://search.twitter.com/search.json
Tweet Button:
http://platform.twitter.com/widgets.js
@anywhere:
http://platform.twitter.com/anywhere.js
Web Widgets:
http://widgets.twimg.com/j/2/widget.js

Some common errors include:
* Incorrectly using http://twitter.com instead of
http://api.twitter.com/1/
* Incorrectly using 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/authorizeinstead of
http://api.twitter.com/oauth/authorize
* Incorrectly querying http://199.16.156.11/search.json instead of
http://search.twitter.com/search.json

You can find the documented endpoints on our developer resources site:
http://dev.twitter.com

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/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