Users search doesn't show up some verified account


#1

Hi,

Today I experienced some weird behavior on the /1.1/users/search.json REST API endpoint. when I look for a specific user, it doesn’t show up in the search results. It seems to occur only with verified accounts. for example requesting /1.1/users/search.json/q=BRITAwards or /1.1/users/search.json?q=samsmithworld won’t return me those user, even if the query matches exactly the screen_name of those particular users.

I usually do those query via twitter4j in Java, but I did the testing with POSTMAN as well. Also tested using different accounts.
Twitter search input return those results.

Is that a known issue? Am I doing something wrong around this ?

Thanks in advance


User search missing expected results
User search missing expected results
GET users/search with q=bmw doesn't return user with id=1545994664(screen_name=bmw)
Search problems have returned
Users/search endpoint does not return the most relevant users
#2

I’m experiencing the exact same thing. The users/search endpoint is broken.

Anyone out there know how long this will take to fix? My site relies on Twitter search and I may have to move it to using the Facebook API instead.


#3

It seems some other users experience the same, there might be some issues currently.


#4

Thanks for all the reports, we will investigate.


#5

Great news @andypiper, thanks!


#6

Tracking internally as PREL-11824


User/Search Page not working suddenly
User/Search API Paging Issue
#7

In my case, twitter only show up the first 20 results and page parameter does not work.

I even tested this on Twitter.com. Twitter people search results only show up 20 results: (example: https://twitter.com/search?q=twitter&src=typd&mode=users)

The same results appears on the official twitter app for iOS.

BTW. I’m sorry. What’s the meaning of Tracking internally as PREL-11824. I’m new here you know :sweat:


GET users/search endpoint returning inaccurate results as of a few hours ago
#8

“PREL-11824” is the internal tracking number for this issue / bug. It is useful i.e. if you want to ask about a status update or refer to this issue. Unfortunately there is not public bugtracker for these issues anymore.


#9

This morning it works fine for me… :stuck_out_tongue:
It is solved, isn’t it?


#10

It’s working for me now. Twitter staff, thank you all. :heart:


#11

It’s working for me again too! Yay.


#12

Has been updated and fixed, to the best of our knowledge. Thanks for the confirmation everyone, and your patience!


#13

Great, it seems to work well on my end. Many thanks for the quick fix.


#14