It seems as neither is working. I tried #test1, #test2, #test3 and
#test1 #test2 #test3, but I got no data (streaming API), and I let it
run for hours. When I used only a single term #test1, I immediately
started getting data. Was there a change to prevent more than one term
from being used?

On Oct 14, 1:52 pm, John Kalucki <> wrote:
> You may be conflating the Streaming API, which requires commas between
> keywords, and the search API, which does not.
> -John Kalucki
> Services, Twitter Inc.
> On Oct 14, 9:19 am, Kyle B <> wrote:
> > On Oct 13, 4:09 pm, EastSideDev <> wrote:
> > > I am using the streaming search API. If I have more than one term to
> > > search, do I need to separate those terms with commas? If these are
> > > hash tags, do I include the hash symbol? ("#test1, #test2, #test3)  I
> > > am experiencing some random problems, and I would like to eliminate
> > > this as the trouble spot before looking for the problem elsewhere.
> > Personally, I have experienced no problems using spaces between the
> > search terms.  Be careful what you use because there is a difference
> > between searching all keywords and all occurrences of all keywords.  I
> > think you are fine with or without commas though.
> > Here are the search operators from twitter:  
> >
> > You can get an idea for url composition by using the advanced 
> > search:

Reply via email to