Thanks Twitter. Not only have you removed open access to public Twitter timelines, you’re expecting developers to contend with cryptic authentication documentation!
Many of us simply want to display our own tweets on our own website, but it’s obvious Twitter prefers us to use their widgets. Despite the convoluted Twitter instructions, implementing OAuth in your lovingly-crafted API 1.0 application is reasonably straight-forward if you use the libraries provided by talented group of (non-Twitter) developers .
In the example below, we’re going to apply Twitter OAuth authentication to a PHP application which previously parsed timeline data from a REST URL such as:
There are also Twitter libraries for C, Clojure, .NET, Go, Java, Node.js, Lua, Objective-C, Perl, Python and Ruby — the instructions will be similar.
Step 1: Create Your Twitter Application
Head to dev.twitter.com/apps/ and log in using your Twitter ID and password. This can be any account; your application will be able to read any other user’s timeline without their knowledge or permission (I realize that doesn’t make much sense given Twitter’s new policies, but I didn’t make the rules!)
Click the Create a new application button and enter the name and description of your application. The website should be a page where you can download your code but, since you’re still writing it, enter your home page URL and change it later. Leave the callback URL blank.
Complete the CAPTCHA and click Create.
Step 2: Create an Access Token
Click the Create my access token button at the bottom of the Details tab on your application’s page. You’ll now see various strings against:
- OAuth: Consumer key
- OAuth: Consumer secret
- Token: Access token
- Token: Access token secret
Keep the page open — you’ll need these shortly.
Step 3: Download the OAuth Library
Download Abraham Williams’ PHP Twitter OAuth library from github.com/abraham/twitteroauth.
The project contains a number of files, but the only ones you actually require are OAuth.php and twitteroauth.php in the twitteroauth folder. Copy both to a suitable folder in your application.
Step 4: Modify Your Timeline Fetching Code
Your PHP should now use code such as this to fetch a user’s timeline:
require('twitteroauth.php'); // path to twitteroauth library $consumerkey = '11111111'; $consumersecret = '22222222'; $accesstoken = '33333333'; $accesstokensecret = '44444444'; $twitter = new TwitterOAuth($consumerkey, $consumersecret, $accesstoken, $accesstokensecret); $tweets = $twitter->get('https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=craigbuckler&count=10'); print_r($tweets);
$accesstokensecret must be set to the Twitter codes generated in Step 2 above.
$twitter->get method must then be passed an appropriate REST URL. The example shows mine so you should enter your own Twitter ID for the
screen_name parameter (unless you specifically want to display my tweets moaning about Twitter?)
Run the code and, with luck, a stream of tweets should appear … in exactly the same way they did before the Twitter police insisted on restricting access to public messages. You’ll now need to format them according to the display requirements. Shesshh.
Note that TwitterOAuth’s get() method runs PHP’s
json_decode command and returns an object. If you’d prefer an associative array, change line 144 of twitteroauth.php to:
return json_decode($response, true);
Hopefully, that should provide a few months grace until Twitter force us to migrate to API 2.0 and jump through more flaming hoops. Best of luck.