How would I pull ~20 latest statuses from user_timeline with API 1.1 without Oauth?

[SkillsUSARI]

anyone able to help with iOS? I have retrieved my access_token but that is as far as I can get.

[creotec]

Here is my PHP solution to generate RSS feeds from any Twitter user’s public timeline. You can install it once a server and just call it using http://YOURSERVER/index.php?u=TWITTERUSER and it will return a RSS feed. It creates a cached copy of generated XML files so hopefully you keep within your call limits.

http://ebusinessconsultant.co.uk/twitter-to-rss.zip

[spritz_creative]

Thanks @jason_mayes, this is fantastic.

I went with a server side solution but wanted to go with javascript due to page load speed issues, etc, etc.

Can someone from twitter verify that this is a long term workable solution - or is this more of an exploit?

I’m still yet to hear logical reasoning as to why twitter decided to require authentication for public information. I’m sure many people here share the frustration that this change is causing.

[SkillsUSARI]

I finally just got this figured out on iOS using Application authentication.
I was getting my token ok - but when I submitted the token with the user timeline request, it was giving me bad authentication. Reading thru the doc I thought it told me to convert my token to base64. but apparently it was already being returned to me base64. once I changed that, all is well. the rest of my code worked as before with API 1. whew!

[twingstudio]

No doubt about it. The webdevdoor tutorial is pretty simple and awesome! Works fine here!!! Thank you =]
http://www.webdevdoor.com/php/authenticating-twitter-feed-timeline-oauth/

[martinshoe]

Works for me and easy to set up!
Pretty cool solution!

What is the cache refresh time in thuis script?
Thanks !!

[AZOMITE]

Congrats. Will re-read and see if it can help us too.

[umerpasha]

C# dot net code to get latest tweets using twitter API 1.1

[shaf69uk]

What about Digital Signage screen using XML Player which can’t have long code but only 1 line URL?
Twitter is dead on my screen

[creotec]

You can change the cache time in “index.php” look for the line (line 19)

$cachetime = (60 * 60)*2; //Time in seconds to check cached file

(60 * 60)*1 = 3600 seconds = 1 hour
(60 * 60)*2 = 7200 seconds = 2 hours
(60 * 60)*24 = 86400 seconds = 24 hours = 1 day

For example you can change line to read:
$cachetime = 3600; //Time in seconds to check cached file

To get more than the default latest 10 timelines, call the script using

http://YOURSERVER/index.php?u=TWITTERUSER&l=NUMBEROFTIMELINE

eg: “http://YOURSERVER/index.php?u=creotec&l=20” will return 20 timelines.

[garethdweaver]

Check out this example for streaming tweets:
https://github.com/themattharris/tmhOAuth-examples/blob/master/userstream.php

Also here is seaofclouds jquery twitter modded plugin using tmhOAuth:

StanScates/Tweet.js-Mod

[testwitto]

Agreed, seriously what is Twitter thinking about… Who the hell do they think they are?

[martinshoe]

Thanks for the quick support!
Your solution works prefect!

[kiers]

Hi All,

I’ve just found this: https://dev.twitter.com/docs/auth/application-only-auth

This makes it much more straightforward to have a centralised app if all you’re doing is searching the public tweets. Essentially it allows you register one app, and just use its two keys to perform searches, rather than needed OAuth tokens for each user.

In a nutshell:

• You send your consumer (app) keys in a simple HTTPS POST request to oauth2/token - this returns a ‘bearer’ token
• You then use the bearer key as the authorization header to any search / timeline etc requests you need to make.

And heres the best part…

The bearer token doesn’t expire.

You can make some code to submit your keys and get it back, sling it a config file and you never need to request it again (unless you opt to invalidate it). Depending on your uses, this one bearer could provision a number of websites (i.e. I user Cron jobs to fetch the tweets and cache in my own database, rather then doing a round trip to twitter on each page load, so I use 6 requests per site per hour, rather than 100s or even 1000s)

Here’s my example code to grab the bearer token (using PHP curl)

// kick things off $ch = curl_init();

//set the url
curl_setopt($ch,CURLOPT_URL, ‘https://api.twitter.com/oauth2/token’);

// must be a POST
curl_setopt($ch,CURLOPT_POST, true);

// need to post this one variable
$data = array();
$data[‘grant_type’] = “client_credentials”;
curl_setopt($ch,CURLOPT_POSTFIELDS, $data);

// set up authorization using keys from twitter app:
$consumerKey = ‘xxxxxxxxxxxx’;
$consumerSecret = ‘xxxxxxxxxxxxxxxxxxxxxxxx’;
curl_setopt($ch,CURLOPT_USERPWD, $consumerKey . ‘:’ . $consumerSecret);

// set this so we can read the returned information
curl_setopt($ch,CURLOPT_RETURNTRANSFER, true);

//execute post
$result = curl_exec($ch);

//close connection
curl_close($ch);

// spit out what the server sent back (although really we’d parse it / process it / store it / use it
print_r($result);

Hope that’s helpful,

Kiers

[kiers]

Hi All,

Check this out: https://dev.twitter.com/docs/auth/application-only-auth

Application-only auth allows for search-type requests to be carried out without being linked to a specific user account. Obviously can’t therefore post tweets, but for sucking down a twitter feed to display on a site, it’s ideal.

You do need to create an App, but it does mean that you could use that one App to provision twitter feeds on a number of client websites (subject to the rate limit - probably best done by pulling tweets down on a schedule and storing in a database, rather than per user/pageview)

Essentially, you request a ‘Bearer Token’ for your app by sending in your Consumer Key and Secret - just those 2, as opposed to the 4 required for Application & User Auth.

The returned ‘Bearer Token’ doesn’t expire (unless you invalidate it) so once you have it, you can store in in config files / databases etc and simply use it as an Authorization header in a standard HTTP GET request - no need for funky OAuth libraries - just PHP & curl

As an example - here’s how to get your bearer token:

$ch = curl_init();

//set the endpoint url
curl_setopt($ch,CURLOPT_URL, ‘https://api.twitter.com/oauth2/token’);
// has to be a post
curl_setopt($ch,CURLOPT_POST, true);
$data = array();
$data[‘grant_type’] = “client_credentials”;
curl_setopt($ch,CURLOPT_POSTFIELDS, $data);

// here’s where you supply the Consumer Key / Secret from your app:
$consumerKey = ‘xxxxxxxxx’;
$consumerSecret = ‘yyyyyyyyyyyyyyyyyyy’;
curl_setopt($ch,CURLOPT_USERPWD, $consumerKey . ‘:’ . $consumerSecret);

curl_setopt($ch,CURLOPT_RETURNTRANSFER, true);

//execute post
$result = curl_exec($ch);

//close connection
curl_close($ch);

// show the result, including the bearer token (or you could parse it and stick it in a DB)
print_r($result);

Then, once you have the bearer token, to make a twitter request is simple:

//open connection
$ch = curl_init();
	
//set the url, including your parameters
curl_setopt($ch,CURLOPT_URL, 'https://api.twitter.com/1.1/statuses/user_timeline.json?count=100&screen_name=twitterapi');

// add in the bearer token
$bearer = "AAAAAAAAAAAAAAAAAAAAAA.....AAAAAAAAAAAAA";	
curl_setopt($ch,CURLOPT_HTTPHEADER,array('Authorization: Bearer ' . $bearer));

curl_setopt($ch,CURLOPT_RETURNTRANSFER, true);
	
//execute request
$result = curl_exec($ch);
	
//close connection
curl_close($ch);

// Print out the JSON encoded response
print_r($result);

Hope that’s helpful!

K

[kiers]

Hi All,

Check this out: https://dev.twitter.com/docs/auth/application-only-auth

Application-only auth allows for search-type requests to be carried out without being linked to a specific user account. Obviously can’t therefore post tweets, but for sucking down a twitter feed to display on a site, it’s ideal.

You do need to create an App, but it does mean that you could use that one App to provision twitter feeds on a number of client websites (subject to the rate limit - probably best done by pulling tweets down on a schedule and storing in a database, rather than per user/pageview)

Essentially, you request a ‘Bearer Token’ for your app by sending in your Consumer Key and Secret - just those 2, as opposed to the 4 required for Application & User Auth.

The returned ‘Bearer Token’ doesn’t expire (unless you invalidate it) so once you have it, you can store in in config files / databases etc and simply use it as an Authorization header in a standard HTTP GET request - no need for funky OAuth libraries - just PHP & curl

As an example - here’s how to get your bearer token:

$ch = curl_init();

//set the endpoint url
curl_setopt($ch,CURLOPT_URL, ‘https://api.twitter.com/oauth2/token’);
// has to be a post
curl_setopt($ch,CURLOPT_POST, true);
$data = array();
$data[‘grant_type’] = “client_credentials”;
curl_setopt($ch,CURLOPT_POSTFIELDS, $data);

// here’s where you supply the Consumer Key / Secret from your app:
$consumerKey = ‘xxxxxxxxx’;
$consumerSecret = ‘yyyyyyyyyyyyyyyyyyy’;
curl_setopt($ch,CURLOPT_USERPWD, $consumerKey . ‘:’ . $consumerSecret);

curl_setopt($ch,CURLOPT_RETURNTRANSFER, true);

//execute post
$result = curl_exec($ch);

//close connection
curl_close($ch);

// show the result, including the bearer token (or you could parse it and stick it in a DB)
print_r($result);

Then, once you have the bearer token, to make a twitter request is simple:

//open connection
$ch = curl_init();
	
//set the url, including your parameters
curl_setopt($ch,CURLOPT_URL, 'https://api.twitter.com/1.1/statuses/user_timeline.json?count=100&screen_name=twitterapi');

// add in the bearer token
$bearer = "AAAAAAAAAAAAAAAAAAAAAA.....AAAAAAAAAAAAA";	
curl_setopt($ch,CURLOPT_HTTPHEADER,array('Authorization: Bearer ' . $bearer));

curl_setopt($ch,CURLOPT_RETURNTRANSFER, true);
	
//execute request
$result = curl_exec($ch);
	
//close connection
curl_close($ch);

// Print out the JSON encoded response
print_r($result);

Hope that’s helpful!

K

[jason_mayes]

Have updated script to allow for:

• Automatic hyperlinking of URLs and Hashtags / @replies
• You can now specify how many tweets you want it to return, between 1 and 20.

Same URL as before. http://goo.gl/JinwJ

[creotec]

Try http://twss.55uk.net/ to generate RSS feeds without Oauth

[jason_mayes]

Updated to v4 of my code now Same link as before.

[Techture]

You are a God. Thank you, sir.