v2 shorten only accepts apiKey parameter not api_key

[GoogleCodeExporter]

Our (untouched) bit.ly code using your v2 API has now stopped working, 
complaining of a missing api key. It seems that it now needs it called "apiKey" 
rather than "api_key"... which is what your v3 API requires.

Bit of a pain because we're now having to redeploy our apps to account for this 
:)

Original issue reported on code.google.com by james.cr...@gmail.com on 28 Feb 2011 at 1:11

[GoogleCodeExporter]

Thanks for reporting this James; unfortunately that was an undocumented feature 
even i was unaware of. 

Because the v2 documentation only referred to an "apiKey" parameter, and the v2 
api endpoints were deprecated as of March 2010, this will most likely not be 
fixed. We would encourage you to update your code to call v3 endpoints which 
have a simpler response when you make your changes.

Original comment by jehiah on 28 Feb 2011 at 2:49

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by jehiah on 28 Feb 2011 at 2:50

• Changed title: v2 shorten only accepts apiKey parameter not api_key