I am happy to announce Version 3 of the bit.ly API
At bit.ly we've been working hard to improve the speed and reliability of our API endpoints, provide simpler, more consistent response formats, and clarify our API documentation. This V3 release goes a long way towards accomplishing those goals. 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.
We have also added a simpler, more efficient method to lookup bit.ly click counts, as well as a method to query bitly.Pro domain status.
Many of these changes started as user requests, and we are looking forward to adding more API endpoints to access bit.ly data based on your feedback.
Previous versions of the API are being deprecated in favor of V3 endpoints. In a following post, we will detail the phaseout schedule. For the time being, existing API endpoints will remain active, but we encourage you to upgrade your client libraries and API calls to the newest version at your earliest convenience. Additionally, upcoming endpoints that provide increased functionality will only be rolled out via the V3 interface.
On Tue, Mar 30, 2010 at 9:18 PM, Jehiah Czebotar <jeh...@bit.ly> wrote: > I am happy to announce Version 3 of the bit.ly API
> At bit.ly we've been working hard to improve the speed and reliability > of our API endpoints, provide simpler, more consistent response > formats, and clarify our API documentation. This V3 release goes a > long way towards accomplishing those goals. 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.
> We have also added a simpler, more efficient method to lookup bit.ly > click counts, as well as a method to query bitly.Pro domain status.
> Many of these changes started as user requests, and we are looking > forward to adding more API endpoints to access bit.ly data based on > your feedback.
> Previous versions of the API are being deprecated in favor of V3 > endpoints. In a following post, we will detail the phaseout schedule. > For the time being, existing API endpoints will remain active, but we > encourage you to upgrade your client libraries and API calls to the > newest version at your earliest convenience. Additionally, upcoming > endpoints that provide increased functionality will only be rolled out > via the V3 interface.
> -- > Jehiah
> -- > You are subscribed to the bit.ly API discussion group. > To post, email to bitly-api@googlegroups.com > For more options, visit http://groups.google.com/group/bitly-api
> To unsubscribe from this group, send email to bitly-api+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
The v3 documentation mentions that Bit.ly imposes per-hour, per- minute, and per-IP rate limits for each API method, but does not mention what those limits are. Could you please discuss these? Also, do you plan on implementing a method so that we can check the rate limit status?
The ability API calls is a *VERY* welcome addition. Thank you!
-- Neil
On Mar 30, 9:18 pm, Jehiah Czebotar <jeh...@bit.ly> wrote:
> I am happy to announce Version 3 of the bit.ly API
> At bit.ly we've been working hard to improve the speed and reliability > of our API endpoints, provide simpler, more consistent response > formats, and clarify our API documentation. This V3 release goes a > long way towards accomplishing those goals. 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.
> We have also added a simpler, more efficient method to lookup bit.ly > click counts, as well as a method to query bitly.Pro domain status.
> Many of these changes started as user requests, and we are looking > forward to adding more API endpoints to access bit.ly data based on > your feedback.
> Previous versions of the API are being deprecated in favor of V3 > endpoints. In a following post, we will detail the phaseout schedule. > For the time being, existing API endpoints will remain active, but we > encourage you to upgrade your client libraries and API calls to the > newest version at your earliest convenience. Additionally, upcoming > endpoints that provide increased functionality will only be rolled out > via the V3 interface.
Nice, Any idea when Version 2 will be deprecated? I'll update my app, but as it's a windows based client their may be older version that will end-up brakeing.
On Tue, Mar 30, 2010 at 9:18 PM, Jehiah Czebotar <jeh...@bit.ly> wrote: > I am happy to announce Version 3 of the bit.ly API
> At bit.ly we've been working hard to improve the speed and reliability > of our API endpoints, provide simpler, more consistent response > formats, and clarify our API documentation. This V3 release goes a > long way towards accomplishing those goals. 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.
> We have also added a simpler, more efficient method to lookup bit.ly > click counts, as well as a method to query bitly.Pro domain status.
> Many of these changes started as user requests, and we are looking > forward to adding more API endpoints to access bit.ly data based on > your feedback.
> Previous versions of the API are being deprecated in favor of V3 > endpoints. In a following post, we will detail the phaseout schedule. > For the time being, existing API endpoints will remain active, but we > encourage you to upgrade your client libraries and API calls to the > newest version at your earliest convenience. Additionally, upcoming > endpoints that provide increased functionality will only be rolled out > via the V3 interface.
> -- > Jehiah
> -- > You are subscribed to the bit.ly API discussion group. > To post, email to bitly-api@googlegroups.com > For more options, visit http://groups.google.com/group/bitly-api
> To unsubscribe from this group, send email to bitly-api+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject.
<scott.a.herb...@googlemail.com> wrote: > Any idea when Version 2 will be deprecated? I'll update my app, but > as it's a windows based client their may be older version that will end-up > brakeing.
> So it would be nice to give ppl a cut off date.
we completely understand that it takes time to roll out application updates, so we are going to see how fast the uptake of the new v3 endpoints happens before deciding on and end-of-life for v2 endpoints. It will however be on an order of months not weeks.
On Tue, Mar 30, 2010 at 5:05 PM, Neil <nei...@gmail.com> wrote: > Jehiah,
> The v3 documentation mentions that Bit.ly imposes per-hour, per- > minute, and per-IP rate limits for each API method, but does not > mention what those limits are. Could you please discuss these? Also, > do you plan on implementing a method so that we can check the rate > limit status?
> The ability API calls is a *VERY* welcome addition. Thank you!
> -- Neil
yes and yes!
Our goal of rate limits is of course to make sure they are high enough that you can do interesting things, but low enough to stop abuse that degrades the service for everyone. We are not yet ready to expose the default limits, but are looking forward to being able to do so in the future.
I can also describe a little about how these work. The primary limits that come into play are the hourly and per-minute limits on each method. These limits are per-method, so that the limit on /v3/shorten does not impact the limit on /v3/clicks, and they re-set at the end of every hour. The per-minute limit is simply a burst limit at 1/10th the hourly limit.
As always, make sure you check for rate limit responses from the api, and if you run into any issues with the limits drop us a line at supp...@bit.ly
The batching support should alleviate some of the stress on the servers, at least from API calls. Could you please make it clear in the documentation that the batching support is limited to 15 lookup parameters. For example, if you call the clicks method, you can pass any number of hashes or short URLs as long as the combined number of both types of parameter is <= 15.
On Tue, Mar 30, 2010 at 10:31 PM, Jehiah Czebotar <jeh...@bit.ly> wrote: > On Tue, Mar 30, 2010 at 5:05 PM, Neil <nei...@gmail.com> wrote: >> Jehiah,
>> The v3 documentation mentions that Bit.ly imposes per-hour, per- >> minute, and per-IP rate limits for each API method, but does not >> mention what those limits are. Could you please discuss these? Also, >> do you plan on implementing a method so that we can check the rate >> limit status?
>> The ability API calls is a *VERY* welcome addition. Thank you!
>> -- Neil
> yes and yes!
> Our goal of rate limits is of course to make sure they are high enough > that you can do interesting things, but low enough to stop abuse that > degrades the service for everyone. We are not yet ready to expose the > default limits, but are looking forward to being able to do so in the > future.
> I can also describe a little about how these work. The primary limits > that come into play are the hourly and per-minute limits on each > method. These limits are per-method, so that the limit on /v3/shorten > does not impact the limit on /v3/clicks, and they re-set at the end of > every hour. The per-minute limit is simply a burst limit at 1/10th the > hourly limit.
> As always, make sure you check for rate limit responses from the api, > and if you run into any issues with the limits drop us a line at > supp...@bit.ly
> -- > Jehiah
> -- > You are subscribed to the bit.ly API discussion group. > To post, email to bitly-api@googlegroups.com > For more options, visit http://groups.google.com/group/bitly-api
> To unsubscribe from this group, send email to bitly-api+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
On Tue, Mar 30, 2010 at 5:38 PM, Neil <nei...@gmail.com> wrote: > The batching support should alleviate some of the stress on the > servers, at least from API calls. Could you please make it clear in > the documentation that the batching support is limited to 15 lookup > parameters. For example, if you call the clicks method, you can pass > any number of hashes or short URLs as long as the combined number of > both types of parameter is <= 15.
good catch; i'll get the docs updated to reflect that limit.
Congrats on your new API release. I've quickly read through documentation but couldn't find the "/info" API which used to be in v2. I want to get htmlTitle of the page along with the long url.
Is it deprecated? why? any plan to add htmlTitle to "/clicks" or "/ expand"? (Personal request: I want to retrieve click numbers and htmlTitle at the same time)
Anyway, "/clicks" API is cool!
On 3月31日, 午前5:18, Jehiah Czebotar <jeh...@bit.ly> wrote:
> I am happy to announce Version 3 of the bit.ly API
> At bit.ly we've been working hard to improve the speed and reliability > of our API endpoints, provide simpler, more consistent response > formats, and clarify our API documentation. This V3 release goes a > long way towards accomplishing those goals. 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.
> We have also added a simpler, more efficient method to lookup bit.ly > click counts, as well as a method to query bitly.Pro domain status.
> Many of these changes started as user requests, and we are looking > forward to adding more API endpoints to access bit.ly data based on > your feedback.
> Previous versions of the API are being deprecated in favor of V3 > endpoints. In a following post, we will detail the phaseout schedule. > For the time being, existing API endpoints will remain active, but we > encourage you to upgrade your client libraries and API calls to the > newest version at your earliest convenience. Additionally, upcoming > endpoints that provide increased functionality will only be rolled out > via the V3 interface.
On Wed, Mar 31, 2010 at 11:31 AM, Eiji Kitamura <agek...@gmail.com> wrote: > Hi,
> Congrats on your new API release. > I've quickly read through documentation but couldn't find the "/info" > API which used to be in v2. > I want to get htmlTitle of the page along with the long url.
> Is it deprecated? why? any plan to add htmlTitle to "/clicks" or "/ > expand"? > (Personal request: I want to retrieve click numbers and htmlTitle at > the same time)
> Anyway, "/clicks" API is cool!
> On 3月31日, 午前5:18, Jehiah Czebotar <jeh...@bit.ly> wrote: > > I am happy to announce Version 3 of the bit.ly API
> > At bit.ly we've been working hard to improve the speed and reliability > > of our API endpoints, provide simpler, more consistent response > > formats, and clarify our API documentation. This V3 release goes a > > long way towards accomplishing those goals. 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.
> > We have also added a simpler, more efficient method to lookup bit.ly > > click counts, as well as a method to query bitly.Pro domain status.
> > Many of these changes started as user requests, and we are looking > > forward to adding more API endpoints to access bit.ly data based on > > your feedback.
> > Previous versions of the API are being deprecated in favor of V3 > > endpoints. In a following post, we will detail the phaseout schedule. > > For the time being, existing API endpoints will remain active, but we > > encourage you to upgrade your client libraries and API calls to the > > newest version at your earliest convenience. Additionally, upcoming > > endpoints that provide increased functionality will only be rolled out > > via the V3 interface.
> > -- > > Jehiah
> -- > You are subscribed to the bit.ly API discussion group. > To post, email to bitly-api@googlegroups.com > For more options, visit http://groups.google.com/group/bitly-api
> To unsubscribe, reply using "remove me" as the subject.
You are correct that currently there is no v3 api endpoint that is similar to the v2 /info call. This is intentional while we work to restructure some of that content.
On Tue, Mar 30, 2010 at 11:31 PM, Eiji Kitamura <agek...@gmail.com> wrote: > Hi,
> Congrats on your new API release. > I've quickly read through documentation but couldn't find the "/info" > API which used to be in v2. > I want to get htmlTitle of the page along with the long url.
> Is it deprecated? why? any plan to add htmlTitle to "/clicks" or "/ > expand"? > (Personal request: I want to retrieve click numbers and htmlTitle at > the same time)
I've been going over the new API docs, and I'm trying to understand the benefits/differences between login and x_login. What's the purpose? Why would you need or want to send both parameters?
login and x_login are there to create a way for you as a developer to authenticate based on your credentials and still make operations on behalf of the user.
This allows us to give you as a developer feedback on your full request volume when performing operations on behalf of others, and helps clarify situations that would otherwise look like abuse of user credentials. It also helps direct us to the right location (the application developer) when there are problems that need to be resolved.
-- Jehiah
On Thu, Apr 1, 2010 at 4:57 PM, Jay R. [dlvr.it] <j...@dlvr.it> wrote:
> I've been going over the new API docs, and I'm trying to understand > the benefits/differences between login and x_login. What's the > purpose? Why would you need or want to send both parameters?
Great job on the new v3 APIs! I've currently got an iPhone app live that uses your APIs. One of our big asks was the ability to look up a users history so we can show them tracking information. Currently, I can only show them tracking history for URLs that they shorten on the device, but anything else done outside of our app we can't see. I know this was potentially in the works, any idea on when this might show up?
I'm happy to help with developing use cases or whatever else you might need to help light this feature up. We are working on our iPad app as well as a richer history feature would be awesome!
Thanks! Chris
On Mar 30, 1:18 pm, Jehiah Czebotar <jeh...@bit.ly> wrote:
> I am happy to announce Version 3 of the bit.ly API
> At bit.ly we've been working hard to improve the speed and reliability > of our API endpoints, provide simpler, more consistent response > formats, and clarify our API documentation. This V3 release goes a > long way towards accomplishing those goals. 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.
> We have also added a simpler, more efficient method to lookup bit.ly > click counts, as well as a method to query bitly.Pro domain status.
> Many of these changes started as user requests, and we are looking > forward to adding more API endpoints to access bit.ly data based on > your feedback.
> Previous versions of the API are being deprecated in favor of V3 > endpoints. In a following post, we will detail the phaseout schedule. > For the time being, existing API endpoints will remain active, but we > encourage you to upgrade your client libraries and API calls to the > newest version at your earliest convenience. Additionally, upcoming > endpoints that provide increased functionality will only be rolled out > via the V3 interface.
You can already get the history, albeit limited to the last 15 shortened URLs. You just have to think outside of the API box. Think RSS! Hint: that's how my iPhone app, Linkie, gets the job done.
I too would like to see an API endpoint that allows the retrieval of the history, but with paging support. That would be similar to the way the web UI currently works. While I'm at it, throw in the location and timeline data (as seen on the info pages) into the API and I'll be happy.
On Thu, Apr 8, 2010 at 12:18 AM, CDressler <chris.dress...@gmail.com> wrote: > Great job on the new v3 APIs! I've currently got an iPhone app live > that uses your APIs. One of our big asks was the ability to look up a > users history so we can show them tracking information. Currently, I > can only show them tracking history for URLs that they shorten on the > device, but anything else done outside of our app we can't see. I know > this was potentially in the works, any idea on when this might show > up?
> I'm happy to help with developing use cases or whatever else you might > need to help light this feature up. We are working on our iPad app as > well as a richer history feature would be awesome!
> Thanks! > Chris
> On Mar 30, 1:18 pm, Jehiah Czebotar <jeh...@bit.ly> wrote: >> I am happy to announce Version 3 of the bit.ly API
>> At bit.ly we've been working hard to improve the speed and reliability >> of our API endpoints, provide simpler, more consistent response >> formats, and clarify our API documentation. This V3 release goes a >> long way towards accomplishing those goals. 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.
>> We have also added a simpler, more efficient method to lookup bit.ly >> click counts, as well as a method to query bitly.Pro domain status.
>> Many of these changes started as user requests, and we are looking >> forward to adding more API endpoints to access bit.ly data based on >> your feedback.
>> Previous versions of the API are being deprecated in favor of V3 >> endpoints. In a following post, we will detail the phaseout schedule. >> For the time being, existing API endpoints will remain active, but we >> encourage you to upgrade your client libraries and API calls to the >> newest version at your earliest convenience. Additionally, upcoming >> endpoints that provide increased functionality will only be rolled out >> via the V3 interface.
>> -- >> Jehiah
> -- > You are subscribed to the bit.ly API discussion group. > To post, email to bitly-api@googlegroups.com > For more options, visit http://groups.google.com/group/bitly-api
For the /v3/shorten API the docs say to use longUrl parameter as input but the examples use the uri parameter. Which is the preferred parameter to use for v3?
> I am happy to announce Version 3 of the bit.ly API
> At bit.ly we've been working hard to improve the speed and reliability > of our API endpoints, provide simpler, more consistent response > formats, and clarify our API documentation. This V3 release goes a > long way towards accomplishing those goals. 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.
> We have also added a simpler, more efficient method to lookup bit.ly > click counts, as well as a method to query bitly.Pro domain status.
> Many of these changes started as user requests, and we are looking > forward to adding more API endpoints to access bit.ly data based on > your feedback.
> Previous versions of the API are being deprecated in favor of V3 > endpoints. In a following post, we will detail the phaseout schedule. > For the time being, existing API endpoints will remain active, but we > encourage you to upgrade your client libraries and API calls to the > newest version at your earliest convenience. Additionally, upcoming > endpoints that provide increased functionality will only be rolled out > via the V3 interface.
Thanks for the reply! Yep I'd considered doing that before but was worried it only gave the last 15 shortened URLs and was imagining all the support e-mails "where are the rest??" kind of thing. Still weighing that, but really hoping they finally give a history API! :)
On Apr 8, 12:50 am, Neil <nei...@gmail.com> wrote:
> You can already get the history, albeit limited to the last 15 > shortened URLs. You just have to think outside of the API box. Think > RSS! Hint: that's how my iPhone app, Linkie, gets the job done.
> I too would like to see an API endpoint that allows the retrieval of > the history, but with paging support. That would be similar to the way > the web UI currently works. While I'm at it, throw in the location and > timeline data (as seen on the info pages) into the API and I'll be > happy.
> On Thu, Apr 8, 2010 at 12:18 AM, CDressler <chris.dress...@gmail.com> wrote: > > Great job on the new v3 APIs! I've currently got an iPhone app live > > that uses your APIs. One of our big asks was the ability to look up a > > users history so we can show them tracking information. Currently, I > > can only show them tracking history for URLs that they shorten on the > > device, but anything else done outside of our app we can't see. I know > > this was potentially in the works, any idea on when this might show > > up?
> > I'm happy to help with developing use cases or whatever else you might > > need to help light this feature up. We are working on our iPad app as > > well as a richer history feature would be awesome!
> > Thanks! > > Chris
> > On Mar 30, 1:18 pm, Jehiah Czebotar <jeh...@bit.ly> wrote: > >> I am happy to announce Version 3 of the bit.ly API
> >> At bit.ly we've been working hard to improve the speed and reliability > >> of our API endpoints, provide simpler, more consistent response > >> formats, and clarify our API documentation. This V3 release goes a > >> long way towards accomplishing those goals. 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.
> >> We have also added a simpler, more efficient method to lookup bit.ly > >> click counts, as well as a method to query bitly.Pro domain status.
> >> Many of these changes started as user requests, and we are looking > >> forward to adding more API endpoints to access bit.ly data based on > >> your feedback.
> >> Previous versions of the API are being deprecated in favor of V3 > >> endpoints. In a following post, we will detail the phaseout schedule. > >> For the time being, existing API endpoints will remain active, but we > >> encourage you to upgrade your client libraries and API calls to the > >> newest version at your earliest convenience. Additionally, upcoming > >> endpoints that provide increased functionality will only be rolled out > >> via the V3 interface.
> >> -- > >> Jehiah
> > -- > > You are subscribed to the bit.ly API discussion group. > > To post, email to bitly-api@googlegroups.com > > For more options, visithttp://groups.google.com/group/bitly-api
