Taylor, I forgot to mention that I'm using the class epi as the client API for PHP and I have several other endpoint being called with parameters and so far, this is the only endpoint experiencing the issue.
Thanks, Jeff On Jun 15, 10:22 am, Jeff <[email protected]> wrote: > Taylor, > > Thanks for the response. Hopefully, this is what you need. I dumped it > right before the request. > > [ > "Expect:", > "Authorization: OAuth realm=\"http:\/\/api.twitter.com\/1\/followers > \/ids.json\", > oauth_consumer_key=\"OlPht6d2h3N1XYwCpCyx5Q\", > oauth_token=\"130232354- > gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY\", > oauth_nonce=\"71cc67f647043054dbd640b9b1f3d8fc\", > oauth_timestamp=\"1308151065\", > oauth_signature_method=\"HMAC-SHA1\", > oauth_version=\"1.0\", > oauth_signature=\"lYen9ON%2B5bVah%2BBHVGnPCMqBXQ8%3D > \"", > "User-Agent: " > ] > > On Jun 15, 10:05 am, Taylor Singletary <[email protected]> > wrote: > > > > > > > > > This means that your signing is slightly wrong (and likely has been slightly > > wrong for some time) when you're using parameters in your request. Can you > > detail the signature base string and authorization header you are using when > > building this request? > > > @episod <http://twitter.com/intent/user?screen_name=episod> - Taylor > > Singletary > > > On Wed, Jun 15, 2011 at 8:00 AM, Jeff <[email protected]> wrote: > > > > Tuesday morning around 10am CDT I noticed a change in the API > > > endpoint /version/followers/ids in how it operates. > > > > If you provide the cursor parameter, such as: > > > > /1/followers/ids.json?cursor=-1&user_id=12345 the method returns data > > > correctly, however it also return the error warning "Invalid OAuth > > > credentials detected". Here is the response from the API. > > > > "data":{ > > > "responseText":"{\"previous_cursor\":0,\"next_cursor_str\":\"0\", > > > \"previous_cursor_str\":\"0\",\"ids\": > > > [222126862,95945240,169607024,148845934,95447204,94401716], > > > \"next_cursor\":0}", > > > "headers":{ > > > "Date":"Wed, 15 Jun 2011 14:39:54 GMT", > > > "Server":"hi", > > > "Status":"200 OK", > > > "X-Warning":"Invalid OAuth credentials detected", > > > "X-Transaction":"1308148794-15054-58845", > > > "X-RateLimit-Limit":"150", > > > "X-Frame-Options":"SAMEORIGIN", > > > "Last-Modified":"Wed, 15 Jun 2011 14:39:54 GMT", > > > "X-RateLimit-Remaining":"66", > > > "X-Runtime":"0.02003", > > > "Content-Type":"application\/json; charset=utf-8", > > > "Content-Length":"150", > > > "Pragma":"no-cache", > > > "X-RateLimit-Class":"api", > > > "X-Revision":"DEV", > > > "Expires":"Tue, 31 Mar 1981 05:00:00 GMT", > > > "Cache-Control":"no-cache, no-store, must-revalidate, pre- > > > check=0, post-check=0", > > > "X-MID":"c7827d770b9045b049f3967663b08dce7704a9fb", > > > "X-RateLimit-Reset":"1308150383", > > > "Vary":"Accept-Encoding", > > > "Connection":"close" > > > }, > > > > The problem here is that because it thinks the OAuth credentials are > > > "Invalid" it gives me a rate limit of 150. > > > > If I remove the parameters "?cursor=-1&user_id=12345" and simply use > > > the endpoint /1/followers/ids.json it accepts my OAuth credentials as > > > valid and and returns the appropriate rate limit of 350. Although this > > > works, I need pagination as there are a lot of ids I need to retrieve. > > > > This had been working correctly and I noticed the change yesterday > > > morning. > > > > Any help on resolving this or letting me know if something has changed > > > when parameters are used with this endpoint would be greatly > > > appreciated. > > > > Thanks, > > > Jeff > > > > -- > > > Twitter developer documentation and resources:https://dev.twitter.com/doc > > > API updates via Twitter:https://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >https://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
