API 1.1 400 error when using the page parameter

ghentsch · 2012-10-18T15:18:06.000Z

I’m trying to use paging to get more than 100 tweets from a search. In 1.0, i used “rpp” and “page” but the docs no longer talk about “page” although I’ve changed my “rpp” to “count” for 1.1. The oAuth tool allows me to crank out a base string for a search with count and page though. I’m getting a 400 error.

search:

https://api.twitter.com/1.1/search/tweets.json?q=%23bieber&result_type=recent&count=100&page=1

oAuth tool:

GET&https%3A%2F%2Fapi.twitter.com%2F1.1%2Fsearch%2Ftweets.json
&count%3D100
%26oauth_consumer_key%3DZO1nqqmS77mfNP7v17zraA
%26oauth_nonce%3D8b8582a21a2a9d7a7e7c8cb57e1b18bc
%26oauth_signature_method%3DHMAC-SHA1
%26oauth_timestamp%3D1350572549
%26oauth_token%3D19739039-IoUouCpvUgRyMN2wz5b0NtFfuOsgnoVHcaOYnuiPH
%26oauth_version%3D1.0
%26page%3D1
%26q%3D%2523bieber
%26result_type%3Drecent

Our application:

GET&https%3A%2F%2Fapi.twitter.com%2F1.1%2Fsearch%2Ftweets.json
&count%3D100
%26oauth_consumer_key%3DZO1nqqmS77mfNP7v17zraA
%26oauth_nonce%3DNjM0ODYxNTQ4NjA4Mzg3NTAw
%26oauth_signature_method%3DHMAC-SHA1
%26oauth_timestamp%3D1350572461
%26oauth_token%3D19739039-IoUouCpvUgRyMN2wz5b0NtFfuOsgnoVHcaOYnuiPH
%26oauth_version%3D1.0
%26page%3D1
%26q%3D%2523bieber
%26result_type%3Drecent

error:

The remote server returned an error: (400) Bad Request.

episod · 2012-10-18T15:24:03.000Z

The OAuth tool has no intrinsic knowledge of what an API method does or does not support – it’s just a tool that does OAuth…

Traditional paging is no longer offered in the Search API. You’ll need to treat it like a timeline and use since_id and max_id to navigate. You can find some tips here: [node:6213]