Yes I have been using the 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 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.


On Sun, Jan 31, 2010 at 10:41 AM, Raffi Krikorian <> wrote:
> please check out - 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
>, and search related methods are on
> the exception comes with trends:
> the "trends api" which has local trends and global trends is on
> the original trends information (global trends, daily global trends, weekly
> global trends) are on search
> On Sat, Jan 30, 2010 at 2:05 PM, Josh Roesslein <>
> wrote:
>> Hello,
>> I have discovered that the search methods search and trends seem to
>> work okay with the domain
>> But the methods trends/current, trends/daily, and trends/weekly return
>> 401's. They only appear to work correctly
>> on the
>> I have opened an issue here [1]. Will all search methods eventually
>> work on the domain?
>> Thanks.
>> Josh
>> [1]
> --
> Raffi Krikorian
> Twitter Platform Team

Reply via email to