So I've found the issue and we're talking about the resolution
internally...
One of the key balances in play here is what the intent is vs. what is
valid input.
One could argue that a blank string value could be bad input and thus
it should error out (granted it should give a better error than a
500)...
But on the other hand, empty form values are kind of normal in the
HTML world, so would that be valid input in an API world?
I think we are a little *inconsistent* on a few parameters wether they
are blank or non-existing... I know for a fact that the Ruby library
sends nil/empty values along by default on a lot of parameters...
We'll discuss this internally but would welcome any suggestions from
you guys...
Jake Good
http://dev.drop.io