Re: Shorten URL and authentication token

[a...@bit.ly]

Hi Matthew --

We do have rate limits on our endpoints so depending on how popular your site is (or, really, the share buttons on your site) you might start getting error messages if you hit the shorten endpoint too many times.  Assuming the long URLs of pages on your website do not change after they are created then it would be better to instead get the short URL of the page once, perhaps when the page is generated, and then store the short URL on your server and then have your share buttons pull from that saved value rather than calling the shorten endpoint repeatedly.

Let me know if you have any other questions.

Regards,

Andrew

On Wednesday, May 8, 2013 11:38:31 AM UTC-4, Matthew Verghese wrote:

When a user clicks a share button on my site, on server side, I am creating a URL, shortening it using Bitly and returning this URL to be shared.

When creating the bitly shorten url, I am not authenticating any additional end-users and am using my developer access token(instead of login and ApiKey).

URLs created are similar to : https://api-ssl.bitly.com/v3/shorten?access_token=xxxxx&longUrl=http%3A%2F%2xxxxxxx%2F

Wondering if I will run into issues with calling the shorten api method too many times with the access_token and about concurrent requests to the API.

Do you see any issues with shortening links using this method.