GithubHelp home page GithubHelp logo

bitly-api's People

Contributors

jehiah avatar mattlemay avatar

Watchers

 avatar

bitly-api's Issues

/lookup for a url shorten with custom short domain is returning bit.ly short url

What steps will reproduce the problem (provide an exact http api call 
whereappropriate)?
1. /shorten a long url using custom short domain
http://api.bitly.com/v3/shorten?login=MY_LOGIN&apiKey=MY_API_KEY&longUrl=http%3A
%2F%2Fwww.example-of-unique-link.com%2F&format=json
{ "status_code": 200, "status_txt": "OK", "data": { "long_url": 
"http:\/\/www.example-of-unique-link.com\/", "url": 
"http:\/\/my.own-doma.in\/5Lu6", "hash": "5Lu6", "global_hash": "b1tL33", 
"new_hash": 1 } }

2. /lookup for this long url
http://api.bitly.com/v3/lookup?login=MY_LOGIN&apiKey=MY_API_KEY&url=http%3A%2F%2
Fwww.example-of-unique-link.com%2F&format=json
{"status_code": 200, "data": {"lookup": [{"url": 
"http://www.example-of-unique-link.com/", "short_url": "http://bit.ly/b1tL33", 
"global_hash": "b1tL33"}]}, "status_txt": "OK"}


What is the expected output? What do you see instead?
expected:
{"status_code": 200, "data": {"lookup": [{"url": 
"http://www.example-of-unique-link.com/", "short_url": 
"http://my.own-doma.in/5Lu6", "global_hash": "b1tL33"}]}, "status_txt": "OK"}

instead:
{"status_code": 200, "data": {"lookup": [{"url": 
"http://www.example-of-unique-link.com/", "short_url": "http://bit.ly/b1tL33", 
"global_hash": "b1tL33"}]}, "status_txt": "OK"}


What version of the product are you using? On what operating system?
v3 on curl/mac


Please provide any additional information below.
Since a long url was shorten using my api key and login which has custom short 
domain set up, it was expected to retrieve (/lookup) the same short url with my 
custom short domain and not the bit.ly one.
I don't want to use /shorten again since the idea is to just check if a long 
url already exists shorten with my own custom short domain.

Original issue reported on code.google.com by [email protected] on 10 Aug 2011 at 9:21

java.lang.VeriftError: com.rosaloves.net.shourturl.bitly.bitlylmpl

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1. I'm trying to use the bitlyj-1.0.0 jar for my android application.
2. I use the method BitlyFactory.newInstance for get a user certificate and
the application crushed by this exception.


What version of the product are you using? On what operating system?
I'm using the Google api's level 3 on AVD android demo.

Please provide any additional information below.
The code from the example at page http://code.google.com/p/bitlyj/ doesn't
works for me. Can anybody please make a suggestion about the proper solution ?
Thanks,
Elad.

Original issue reported on code.google.com by [email protected] on 11 Mar 2010 at 8:50

Well formed XML chokes on '&'

I was trying one of the example urls to look at the info of a page, except
that I wanted to see the output format in xml instead of json:

http://api.bit.ly/info?version=2.0.1&hash=31IqMl,3j4ir4&login=bitlyapidemo&apiKe
y=R_0da49e0a9118ff35f52f629d2d71bf07&format=xml

Firefox complained that the xml wasn't well formed because it had an
un-escaped '&' when it should have used a & instead.

Original issue reported on code.google.com by jacob.brunson on 28 Jan 2009 at 7:52

XML response is invalid for any result collection that creates nodes by the hash name, if that hash starts with a number

What steps will reproduce the problem?
1. Make an api request on a method that returns data keyed under a hash name 
(like info).
2. Use a hash that starts with a number, specifying XML as the format:
http://api.bit.ly/expand?
version=2.0.1&shortUrl=http://bit.ly/31IqMl&login=bitlyapidemo&apiKey=R_0da49e0a
9118ff35f5
2f629d2d71bf07&format=xml

What is the expected output? What do you see instead?
A valid XML document should be returned, otherwise it's useless.

A simple solution could be to introduce a <hash> element with a required 
attribute to carry the 
actual hash: <hash name="31IqMl">...</hash>. In addition, the XML can't be 
semantic without 
consistent elements.

Original issue reported on code.google.com by [email protected] on 27 Feb 2009 at 10:38

Invalid JSON call to Shorten endpoint produces bad formated response

What steps will reproduce the problem (provide an exact http api call where
appropriate)?

1. I call the endpoint with a invalid parameter, for example
http://api.bit.ly/v3/shorten?login=digiogo&apiKey=e73334a3ee6bed79705612c&longUr
l=dasdhttp://www.fiap.com.br&format=json
2. According to the API documentation I'd receive the response with data member 
as NULL, but it returns an empty array instead.


What is the expected output?
{ "data": null, "status_code": 500, "status_txt": "INVALID_URI" }

What do you see instead?
{ "data": [ ], "status_code": 500, "status_txt": "INVALID_URI" }

What version of the product are you using? On what operating system?
v3

Original issue reported on code.google.com by [email protected] on 25 Nov 2010 at 11:42

return data is version 1.0 even if version is set to 2.0.1 (current version)

What steps will reproduce the problem?
1. follow bit.ly link or hash for /info? with version=2.0.1.
2.
3.

What is the expected output? What do you see instead?
The return result contains node "<version>1.0</version>" instead of
"<version>2.0.1</version>" as expected.

What version of the product are you using? On what operating system?
2.0.1, windows XP SP3

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 4 Dec 2009 at 9:10

404 error on /shorten with no format specified

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1. 
http://api.bit.ly/shorten?version=2.0.1&longUrl=http://www.validurl.com/blabla.h
tmll&login=USERNAME&apiKey=APIKEY&history=1 
2.(I replaced the url, API key and USERNAME for privacy concerns.)
3.

What is the expected output? What do you see instead?
I am expecting the return of a shortened url. What I get back is a 404 not 
found error.

What version of the product are you using? On what operating system?
2.0.1

Please provide any additional information below.
This is part of an automated script that sends the request to bit.ly to 
generate a link and then tweet it.

Original issue reported on code.google.com by [email protected] on 24 Feb 2011 at 8:35

CORS fails for when POST method is used

cross domain resource sharing requests fail when the XMLHttpRequest is using 
the POST method (as opposed to GET that works fine).

not sure in fact if this applies to CORS or is also an issue for normal 
requests.

reason for asking for the POST method is to support longer URL to shorten, up 
to the 2000 chars supported by the standards.

at this point, a request to shorten a URL of 2000 chars fails

Original issue reported on code.google.com by [email protected] on 16 Mar 2011 at 2:26

v2 shorten only accepts apiKey parameter not api_key

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 [email protected] on 28 Feb 2011 at 1:11

Validate API call returns no data

What steps will reproduce the problem (provide an exact http api call where
appropriate)?

http://api.bit.ly/v3/validate?x_login=notbilytapi&x_apiKey=not_apikey&apiKey=R_0
da49e0a9118ff35f52f629d2d71bf07&login=bitlyapidemo&format=json 

What is the expected output? What do you see instead?

The above example is from your documentation. My own variation using my own 
keys is structured in an identicle fashion. Both calls return no data 
whatsoever. This code was working a few weeks back.

What version of the product are you using? On what operating system?
V3 API call. Various O/S

Please provide any additional information below.

This was working fine a few weeks back. My code is unchanged and no longer 
works!

Original issue reported on code.google.com by [email protected] on 16 Nov 2010 at 9:19

Multiple encoded long Urls cannot be shortened.

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1. Try sending a shorten request for 3 urls as below :
http://api.bit.ly/v3/shorten?login=<your login>&apiKey=<your
key>&uri=http%3A%2F%2Ftr.dev.oneriot.com%2FHw3RPvCuwyVlsH_bSPtnPaQlDTxUDAhY3svB_
XfF5blu7X2R9NkDY2T6A3kRhuzgx3IdYhzzIqOwkB8QJ9UrvOltvx_aEjRzI4gbpOvHG_bYwC4Ldg2n0
Aw1l_5BPUjqHDKKtgIrtrRYzre6gs_uFsNzuEK4vMlnvgujRvZmuwUG1pP_2emP3_f5ktgqQs&uri=ht
tp%3A%2F%2Ftr.dev.oneriot.com%2FE1aOIteedp9mORbc6dSDs7O8kdfqEISNbpNuusxKzYGVt6YJ
77o7PzJ4_mu82CqZwNDozhpQoq0KgqxjMLcrnNkclEjIF_oKtXKVxdJavVmD7QYWmkUFFtJsnSwArSmf
EpPe-p3EtFxpskJhqWKZt07Ve8ytfHm9aXJsEvUAXGKnbK8kOPgywuvAU0EW8KFj6rru0h3qFLNyrTk4
eR1W0n1705YatGL7C2LfCfH2Wiao1mgyeIBHpFsjrBIgFWY4eUcjO0&uri=http%3A%2F%2Ftr.dev.o
neriot.com%2FELGRm8lCk9yLY2DxvV2d4T2pc_NGI0vsXn9ddoP0UrAMWFa2e8y7m8hYuYBZYTZIKXD
fgMBYhDSokVpkafyhYBjv13O1kSGpsUP3w95ERUUu0KNPOD8IjS4zINdfQOnnZGY_molUjYJ4lLjlMy8
-xP41nwdPqS6vZSAL0HOWlGcWXmBaOvxBB2I5g5Ai2FJy9Ik2w&uri=http%3A%2F%2Ftr.dev.oneri
ot.com%2FMmYlRRt8smq7fBnCg9QKhOK8EdbMMEru-WbHnQSEqR2LZW-Of1YDbxQ4tgobBa0RMq46QSL
cLQPZCrGtV1DcYO6f8WHvuVB1vcDA8YgOrZu6QkVU8B3UXkSTxODhPFD1YOZrefMtJTqyTCBerWbS5U4
wMyeJjm1eSJe5NH02B6kLSGJWDCdpWjyu8z2sN7yR4g&uri=http%3A%2F%2Ftr.dev.oneriot.com%
2FCllW66YqDbk5EcKNEUmeJseYjvDFPjlan2SPfWdUnv-CxVoQ7BuQ2-iXRDCRrsWn2jt0h6pvjCaqvs
3vLYIg0gFszRvyWMLS6Dqms9XCH0HSoI8lqtag5nOqGZIaVlhkpJYqSNafHApHE9NV5Wv1BDDfLC2gg_
vPnhRY3NPJN5sKA&format=xml

2. result is an OK, with only the first url shortened.
3. I tried replacing the "uri" parameter with "longUrl", but the result was
the same as 2 above.

What is the expected output? What do you see instead?
I should see 3 "data" nodes for each of the 3 longUrls

What version of the product are you using? On what operating system?
I'm using version 3.0 of the api on windows XP SP2.

Please provide any additional information below.
shortening of multiple urls used to work fine in version 2.0.1 of the api.

Original issue reported on code.google.com by [email protected] on 13 Apr 2010 at 8:23

Looks like http://api.bitly.com/v3/referrers returns only 500 records at max.

For an example, take any famous shortened URL which is clicked thousands of 
times?
1. Use http://api.bitly.com/v3/referrers to look at its analytics, you will 
need api key as well.


What is the expected output? What do you see instead?
At max, only 500 records about the referrers are available. I expected to be 
able to get to all records.

What version of the product are you using? On what operating system?
Google Chrome, on Windows 7.

Please provide any additional information below.
Is there a way I can get all referral information through API? Like, is there 
an option to look at page2, page3, page4 and get to other bunch of records?

Original issue reported on code.google.com by [email protected] on 27 Aug 2011 at 9:04

INVALID_URI error is ambiguous

What steps will reproduce the problem?
1. shorten a link with an invalid url
2. shorten a valid url that is a bit.ly link (ie: http://bit.ly/1234)
3. the error response for both is INVALID_URI but should be different

What is the expected output? What do you see instead?

the error response when shortening a link that is already a bit.ly or bitly.pro 
link should be ALREADY_A_BITLY_LINK

Original issue reported on code.google.com by jehiah on 1 Apr 2010 at 11:35

I don't think /lookup is working properly.

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1. Try http://api.bit.ly/v3/lookup?url=http://www.53crestdr.com/


What is the expected output? What do you see instead?
It returns one result: "http://bit.ly/djoycQ"
Yet I've encoded it with this link: http://bit.ly/9BbEB2
I would expect to see http://bit.ly/9BbEB2 returned as well.





Original issue reported on code.google.com by [email protected] on 12 Aug 2010 at 7:14

Bit.ly Referrers giving encoded result

What steps will reproduce the problem (provide an exact http api call where 
appropriate)?
1. Perform a V3 referrer call
2. Returned results include encoded referrer result

What is the expected output? What do you see instead?

Expected result is {:referrer => "facebook.com", :clicks => 1}, actual result 
is {:referrer => "1+kCfaqydQ8=", :clicks => 1}

What version of the product are you using? On what operating system?

Version 3 on Mac OS X 10.6.7

Original issue reported on code.google.com by [email protected] on 20 Apr 2011 at 3:19

Cannot implement bit.ly in desktop applications using OAuth 2.0

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1. Develop http://code.google.com/p/zscreen to support bit.ly
2. Attempt to perform desktop authentication using the code 
http://code.google.com/p/zscreen/source/browse/trunk/ZSS.UploadersLib/URLShorten
ers/BitlyURLShortener.cs
3. Cannot authenticate using a desktop application because OAuth 2.0 does not 
support this

What is the expected output? What do you see instead?
To be able to support desktop authentication for bit.ly possibly by supporting 
OAuth 1.0 to support user accounts in desktop applications

What version of the product are you using? On what operating system?
Latest bitly-api version 3

Please provide any additional information below.
N/A

Original issue reported on code.google.com by mcored on 11 Sep 2011 at 11:57

/v3/expand does not validate domain of shortUrl parameter

What steps will reproduce the problem?
1. /v3/expand shortUrl=http://notbitlydomain.com/1224
2. get a valid response for http://bit.ly/1234

What is the expected output? 

it should return a NOT_FOUND entry or a NOT_BITLY_DOMAIN entry and echo back  
that shortUrl

Original issue reported on code.google.com by jehiah on 8 May 2010 at 3:09

Cannot use validate API

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1./v3/validate with login, apiKey, x_login, x_apiKey and format=json.

What is the expected output? What do you see instead?
expected json:
{
    "status_code": 200, 
    "data": {
        "valid": 0
    }, 
    "status_txt": "OK"
}

but now the response has no content.


What version of the product are you using? On what operating system?
v3.0


Original issue reported on code.google.com by [email protected] on 16 Nov 2010 at 12:36

  • Merged into: #27

HTTP 405 Method not allowed with RESTful API

What steps will reproduce the problem (provide an exact http api call where
appropriate)?

Just call the clicks API function through a HTTP POST method and you'll get an 
HTTP 405 status code back.

I've tried with HTTP PUT as well, with same result.

HTTP GET seems to work just fine.

What's peculiar is that until now I've had no problems with HTTP POST for 
calling the various methods (shorten, expand, validate are the ones I've tried)


If this is by design, it'd be great if you'd put it in the ApiDocumentation 
(http://code.google.com/p/bitly-api/wiki/ApiDocumentation)

- Steffen

Original issue reported on code.google.com by [email protected] on 6 Aug 2010 at 8:13

A lot of "Unknown Errors" in bit.ly pro account

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1. Try batch shortening 100 urls.

What is the expected output? What do you see instead?
I expect a 100 short urls but some times I see Unknown Error message being
returned. Very often the errors are contiguous.

What version of the product are you using? On what operating system?
2.0.1


Original issue reported on code.google.com by [email protected] on 8 Mar 2010 at 7:03

If bit.ly api is used to shorten a url, it automatically appends a "slash" ( / ) in the end of the url.

What steps will reproduce the problem?
1. Use bit.ly api to shorten http://www.google.com
2. Take the shortened url and see the info with http://shorturl+
3. You will see the long link shown as "http://www.google.com/

What is the expected output? What do you see instead?
The short url should be generated for exactly the same URL as giving in the
api request. 

What version of the product are you using? On what operating system?
I'm using the shorten url api.

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 8 Aug 2009 at 2:51

Search Links

It would be a nice enhancement to be able to search your bit.ly links in the 
same way we're able to on the site. This way, we could offer a "You might also 
be interested in..." list based on our post titles or tags.

Original issue reported on code.google.com by [email protected] on 8 May 2011 at 1:03

Use encodeURI instead

In http://code.google.com/p/bitly-api/wiki/ApiBestPractices#URL_Encoding , it 
recommends using encodeURIComponent encode longUrl in Javascript. However, the 
API will return INVALID_URI if that's used. Instead, it should say use 
encodeURI instead.

http://betaworks.com/:
  encoded using encodeURIComponent: http%253A%252F%252Fbetaworks.com%252F
  encoded using encodeURI: http%3A%2F%2Fbetaworks.com%2F

Original issue reported on code.google.com by haochi.chen on 30 Sep 2010 at 11:14

Inconsistent casing in calais tags returned

What is the expected output? What do you see instead?

<calais><City><item>Los Angeles</item></City></calais>

and at other times (different urls):

<calais><city><item>Los Angeles</item></city></calais>

What version of the product are you using? On what operating system?

Version 2.0.1 of the API

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 31 Aug 2009 at 4:09

Allow to specify page title in /v3/shorten

Please allow to specify the page title in /v3/shorten the REST API call. Right 
now bit.ly is fetching the page title, but if page that being shortened is 
password protected, that fetch can't get the right title. 
I see that the web UI allows to edit title, so it would be also nice to be able 
to specify it upon creation of the shortened url.

Original issue reported on code.google.com by [email protected] on 1 Jun 2011 at 2:54

Twitter use of bit.ly

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
We're trying to use bit.ly to shorten URLs to our items while posting them
on Twitter. the link to twitter looks something like this (one line, long
URL is encoded):

1.
<a href="http://twitter.com/home?status={item_title} -
http://api.bit.ly/shorten?version=2.0.1&amp;login={mylogin}apiKey=R_{our_key}&lo
ngUrl={our_long_url}">LINK</a>

2.The item gets posted in twitter fine, and a short URL is presented, say
http://bit.ly/4Fn3ms

3.But when clicking on the above short link, we just get the response back:

{
    "errorCode": 0, 
    "errorMessage": "", 
    "results": {
        "http://{our_long_url}": {
            "hash": "5ZkR1z", 
            "shortKeywordUrl": "", 
            "shortUrl": "http://bit.ly/8vpdJu", 
            "userHash": "8pvdJu"
        }
    }, 
    "statusCode": "OK"
}

4.And then if I load the http://bit.ly/8vpdJu, it takes me to the item on
our portal.

What is the expected output? What do you see instead?

I guess my question is how do we integrate bit.ly to our twitter link
without going through the response, what we want is that the short link
posted in twitter take you to the item on our portal directly. Maybe we're
not doint the integration properly or this is more a twitter issue?


What version of the product are you using? On what operating system?
2.0.1

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 22 Dec 2009 at 12:29

/ endings โ€บ Differences on clicks stats

Comparing the kind-of-the-same url (http://domain.tld and http://domain.tld/) 
but not getting the same clicks count results with and without the ending slash.

Is there any way to get the same results for those two, being more than very 
similars ?

Original issue reported on code.google.com by [email protected] on 17 Jul 2011 at 9:45

lookup returns NOT_FOUND but online (from bitly site) returns short url

I am trying the look up api method... 
Please see below the request and response received. The same url when submitted 
on the bitly site returns the short url. Also sometimes resetting the api  key 
works... 

http://api.bit.ly/v3/lookup?url=http%3A%2F%2Fwww.twitter.com%2F26163249961&login
={LOGIN}&apiKey=R_542b81748f130c2487f10380560cd90c&format=json

The lookup response is:
{"status_code": 200, "data": {"lookup": [{"url": 
"http://www.twitter.com/26163249961", "error": "NOT_FOUND"}]}, "status_txt": 
"OK"}

Kindly also tell if there are any usage limits such as calls per day etc

Original issue reported on code.google.com by [email protected] on 20 Oct 2010 at 12:09

There is an error in xml document(0,0)

What steps will reproduce the problem?
Dim serializer= New XmlSerializer(GetType
(DataBatrix.bitlyAPI.bitlyShortenResponse))

        Using reader As XmlTextReader = New XmlTextReader
(RequestUrl.ToString())
          responseObj = CType(serializer.Deserialize(reader), 
DataBatrix.bitlyAPI.bitlyShortenResponse)
        End Using

What is the expected output? What do you see instead?
there is an error in xml document (0,0)

What version of the product are you using? On what operating system?
Visual Studio 2008, XP


Please provide any additional information below.
I just copied data from Api Documentation.

If I send 10 record of array it works fine.But If I am sending more than 
350 records or more than 10 records It gives me above error.
Please help me out I tried to search at internet, They were saying that 
you need to dispose your stream.
Where do I need to close the stream, I copied the same thing from Api 
Documentation and it works with 10 record of data.

Please help.

Original issue reported on code.google.com by [email protected] on 25 Oct 2009 at 6:31

Inconsistencies in error reporting

What steps will reproduce the problem?
1. Execute the /expand, /info and /stats methods using a non-existent hash as 
the argument 
(like 1234THISISFAKE4321).
2. Compare the results.

What is the expected output? What do you see instead?
I expected the error reporting to be consistent about these calls, as they all 
deal with single or 
batch requests, and they all operate on already-shortened URLs.

/info Behaves in what may be the most logical way. If the method itself 
executes without error 
(barring invalid results), no error is reported in the top-level error keys. If 
the requested 
hash/url doesn't exist, that error is reported within the relevant key (the 
submitted hash/url) 
using the familiar error keys. That seems the most logical to me because it 
clearly shows two 
possible levels of errors: API/method and then method arguments.

/expand Reports an error at the top level indicating the presence of an error 
to be found in one 
of the result sets (unless there is no error). This isn't crazy because the 
code specifically 
indicates that an error in the contained batch is present. The crazy part to me 
is the 
inconsistency with /info.

/stats Doesn't seem to report any errors at all, which to me seems just plain 
wrong. If an invalid 
hash/url is provided, I would expect a relevant error to be returned.

What version of the product are you using? On what operating system?
2.1 - any

Original issue reported on code.google.com by [email protected] on 2 Mar 2009 at 9:05

only one item returned on lookup method

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
Use /v3/lookup api

What is the expected output? What do you see instead?
I would expect to get all results from the url submitted

What version of the product are you using? On what operating system?
V3 on a CentOS5 machine

Please provide any additional information below.
If I submit a url multiple times to be shortened I can receive multiple short 
urls. I would like to use the lookup method to do a reverse and grab all 
shortened urls so that I may then search another service for all instance of 
any of the short urls.

Currently the lookup method is only returning one short url. It seems to be the 
"main" while others are "branches" or something. Either way, I need the actual 
link address for all short urls for said long url to be able to correctly do 
the search.

Original issue reported on code.google.com by [email protected] on 24 Jun 2010 at 10:54

Multiple URL paramters gives same hash

What steps will reproduce the problem?
1. enter a long url such as http://test.com?id=1&name=1
2. enter another url such as http://test.com?id=1&name=2


What is the expected output? What do you see instead?
The output is the same bit.ly url, when it should be two different urls.

What version of the product are you using? On what operating system?
Using the bit.ly api, version 2.0.1.


Original issue reported on code.google.com by [email protected] on 15 Aug 2009 at 9:12

Url's shortened by using the API does not appear in History?

What steps will reproduce the problem?
1. Use the shorten REST API
2. Shorten an Url
3. Go to Url History on your account

What is the expected output? What do you see instead?
The Url appering in History

What version of the product are you using? On what operating system?
Its used by our Twitter/Dynamics CRM integration. The bit.ly API wrapper 
is a .NET 3.5 component written in C# (using XML as the REST format)

Please provide any additional information below.
You can contact me on [email protected] for further information (Code, 
etc)

Original issue reported on code.google.com by [email protected] on 3 Jun 2009 at 8:33

Missing CORS support for qrcodes

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1. Add an image to a HTML5 canvas using a bit.ly qrcode as a source
2. Attempt to call toDataURL on the canvas

What is the expected output? What do you see instead?

Expected result is to get a dataURL, however a security exception is raised 
instead due to cross-origin restrictions.

Please provide any additional information below.

Bit.ly is not returning the appropriate CORS headers along with qrcode images, 
which prevents the 'Not tainting the canvas element' use case as documented 
here:

http://www.w3.org/TR/cors/#use-cases


Original issue reported on code.google.com by [email protected] on 17 May 2011 at 12:24

Parameter documentation clicks_by_day

clicks_by_day accepts the parameter 'days'. this is shown in the example URI 
but would also be nice to have it in the list of parameters.

can you please add that parameter to the documentation?

Original issue reported on code.google.com by [email protected] on 5 Jan 2011 at 11:44

Get all shortURL of a longURL

It would be nice if i could get the shortURLs created by any users for a
given longURL, not just my personal shortURL.

I need this to search twitter for all tweets linked to an URL.

Original issue reported on code.google.com by [email protected] on 3 Jul 2009 at 5:31

Keep receiving 503: Unknown Error when doing 'referrers' call

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1.Call with a normal account's login and api_key: 
http://api.bitly.com/v3/referrers

What is the expected output? What do you see instead?
Expected to receive response with referrers of certain links; while now always 
getting 503 errors

What version of the product are you using? On what operating system?
API version: v3; OS: MacOS & Linux

Please provide any additional information below.
Found this since 5 hours ago

Original issue reported on code.google.com by [email protected] on 16 Mar 2011 at 3:54

v2 /shorten seems to be ignoring domain

What steps will reproduce the problem (provide an exact http api call where
appropriate)?

Send a request to a version 2 url seems to be ignoring the requested domian.

1. Request URL: 

http://api.j.mp/shorten?login=globocore&version=2.0.1&apiKey=R_9a3a17fe7ab262e23
e72f853bd46fcdd&format=json&longUrl=http%3A%2F%2Fmyurl.com%2Fsome_url%2F

2. Response: 

{"errorCode": 0, "errorMessage": "", "results": {"http://myurl.com/some_url/": 
{"userHash": "cmjTQg", "shortKeywordUrl": "", "hash": "c9vu62", 
"shortCNAMEUrl": "http://bit.ly/cmjTQg", "shortUrl": "http://bit.ly/cmjTQg"}}, 
"statusCode": "OK"}


What is the expected output? What do you see instead?

Expected response: '{"errorCode": 0, "errorMessage": "", "results": 
{"http://myurl.com/some_url/": {"userHash": "cmjTQg", "shortKeywordUrl": "", 
"hash": "c9vu62", "shortCNAMEUrl": "http://j.mp/cmjTQg", "shortUrl": 
"http://j.mp/cmjTQg"}}, "statusCode": "OK"}'


What version of the product are you using? On what operating system?
Version 2.0.1 tested on a Mac Snow Leopard and a Ubuntu 9

Please provide any additional information below.

This was working fine until yesterday.

Original issue reported on code.google.com by [email protected] on 24 Feb 2011 at 5:05

not able to short follwing URL

What steps will reproduce the problem (provide an exact http api call where
appropriate)?


i am trying to short follwing url but it will not short as expected it will
just cut after some string. but it will work fine in bit.ly website

http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=2801+Ocean+P
ark+Blvd&city=Santa+Monica&state=CA&csz=Santa+Monica,+CA+90
405-5200&slt=34.018220&sln=-118.457158&name=&zip=90405-5200
&country=us&&BFKey=&BFCat=&BFClient=&mag=6&desc=&cs=9&ne
wmag=8&poititle=&poi=&ds=n 

What is the expected output? What do you see instead?
it will short my URL

What version of the product are you using? On what operating system?
Version 3 and windows xp

Please provide any additional information below.
http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=2801+Ocean+P
ark+Blvd&city=Santa+Monica&state=CA&csz=Santa+Monica,+CA+90
405-5200&slt=34.018220&sln=-118.457158&name=&zip=90405-5200
&country=us&&BFKey=&BFCat=&BFClient=&mag=6&desc=&cs=9&ne
wmag=8&poititle=&poi=&ds=n 

Original issue reported on code.google.com by [email protected] on 13 Apr 2010 at 9:19

API end-points works incorrect for users with "_" in login.

I have signed up with my Twitter account. I have "_" in my login.
When I try to call something end-point I get error 500 (INVALID_LOGIN) every 
times. Looks like it is happened because user login can contain only letters or 
numbers.

Please correct me if I am wrong.

Thanks.

Original issue reported on code.google.com by [email protected] on 15 Aug 2011 at 10:56

CORS fails for &format=txt request

cross-origin resource sharing requests fails when format=txt is used

exact same request with format=xml or without format= works cross domain

Original issue reported on code.google.com by [email protected] on 16 Mar 2011 at 2:23

misleading error on an invalid api endpoint

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1. Do a HTTP GET request to: 
http://api.bit.ly/v3/prodomain?format=xml&login=bugmenot123&apiKey=R_5a182197450
5ebd314fd18e26eb6c47d&domain=pep.si

Either I expected this to be a valid pro domain (it's mentioned as an example 
at your page) or I expected an ordinary xml result like this:

<?xml version="1.0" encoding="UTF-8"?>
<response>
    <status_code>200</status_code>
    <data>
        <domain>nyti.ms</domain>
        <bitly_pro_domain>1</bitly_pro_domain>
    </data>
    <status_txt>OK</status_txt>
</response>

Instead I get this:

<bitly><errorCode>201</errorCode><errorMessage>Missing parameter 
version</errorMessage><statusCode>ERROR</statusCode></bitly>


Do note that if I call the pro_domain function for nyti.ms I still get the 
"weird" error.


Also note that I get the same "weird" error if I use json format, it's just 
formatted as json in that case.

With regards
Steffen

Original issue reported on code.google.com by [email protected] on 18 Aug 2010 at 3:48

bug in lookup api on unicode characters

What steps will reproduce the problem (provide an exact http api call where
appropriate)?
1. 
http://api.bit.ly/v3/lookup?url=http://zunguzungu.wordpress.com/2010/11/29/julia
n-assange-and-the-computer-conspiracy-%E2%80%9Cto-destroy-this-invisible-governm
ent%E2%80%9D


What is the expected output? What do you see instead?
I would expect the link to resolve to http://bit.ly/ftdcNl+

What version of the product are you using? On what operating system?


Please provide any additional information below.
The encoded values in the url are \u201c and \u201d , left and right quote 
respectively. 

When passed to the lookup api either on its own or within a multiple url lookup 
the entire response returns:

{"status_code": 500, "data": null, "status_txt": "UNKNOWN_ERROR"}

What I would expect to happen is that the request return 200 with just this url 
returning an error.

My suspicion is that there is a parser in the library you are using to parse 
the urls from within the  query string.

Original issue reported on code.google.com by [email protected] on 30 Nov 2010 at 11:07

CORS support incomplete for error conditions on some api endpoints

CORS supported added on 15-Dec-2010 - allows *any* domain to use the API.

Here's a demo: http://jsbin.com/ogoga3/

It will show 'fail' if it doesn't work, and 'works!' if it does.

The source code: http://jsbin.com/ogoga3/edit/

XHR is complaining: 

"XMLHttpRequest cannot load [snip url requested]. Origin http://jsbin.com is 
not allowed by Access-Control-Allow-Origin."

Suggesting that CORS isn't working ;-(

Original issue reported on code.google.com by [email protected] on 17 Dec 2010 at 12:29

Thumnail URL's retrieved via info on an URL give AccessDenied

What steps will reproduce the problem?
1. Request info on some link, ie.
http://api.bit.ly/info?version=2.0.1&hash=bnb3z&login=birdbook&apiKey=R_affa2d13
07feebb21990cfff93220603&keys=thumbnail
2. See the result which includes thumbnail URLs, like:
http://s.bit.ly/bitly/a9ZjH/thumbnail_large.png
3. See the output: XML which says: AccessDenied


I cannot find any documentation about using thumbnails of links. Nor can I
find how to authenticate myself for using that URL. Where do I start
looking? Googling about this sort of stuff leads me to nothing...

Original issue reported on code.google.com by jan%[email protected] on 25 Jun 2009 at 2:51

invalid code response when trying to get the access token

I used the "https://bit.ly/oauth/authorize" API and get the code in the 
redirect uri http service, when the service tried to get the access token using 
the API "https://api-ssl.bitly.com/oauth/access_token", it always returns the 
response:
INVALID_CODE

The code is returned by the bit.ly service, so I don't think the code is 
invalid. I also checked the client_id and client_secret again, there is no 
typo. Is there any other reason to get the "INVALID_CODE" response?

Thanks,
Juan


Original issue reported on code.google.com by [email protected] on 17 Jun 2011 at 5:25

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.