Skip to main content

Use bit.ly to create shorten urls in PHP : Part1

Bit.ly is the most popular service to create shorten urls. In 2010, they had announced 

Version 3 of the bit.ly API. They had come with some new features like click counts, 

getting bundle information, query bitly information etc... All V3 methods support identical 

JSON and XML response formats. JSONP is likewise universally supported, and many 

methods support an additional plain text response format.


I have divided the bitly session into two parts.

1) Use bit.ly to create shorten urls in PHP : Part1

2) Use bit.ly API in PHP : Part2


Let’s start with first part. Please follow these steps:

a)  Register yourself with https://bitly.com/
 
b)  Go to developers section : http://dev.bitly.com/
 
c)  On top navigation bar click on My Apps link.

d)  Go to Manage My Apps->Advanced Tab 

e)  Note down your API Key (Click on Show legacy API
     key link in Legacy API Key Section and it would show you the API key).

f)  Click on the link http://bitly.com/a/your_api_key It would show your username and 
    api key. Make sure  that both the api keys from step 5 and 6 are same.

To create shorten urls we need only username and api_key parameters.

Following is the function I had written to create shorten url using json format.

//Note* Constants like THIRD_PARTY_SHORTEN_BASE_URL are stored in 
config.php file.

//bitly_shorten_url.php

include ("config.php");

echo shorten_long_url("http://beta.growthpod.com/","json"); die;

//All bit.ly APIs support an optional return format parameter format=json so same 
convetion i had followed here

function shorten_long_url($long_url,$format = 'json') {  
              
                $authorize_url = THIRD_PARTY_SHORTEN_BASE_URL."?                  
                login=".BITLY_USERNAME."&apiKey=".BITLY_API_KEY."&longUrl=".
                $long_url."&format=".$format;
                 
                $response = file_get_contents($authorize_url);

                if($format == "json") {
                                $json_parsed = json_decode($response);

                                //I have used both status_code and status_txt parameters to test if 
                                  response in ok because as per bitly API documentation sometimes 
                                  status_code 200 doesn't mean the request id ok
                                if($json_parsed->status_code == 200 && $json_parsed->status_txt == 
                                "OK"){
                                                $shorten_url   = $json_parsed->data->url;
                                                return $shorten_url;
                                }else
                                                return 'Invalid Request';
                }else{
                                //write code for xml request here
                }
}             

It would return you the shorten url.

Thanks!!!!!!!!! Enjoy Programming :)





Labels:
Location: Sangrur, Punjab, India

Comments

Post a Comment

Thanks for your valuable comments.

Popular posts from this blog

Odoo/OpenERP: one2one relational field example

one2one relational field is deprecated in OpenERP version>5 but you can achieve the same using many2one relational field. You can achieve it in following two ways : 1) using many2one field in both the objects ( http://tutorialopenerp.wordpress.com/2014/04/23/one2one/ ) 2)  using inheritance by deligation You can easily find the first solution with little search over internet so let's start with 2nd solution. Scenario :  I want to create a one2one relation between two objects of openerp hr.employee and hr.employee.medical.details What I should do  i. Add _inherits section in hr_employee class ii. Add field medical_detail_id in hr_employee class class hr_employee(osv.osv):     _name = 'hr.employee'     _inherits = {' hr.employee.medical.details ': "medical_detail_id"}     _inherit = 'hr.employee'         _columns = {              'emp_code':fields.char('Employee Code', si
12 comments
Read more

How to draw Dynamic Line or Timeseries Chart in Java using jfreechart library?

Today we are going to write a code to draw a dynamic timeseries-cum-line chart in java.   The only difference between simple and dynamic chart is that a dynamic event is used to create a new series and update the graph. In out example we are using timer which automatically calls a funtion after every 1/4 th second and graph is updated with random data. Let's try with the code : Note : I had tried my best to provide complete documentation along with code. If at any time anyone have any doubt or question please post in comments section. DynamicLineAndTimeSeriesChart.java import java.awt.BorderLayout; import java.awt.Color; import java.awt.event.ActionEvent; import java.awt.event.ActionListener; import javax.swing.Timer; import javax.swing.JPanel; import org.jfree.chart.ChartFactory; import org.jfree.chart.ChartPanel; import org.jfree.chart.JFreeChart; import org.jfree.chart.axis.ValueAxis; import org.jfree.chart.plot.XYPlot; import
37 comments
Read more

Flickr and OAuth

What is Flickr? I think you landed on this page because you know what Flickr is, so let’s come to the point and discuss about the API. Why am explaining? Although each and everything, about API, is well documented on Flickr website here , I'm just trying to explain the whole process by dividing it into small parts. Old Authentication API The current Flickr authorization scheme is not the first one it used. In the early days of Flickr, users granted the power to an app to act on their behalf by giving  the apps their Flickr username and password. Doing so meant that in order to revoke  an app’s permission, users would have to change their Flickr password. Of course, doing that would also instantly revoke permissions of other third-­party apps with knowledge of the user’s password. The new authorization scheme is meant to correct obvious problems with the old scheme. Why should you as a user have to use your Flickr password for anything other than your dealings with Flickr?
29 comments
Read more