Blog2009 ≫ bit.ly unshorten api call doesn't work :-(

Badly formatted xml, damn.

Here's their example 1 oh yeah works fine in JSON but what if I want xml 2? That's not valid xml, so my xml parser isn't picking it up. Can't have a node starting with a number like that. Why put the value in as one of the node names like that anyway? Wonder if I've done this in my own api work at all? Maybe, to give the option of returning multiple values... Ah good bit.ly/roRyu 3, and neither should you bit.ly 4.

Our new highchair 5 has been dispatched!

  1. Removed old api.bit.ly/expand?version=2.0.1&shortUrl=http://bit.ly/31IqMl&login=bitlyapidemo&apiKey=R_0da49e0a9118ff35f52f629d2d71bf07 link here.
  2. Removed old api.bit.ly/expand?version=2.0.1&shortUrl=http://bit.ly/31IqMl&login=bitlyapidemo&apiKey=R_0da49e0a9118ff35f52f629d2d71bf07&format=xml link here.
  3. Removed old bit.ly/roRyu link here.
  4. Removed old bit.ly link here.
  5. As an Amazon Associate, I earn from qualifying purchases.

Node: Javascript (programming language of the internets) on the server side.

💬 @pauly http://bit.ly/3ZKJuK How long will it be before bitly codes start with a letter again? That's how long until their api is fixed

⬅️ :: ➡️

Paul Clarkeʼs weblog - I live in Hythe near Folkestone, Kent. Wed and dad to two, I am a full stack web engineer, and I do mostly js / nodejs, some ruby, other languages etc. I like pubs, parkrun, eating, home-automation + other diy jiggery-pokery, history, tree stuff, Television, squirrels, pirates, lego, + time travel.