404: {"errors":[{"message":"Sorry, that page does not exist","code":34}]}

dustin2k · 2012-12-01T03:29:05.000Z

Thanks jerry. This was my issue as well, after fixing the api.* prefixes.

MarathonKruse · 2012-12-02T04:40:00.000Z

I feel like I must be missing something obvious with this, but I, too, am having issues with the code 34 error:


$friends_str = implode(',',$friends_ids_all);
$conn2->request('POST',$conn2->url("https://api.twitter.com/1.1/users/lookup.json?user_id=$friends_str&include_entities=true"));

ReDetection · 2012-12-17T08:11:00.000Z

I’m getting code = 23 message = “Sorry, that page does not exist” on https://api.twitter.com/1.1/users/lookup.json too! Everything else works fine.

vis_1321 · 2013-01-09T05:50:00.000Z

Get ing error {“errors”:[{“message”:“Sorry, that page does not exist”,“code”:34}]}
while using http://api.twitter.com/1.1/users/show.json api.
with every other api works well but while using this get error every time

episod · 2013-01-09T16:09:26.000Z

Are you providing a user id or screen_name belonging to a user that does not exist?

James_Snell · 2013-01-10T13:03:31.000Z

Hello

I am getting the same issue when adding / removing tweets from favorites. It seems fine for some tweets and not others.

404:The URI requested is invalid or the resource requested, such as a user, does not exist.
{“errors”:[{“message”:“Sorry, that page does not exist”,“code”:34}]}

Any ideas?

James

James_Snell · 2013-01-10T19:40:33.000Z

To confirm above, I am passing ID’s which are on my home timeline so the ID’s definitely exist. I am also definitely passing a valid oAuth token as I am using it on GET calls successfully and some of the POST calls to work

AbdullahFaqeir · 2013-01-16T08:37:13.000Z

I had the same issue with /1/ but I’ve changed it to /1.1/ and it works just fine

akmaurya31 · 2013-01-18T18:50:20.000Z

Sir Please HELP ME

deividfortuna · 2013-02-18T21:07:29.000Z

I used the same code and don’t work. I don’t know what to do more.

ManishSingh_vns · 2013-02-19T16:31:00.000Z

hi i am getting 404 error in account/verify_credentials.json request after access token returned from oauth/access_token

Pls help…

jayaprakash1313 · 2013-02-22T15:21:28.000Z

Hi,
I need to parse twitter home feeds. So can any one help.Which is the correct parsing method (.XML,.JSON) and give the Url.Ex(home_timeline) not User_timeline.
What i post and what my followers post.

domsmemories · 2013-03-13T01:28:01.000Z

thx,my problem solved.

nykolasvs · 2013-03-26T18:04:42.000Z

i’m on the same issue. Can’t get it to work. Passing correct tweetID, but the problem i think it’s on the call it self.

id tried all this:
$content2 = $connection->post(‘favorites/create’, array(‘id’ => $tweet_id) );
$content2 = $connection->post(‘1/favorites/create’, array(‘id’ => $tweet_id) );
$content2 = $connection->post(‘1.1/favorites/create’, array(‘id’ => $tweet_id) );
$content2 = $connection->post(‘favorites/create’.$tweet_id );
$content2 = $connection->post(‘1/favorites/create’.$tweet_id );
$content2 = $connection->post(‘1.1/favorites/create’.$tweet_id );

and many more to…

mekzz · 2013-06-12T01:39:00.000Z

An error occured while calling the Twitter API
404: {“errors”:[{“message”:“Sorry, that page does not exist”,“code”:34}]}

i already migrate to 1.1 API and i’m using Dabr source code.

example:
define(‘API_URL’,‘https://api.twitter.com/1.1/’);
$user = twitter_process(‘https://api.twitter.com/1.1/account/verify_credentials.json’);
$signingURL = ‘https://api.twitter.com/1.1/account/verify_credentials.json’;

anyone can help me? thanks anyway

nashualibrarynh · 2013-06-13T15:51:55.000Z

Here I am back in a thread I visited before! Now of course v1 doesn’t work at all. I tried switching it to 1.1 in the URL, but of course that would be too easy.

I think Twitter needs to realize that while some of us may be IT people, we are not necessarily Twitter developers. We just have one thing we want Twitter to do and then we forget all about it until it breaks. And then we try to figure out how to fix it and we get redirected to the widget, which looks completely different from what we had and would completely ruin the aesthetic of our webpages, or we get thrown into the deep end of Twitter code. I don’t want to code my own widget. I just want the old one to work.

twpost1 · 2013-06-21T06:40:02.000Z

Is any one able to resolve this?
Please help…!!
m getting code 34 for 1.1 API. users/show

twpost1 · 2013-06-21T06:53:51.000Z

u able to get it solved?

twpost1 · 2013-06-21T06:53:35.000Z

have u solved that? if yes pls rly

tinacart · 2013-06-26T18:35:44.000Z

For everyone wanting to solve this using 1.1, head over to webdevdoor.com. He’s got it working using the setup discussed here:

http://www.webdevdoor.com/php/authenticating-twitter-feed-timeline-oauth/

And you can format the JSON response by following the guidelines here:
http://www.webdevdoor.com/javascript-ajax/custom-twitter-feed-integration-jquery/

Thanks so much, Tom E.!