#141

without twitter authentication how can i fetch twitter userid and screen name

because in old api its working fine for over site demo link.

please help me for solve this issue.

#142

Mr Singletary, I’ve been told that it’s possible to subscribe to a Twitter feed in RSS form by entering the username here to generate a link: http://www.twitter-rss.com/

I understand that one could subscribe to your Twitter feed, for instance, with this link: http://www.twitter-rss.com/user_timeline.php?screen_name=episod

I’m not sure if it works but would be interested to know your thoughts.

#143

I have one question regarding the migration from api v1 to v1.1.
I am using openid script for user registration using twitter.Now it has stopped responding due to api up-gradation.
Now I want to know know the exact way of upgrading the twitter API.as I explored alot couldn’t find the guiding link.

#144

Exactly right, thanks!

#145

The original post in this thread has a great, detailed overview on how to move to v1.1: https://dev.twitter.com/discussions/10644

#146

As a result of the new requirements that API requests be signed with OAuth, it is no longer possible to have a pure client-side app that also keeps your secret keys secret. You will need to write a server-side proxy to make the requests between your client-side app and Twitter.

#147

Yes indeed: [node:3726]. OAuth is fairly complicated, and will require some programming knowledge. You might also be interested in our options for websites, found here: Twitter for Websites | Docs | Twitter Developer Platform

#148

I always receive the error message that is “{“errors”:[{“message”:“Bad Authentication data”,“code”:215}]}” when I request the link which is “https://api.twitter.com/1.1/search/tweets.json?q=%40twitterapi&count=10”.

Can someone help me on this?

Thanks.

#149

Why can you not simply keep the old API? It was working well for us until it was disabled and the new API does not work as the old one did. This is causing a consternation of problems for us.

#150

We don’t have any developers - we are a non-profit. But we used the old widget for a long time, and users liked it. When the old one stopped working, we generated the new code at the widget page for a timeline widget, and dropped the code in just as it was in the widget page. It doesn’t do anything, and none of us understand any of it :frowning: We seem to be completely stuck. We have a test page with the just the widget code at http://iagsdc.info/test/widget.php. All it brings up is the link. We really don’t know who to ask - I’ve looked around on this site, but clearly everyone here is much more technical than we are. Is there any hope of getting a simple widget again, like the old one? Here’s our generated code for the test page, if that helps:

Untitled Document Tweets by @IAGSDC
#151

In API v1.1, there is a problem in retweet API. I tried by web intent and its working fine but using with API its not working for me. Is there anything missing by me or you can check it? Please replay me ASAP.

#152

What is the problem you are seeing? It doesn’t look like the retweet method changed between v1 and v1.1.

https://dev.twitter.com/docs/api/1.1/post/statuses/retweet/%3Aid

#153

It looks like you got the new widget working as expected on your landing page.

#154

This code looks like it is intended to run client-side in a browser. With the change to REST API v1.1, you can no longer run purely in a browser due to the new OAuth v1.0a requirements. You will need to run a proxy that handles the OAuth signing. Please see [node:3726] for all of the details.

#155

I am working on a project that uses Streaming API with Phirehose library and i can’t download public tweets with sample anymore. Keep in mind that i’m using API v 1.1 ( const URL_BASE = ‘https://stream.twitter.com/1.1/statuses/’; ) what happend? Could anyone help me with this issue please?

Thanks in advance

#156

I was using this URL to get recommended users before 1.1:
https://api.twitter.com/1.1/users/recommendations?connections=true&disabled=true&dismissable=false&display_location=wtf-component&emptyTimelineModule=true&excluded=&followingCount=2&initialResults=true&limit=3&pc=true&scribeContext[component]=user_recommendations

Then, I tried to use the “new” version to get suggested users instead of recommended users:
https://api.twitter.com/1.1/users/suggestions/twitter.json

However, with the new version, I get the following error:
{“errors”:[{“message”:“Bad Authentication data”,“code”:215}]}

I haven’t changed the authentication process from the previous version.
I am running this URL to authorize:
https://api.twitter.com/oauth/authorize?oauth_token=n6DRG7x4QKwo927qtENAqQWunGVjLB6xcukydTgin8

Any suggestions or samples on how to get this working?

#157

I have a dashboard with multiple twitter accounts. How can I get the home_timeline for all account using api 1.1 without having all users authenticate with username and password? Do I use application-only authentication? I’ve been working on this for a week now and my customer cannot get the data from the 312 twitter accounts. I’m able to test 1 user, but how can I get information for 312 users?

Can someone help, I’ve been asking this question in this forum for days and have not gotten any help? Is there a number I can call to speak to a real human?

This is what I’m dealing with:
function get_twitter_subscribers($args)
{
$rate = @file_get_contents(‘http://api.twitter.com/1.1/application/rate_limit_status.json’);
$rate = @json_decode($rate);

	if($rate->remaining_hits == 0):
		$status = 'retask';
	else:
					
		$new_data = @file_get_contents('http://api.twitter.com/1.1/users/show.json?screen_name='.$args['account_id'].'&include_entities=true');
		$new_data = @json_decode($new_data);
		if(isset($new_data->followers_count)){

			$insert_args = array(
				'account_id' => $args['account_id'],
				'metric' => 'subscribers',
				'value' => $new_data->followers_count,
				'platform' => 'twitter'
			);

			$insert = $this->CI->metrics_model->insert_metric($insert_args);
			
			if (isset($insert)) { $status = 'complete'; }
		
		}else{
			$this->send_error_email("Function: get_twitter_subscribers - new_data->followers_count not set for account id: " . $args['account_id'] . "\r\n\r\n" . "args: " . http_build_query($args) . "\r\n\r\n" . 'http://api.twitter.com/1.1/users/show.json?screen_name='.$args['account_id'].'&include_entities=true');	
		}
		
	endif;

if(!isset($status)){
		$this->send_error_email("Function: get_twitter_subscribers - status not set." . "\r\n\r\n" . "args: " . http_build_query($args) . "\r\n\r\n" . 'http://api.twitter.com/1.1/users/show.json?screen_name='.$args['account_id'].'&include_entities=true');
	$status = 'error';
}

return $status;
#158

Check out [node:10644]. This is a discussion around migrating to v1.1. The authorization process has changed quite a bit, so you will undoubtably need to make changes to your code to accomodate this.

#159

The new API is really more complicated than most people need. I have several websites I manage and now I have to create twitter apps for them each, all they want to do is display their tweets.

Is this an example of “it wasn’t broke, but you fixed it?”

#160

If all they want to do is display their tweets, have a look at this page: Overview | Docs | Twitter Developer Platform