merging the two is still high on the list -- we're unfortunately not there
yet...

On Sun, Jan 31, 2010 at 8:57 AM, Josh Roesslein <jroessl...@gmail.com>wrote:

> Yes I have been using the search.twitter.com domain for all the search
> methods in my library. It was just brought up in a ticket that some of
> the search methods do work on api.twitter.com. This does appear to be
> true after some testing, so I thought maybe Twitter was finally
> merging the two API's together.
>
> Thank you for clearing this up. I will continue using the two separate
> domains search.* and api.* in my library.
>
> Josh
>
> On Sun, Jan 31, 2010 at 10:41 AM, Raffi Krikorian <ra...@twitter.com>
> wrote:
> > please check out http://apiwiki.twitter.com/Twitter-API-Documentation -
> it
> > lists the full domain and URL you should be using for all calls.  in
> > general, all the timeline, status, user related methods are on
> > api.twitter.com, and search related methods are on search.twitter.com.
> > the exception comes with trends:
> >
> > the "trends api" which has local trends and global trends is on
> > api.twitter.com;
> > the original trends information (global trends, daily global trends,
> weekly
> > global trends) are on search twitter.com.
> >
> > On Sat, Jan 30, 2010 at 2:05 PM, Josh Roesslein <jroessl...@gmail.com>
> > wrote:
> >>
> >> Hello,
> >>
> >> I have discovered that the search methods search and trends seem to
> >> work okay with the domain api.twitter.com.
> >> But the methods trends/current, trends/daily, and trends/weekly return
> >> 401's. They only appear to work correctly
> >> on the search.twitter.com.
> >>
> >> I have opened an issue here [1]. Will all search methods eventually
> >> work on the api.twitter.com domain?
> >>
> >> Thanks.
> >>
> >> Josh
> >>
> >> [1] http://code.google.com/p/twitter-api/issues/detail?id=1413
> >
> >
> >
> > --
> > Raffi Krikorian
> > Twitter Platform Team
> > http://twitter.com/raffi
> >
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Reply via email to