{"id":228,"date":"2010-12-17T15:13:31","date_gmt":"2010-12-17T15:13:31","guid":{"rendered":"http:\/\/www.osd.net\/blog\/?p=228"},"modified":"2014-09-09T08:33:34","modified_gmt":"2014-09-09T08:33:34","slug":"update-twitter-status-using-php","status":"publish","type":"post","link":"https:\/\/www.osd.net\/blog\/web-development\/php\/update-twitter-status-using-php\/","title":{"rendered":"Update twitter status using php"},"content":{"rendered":"

After my first post about posting on facebook wall<\/a> had some feedback I decided to create another tutorial for twitter <\/strong>since the system is very similar.<\/p>\n

Twitter also uses oauth, so you will need to ask for the user’s permission in order to update his status (once again the “old” methods that allowed you to do anything you like if you find out the password are useless and this is a good thing).<\/p>\n

Another good reason to write this post was the fact that most of the examples (and the highest ranked on google) you find now on the web use the old method<\/strong> to update the status. That system was very simple but it is not working<\/strong> any more (since twitter switched to oauth only). So if you have a script that wants to do this just by calling an url using curl <\/strong>and authenticating with username and password stop debugging it as it will never work<\/strong>.<\/p>\n

Create twitter application<\/h1>\n

As I said, the system is very similar to the one used on facebook so if you are familiar to it you will find this familiar. If not after you will understand this I am sure that you will be able to understand the other post<\/a> also.<\/p>\n

So the first thing is to create a twitter application<\/strong>. For this, after you log in, go to http:\/\/dev.twitter.com\/apps\/new<\/a> an fill in that form. Make sure that you enter a valid callback url<\/strong>, that points to the script that will save the authentication token. (so let’s say that it will be something like http:\/\/www.example.com\/tw_users.php).<\/p>\n

Also remember to check “Read and Write<\/strong>” under Default Access Type<\/strong>.<\/p>\n

\"Create<\/a>

Create twitter application<\/p><\/div>\n

After you filled all the fields submit this form. You will be provided with an api key<\/strong> (customer key) and a customer secret<\/strong>. You will need these values in your scripts.<\/p>\n

Get user approval<\/h1>\n

Now we will create the script that asks <\/strong>the user for permissions <\/strong>to update his status. For this (and the following operations) I used a library I found google-ing for resources. You will find that library in the archive you can download after you complete reading this post.<\/p>\n

This script will do a simple thing: redirect the user to twitter with some parameters set so that he will be asked for approval.<\/p>\n

\r\n\t$connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET);\r\n\t$request_token = $connection->getRequestToken(OAUTH_CALLBACK . '?user=' . $_GET['user']);\r\n\t$token = $request_token['oauth_token'];\r\n\t$url = $connection->getAuthorizeURL($token);\r\n<\/pre>\n
Saving his access token<\/h1>\n
After the user will allow your application to update his status he will be redirected to that callback url you provided when you created the application. To that url we added the username <\/strong>(so that this application will be able to post updates at anytime for a user that gave you his username and accepted to use it)<\/p>\n
So when the user gets to this page we will save the access token like this:<\/p>\n
\r\n$connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $_SESSION['oauth_token'], $_SESSION['oauth_token_secret']);\r\n$access_token = $connection->getAccessToken($_REQUEST['oauth_verifier']);\r\n$userData['Twitter_Access_Token'] = $access_token['oauth_token'];\r\n$userData['Twitter_Access_Token_Secret'] = $access_token['oauth_token_secret'];\r\n$user_tw_username = @$_GET['user'];\r\n\/\/ save these fields in our database\r\n<\/pre>\n
The hard part is over now you just need to use the info you have.<\/p>\n
Posting new status<\/h1>\n
Now that you have the access token<\/strong> you can post updates for this user at any time.<\/p>\n
The only thing that can change this (and that you might need while testing) is the user revoking your access.<\/p>\n
For this go to your twitter account -> settings -> connections and click to the “revoke access<\/strong>” link next to the name of the application you just created.<\/p>\n
Now the easiest but most important part: sending the new status<\/strong>:<\/p>\n
\r\n\t$connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $info['tw_user_access_token'], $info['tw_access_token_secret']);\r\n\r\n\t$result = $connection->post(\r\n\t\t'statuses\/update',\r\n\t\tarray(\r\n\t\t\t'status' => $message\r\n\t\t)\r\n\t);\r\n<\/pre>\n
That’s all, you just posted your first update on twitter using php<\/strong> \ud83d\ude42<\/p>\n
For the full working example click here<\/a>.<\/p>\n
In the archive you will find all the sources you need (including that library I found for which I don’t want to take credit.. you will find author contact details in the files) and one file named README.txt that tell you what you need to customize for this script to work.<\/p>\n
I hope the post was clear enough and maybe it will help someone. If you have any questions or feedback please use the comment form below.<\/p>\n
\t
\n\t \t\n\t\t
\n\t\t\t
\n\t\t\t\t\n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t\t  \n\t\t\t<\/form>\n\t\t\t
If you liked this post 
 you can buy me a beer<\/strong><\/p>\n\t\t<\/div>\n\t<\/div><\/div>","protected":false},"excerpt":{"rendered":"
After my first post about posting on facebook wall had some feedback I decided to create another tutorial for twitter since the system is very similar. Twitter also uses oauth, so you will need to ask for the user’s permission in order to update his status (once again the “old” methods that allowed you to …<\/p>\n
Read more<\/a><\/div>\n
\n        <\/div><\/div>","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[14],"tags":[35,58,59,60],"_links":{"self":[{"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/posts\/228"}],"collection":[{"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/comments?post=228"}],"version-history":[{"count":14,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/posts\/228\/revisions"}],"predecessor-version":[{"id":1291,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/posts\/228\/revisions\/1291"}],"wp:attachment":[{"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/media?parent=228"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/categories?post=228"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.osd.net\/blog\/wp-json\/wp\/v2\/tags?post=228"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}