Using the new PHP-Twitter API OAuth class

Since August 16 when TwitterAPI team announced the shutting down of basic authentication of Twitter API, which was deprecated on August 31, 2010, all client and browser based tweet application have been on the run for update. I think that’s the currently web buzz on tweet plugins/modules.

The fact is, Twitter API now accepts communication via OAuth and OAuth only. This gives me a big hit on all my blogs and codes …..UPDATE!

Prior to this OAuth enforcement agent, I use a nice script by Tijs Verkoyen and it works pretty good. He posted an update for the new Twitter OAuth but it’ seems there are lots of headache on it — from users comment.

I gave it a shot and this is how I got it working after some tries. You can grab the new OAuth powered Twitter API class by Tijs Verkoyen here

This is a quick example on how to use the class:

<?php
// require
require_once 'twitter.php';

// create instance
$twitter = new Twitter('<your-consumer-key>', '<your-consumer-secret>');

// get a request token
$twitter->oAuthRequestToken('<your-callback-url>');

// authorize
if(!isset($_GET['oauth_token'])) $twitter->oAuthAuthorize();

// get tokens
$response = $twitter->oAuthAccessToken($_GET['oauth_token'], $_GET['oauth_verifier']);

// output, you can use the token for setOAuthToken and setOAuthTokenSecret
var_dump($response);
?>

At this point, you need to create a consumer key and a consumer secret. Consumer? All I want to do is tweet, who is the consumer and what is been consumed? Please ask Twitter by creating an application for your blog or project.

Firstly, go to the Twitter API site to create the necessary keys. Note that you need to log in before you can continue. Fill in the necessary fields like

‘Application Name‘ – this is the name that will appear on your tweet source as in ‘about 1 hour ago via RWB’

‘Description‘ – The description if available.

‘Application Website‘

‘Application Type‘ – Browser for web applications.

‘Callback URL‘ – The return URL after authentication.(You really don’t need this for this class)

‘Access type‘ – Make sure you give your app READ AND WRITE access

Once you are done filling out the form and it submitted, you will be redirected to the APP profile page where the consumer key and consumer secret is residing.

Copy these consumer key and secret; you will also need to copy the ‘Access Token‘. You can find this by clicking on the ‘My Access Token‘ link on the right corner of the page. Copy the Access Token (oauth_token) and the Access Token Secret (oauth_token_secret). Back to the class instance; paste each string/key in the appropriate places.

// create instance
$twitter = new Twitter('[your-consumer-key]', '[your-consumer-secret]');

Referring to the code I updated to for most of my APP tweets:

public function post_twitter($text, $url, $return=0){
	require_once('twitter.php');
	$twitter = new Twitter('consumer-key', 'consumer-secret');
	//set Access Token
	$twitter->setOAuthToken('your-OAuthToken');
	//set Access Token Secret
	$twitter->setOAuthTokenSecret('your-OAuthSecret');
	//This is just for bit.ly
	$bitly = self::make_bitly($url,'json');
	$text_status = substr($text,0,128).'... '.$bitly;
	
	//Update the status
	$response = $twitter->statusesUpdate($text_status);
	if($return == 1):
		return $text_status;
	endif;
	
	//var_dump($response);
	//Note: this is the response I got when the status has already been posted
	//Fatal error:  Uncaught exception 'TwitterException' with message  'Status is a duplicate.'
	//die();
}

With this short lines of code, I found this pretty easy to use and I was able to call my APP twittering back to life.

I think is time for you to update too.

Please drop a comment, ask any question or share your preferred knowledge about this topic.

Thanks for reading.