Twitter search v1.1 returns 403 Forbidden for some users


Calling Twitter Search API v1.1 w/ exactly the same query produces three different results, depends on which oauth tokens used:

  • some users gets tweets back just fine
  • other users gets 403 Forbidden if using since_id parameter, but were able to get tweets back if removing the since_id
  • a few users always get 403 Forbidden error, no matter if since_id is used or not

This started happening fairly recently. Can someone please shed light on what might be the cause and suggest possible solution? Thanks!


Can you see if there’s anything “interesting” about the since_ids being used? Are you also using max_ids? Is there ever any time when since_id is larger than max_id?