Getting 404 with an application that was working fine 2-3 weeks ago


#1

I am using Abraham Williams’ oAuth library for our application. I am trying to to lookup users, using that library:

$this->oAuthConnection->get(‘users/lookup’, array(‘user_id’ => $users_ids, ‘include_entities’ => 1));

I am now getting the following response:

Array
(
[errors] => Array
(
[0] => Array
(
[message] => Sorry, that page does not exist
[code] => 34
)
)
)

I verified that I have the correct version of the library:

public $host = “https://api.twitter.com/1/”;

function accessTokenURL() { return ‘https://api.twitter.com/oauth/access_token’; }
function authenticateURL() { return ‘https://api.twitter.com/oauth/authenticate’; }
function authorizeURL() { return ‘https://api.twitter.com/oauth/authorize’; }
function requestTokenURL() { return ‘https://api.twitter.com/oauth/request_token’; }

Is this library no longer working with the new API?


#2

Can you get closer to what’s failing? Do you know the URL you’re actually sending when it gets down to the HTTP level? Do you know if the user IDs you’re specifying all exist? (A 404 is an expected response from this method when none of your criteria has a match).


#3

I will try to dig a bit deeper, but this is the Abraham Williams library, and I am using it without modifications. Here’s what’s in the library for URLs:

public $host = “https://api.twitter.com/1/”;

function accessTokenURL() { return ‘https://api.twitter.com/oauth/access_token’; }
function authenticateURL() { return ‘https://api.twitter.com/oauth/authenticate’; }
function authorizeURL() { return ‘https://api.twitter.com/oauth/authorize’; }
function requestTokenURL() { return ‘https://api.twitter.com/oauth/request_token’; }

As for the IDs themselves, I am passing 100 IDs at a time, comma separated, and in the past, when one or more of these IDs did not exist, the call returned those that existed, and I sorted it out from there. This is not an issue of iDs not existing.