New Metrics Endpoints / OAuth2 Support!

[Matt LeMay]

Hello, bit.ly API Group Members!

We are extremely excited to announce that we have released some new link-level and user-level metrics endpoints!  These are all documented in the bit.ly API documentation at http://api.bit.ly

The new link-level metrics endpoints are:

/v3/referrers

/v3/countries

/v3/clicks_by_minute

The new user-level metrics endpoints are:

/v3/user/clicks

/v3/user/referrers

/v3/user/countries

/v3/user/realtime_links

Note that all user-level metrics endpoints must be accessed at https://api-ssl.bit.ly, and require authentication via OAuth 2. If you would like to register an OAuth application with us, please e-mail a...@bit.ly.

These new endpoints will form the basis of an API contest we plan to announce soon, and we wanted to give a head start to those of you who are already using our API!  Do not hesitate to get in touch if you have any questions or concerns -- we can't wait to see what you come up with.

Thanks so much, and all the best,

Matt LeMay

bit.ly

[Scott Herbert - Gmail]

Thanks Matt they look really great, could I ask for sample returned data on the API page. As I'm trying to update my .net library and am unsure as to what is returned by some of the new API's

/v3/referrers

states it's output is

• short_url this matches the shortUrl request parameter.
• hash this matches the hash request parameter.
• user_hash is the corresponding bit.ly user identifier.
• global_hash is the corresponding bit.ly aggregate identifier.
• referrer is a referring site for a given bit.ly link.
• referrer_app is a referring application (such as Tweetdeck) for a given bit.ly link.
• url is the URL of a referring application (such as http://tweetdeck.com).
• clicks is the number of clicks from the corresponding referrer.

but it's not clear to me if the last four items are returned more then once

eg. is the xml in the format

<?xml version="1.0" encoding="UTF-8"?>
<response>
    <status_code>200</status_code>
    <data>
        <short_url>http://bit.ly/beaWKI</short_url>
	<hash>beaWKI</hash>
	<user_hash>beaWKI</user_hash>
	<global_hash>aQvrfq</global_hash>
	<referrer_data>
		<referrer>http://techcrunch.com/</referrer>
		<referrer_app>Tweetdeck</referrer_app>
		<url>http://tweetdeck.com</url>
		<clicks>1002341</clicks>
	</referrer_data>
	<referrer_data>
		<referrer>http://news.bbc.co.uk/</referrer>
		<referrer_app>Tweetdeck</referrer_app>
		<url>http://tweetdeck.com</url>
		<clicks>17352</clicks>
	</referrer_data>
    </data>
    <status_txt>OK</status_txt>
</response>

or something else?

thanks.

--
You are subscribed to the bit.ly API discussion group.
To post, email to bitl...@googlegroups.com
For more options, visit http://groups.google.com/group/bitly-api

-- 
Post your RSS feeds to twitter with TwitterBrite,
The professional windows twitter client.
Download it at http://www.twitterbrite.com

[Matt LeMay]

Hi, Scott-

We are working on getting both JSON and XML examples up for all the new API endpoints -- in the meantime, here's some example XML output for /v3/referrers:

http://api.bit.ly/v3/referrers?shortUrl=http%3A%2F%2Fbit.ly%2Fdg9y6W&login=bitlyapidemo&apiKey=R_0da49e0a9118ff35f52f629d2d71bf07&format=xml

<response>

   <status_code>200</status_code>

   <data>

       <short_url>http://bit.ly/dg9y6W</short_url>

       <global_hash>dnd4KR</global_hash>

       <user_hash>dg9y6W</user_hash>

       <referrers>

           <referrer>direct</referrer>

           <clicks>80</clicks>

       </referrers>

       <referrers>

           <referrer>http://www.google.com/</referrer>

           <clicks>7</clicks>

       </referrers>

       <referrers>

           <referrer>http://jehiah.cz/test</referrer>

           <clicks>4</clicks>

       </referrers>

       <referrers>

           <referrer>http://bitly.org/</referrer>

           <clicks>1</clicks>

       </referrers>

       <referrers>

           <referrer>http://jehiah.cz/testb</referrer>

           <clicks>1</clicks>

       </referrers>

       <referrers>

           <referrer_app>tweetdeck</referrer_app>

           <url>http://tweetdeck.com</url>

           <clicks>1</clicks>

       </referrers>

   </data>

   <status_txt>OK</status_txt>

</response>

Thanks, and all the best,

Matt

[Scott Herbert]

Thanks Matt I'll keep an eye and the wiki (and/or play with the API's
manualy)

On Sep 22, 4:42 pm, Matt LeMay <m...@bit.ly> wrote:
> Hi, Scott-
>
> We are working on getting both JSON and XML examples up for all the new API
> endpoints -- in the meantime, here's some example XML output for
> /v3/referrers:
>

> http://api.bit.ly/v3/referrers?shortUrl=http%3A%2F%2Fbit.ly%2Fdg9y6W&...

> >    - *short_url* this matches the shortUrl request parameter.
> >    - *hash* this matches the hash request parameter.
> >    - *user_hash* is the corresponding bit.ly user identifier.
> >    - *global_hash* is the corresponding bit.ly aggregate identifier.
> >    - *referrer* is a referring site for a given bit.ly link.
> >    - *referrer_app* is a referring application (such as Tweetdeck) for a
> >    given bit.ly link.
> >    - *url* is the URL of a referring application (such as
> >    http://tweetdeck.com).
> >    - *clicks* is the number of clicks from the corresponding referrer.

>
> > but it's not clear to me if the last four items are returned more then once
>
> > eg. is the xml in the format
>
> > <?xml version="1.0" encoding="UTF-8"?><response>
> >     <status_code>200</status_code>
> >     <data>
> >         <short_url>http://bit.ly/beaWKI</short_url>
> >    <hash>beaWKI</hash>
> >    <user_hash>beaWKI</user_hash>

> >    <global_hash>aQvrfq <http://bit.ly/aQvrfq></global_hash>

> >    <referrer_data>
> >            <referrer>http://techcrunch.com/</referrer>
> >            <referrer_app>Tweetdeck</referrer_app>
> >            <url>http://tweetdeck.com</url>
> >            <clicks>1002341</clicks>
> >    </referrer_data>
> >    <referrer_data>
> >            <referrer>http://news.bbc.co.uk/</referrer>
> >            <referrer_app>Tweetdeck</referrer_app>
> >            <url>http://tweetdeck.com</url>
> >            <clicks>17352</clicks>
> >    </referrer_data>    </data>
> >     <status_txt>OK</status_txt></response>
>
> > or something else?
>
> > thanks.
>
> > On 21/09/2010 15:28, Matt LeMay wrote:
>
> > Hello, bit.ly API Group Members!
>

> >  *We are extremely excited to announce that we have released some new
> > link-level and user-level metrics endpoints*!  These are all documented in
> > the bit.ly API documentation athttp://api.bit.ly

>
> >  The new link-level metrics endpoints are:
>
> >  /v3/referrers
> > /v3/countries
> > /v3/clicks_by_minute
>
> >  The new user-level metrics endpoints are:
>
> >  /v3/user/clicks
> > /v3/user/referrers
> > /v3/user/countries
> > /v3/user/realtime_links
>
> >  Note that all user-level metrics endpoints must be accessed at

> >https://api-ssl.bit.ly, and require authentication via OAuth 2. *If you

> > would like to register an OAuth application with us, please e-mail

> > a...@bit.ly*.

>
> >  These new endpoints will form the basis of an API contest we plan to
> > announce soon, and we wanted to give a head start to those of you who are
> > already using our API!  Do not hesitate to get in touch if you have any
> > questions or concerns -- we can't wait to see what you come up with.
>
> >  Thanks so much, and all the best,
> > Matt LeMay
> > bit.ly
> > --
> > You are subscribed to the bit.ly API discussion group.
> > To post, email to bitl...@googlegroups.com

> > For more options, visithttp://groups.google.com/group/bitly-api

>
> > --
> > Post your RSS feeds to twitter with TwitterBrite,
> > The professional windows twitter client.

> > Download it athttp://www.twitterbrite.com

>
> >  --
> > You are subscribed to the bit.ly API discussion group.
> > To post, email to bitl...@googlegroups.com

> > For more options, visithttp://groups.google.com/group/bitly-api- Hide quoted text -
>
> - Show quoted text -