• You probably use strict and use warnings. That catches many kinds of common errors. To do this, you'll have to fix various things like declaring your variables.
• When you're initializing the %info hash, consider using the "arrow" syntax. It's easier to read:

  our %info = (version => "0.3"
               format  => 0, 
               ...
               elite   => 1,
              );
  [download]

• With your debug statements, IMHO they're clearer if you use this syntax:

      print "This is a debug message\n" if ($debug);
  [download]

  Larry Wall's rule for how to arrange things is put the important stuff first, and in this case the message can server as documentation as well as a debugging string, so should probably go first.
• What does this mean?

  return and "Failed to login\n" unless ($http_res->is_success);
  [download]

• Several of your subs have the exact same code at the end. If possible, you should find a way to factor that out.
• Using the $& variable can slow down your script considerably, according to perlvar(1). I'm not sure if having it in an if ($debug) block helps or not. If so, maybe an eval would stop the performance hit if you aren't debugging.
• The looping construct at the end is awkward. Something like this would be clearer:

  foreach my $d (@data) {
      if ($d->[5] == 1) {
  ...
      }
  }
  [download]

• Using constants for your array subscripts would make your script clearer, and if you use the use constant technique, won't slow things down at all.

Of course, many of these are a matter of style; those are just my first impressions.

Overall, looks like a nicely written script. Thanks for posting it!