Return date format in API instance info

Ah yes, you're right.
I tested this out with `m/d/y`, so I didn't catch it...  Some unit tests would probably help.

Of course it occurs to me now that the appropriate way to do this in order to not deal with these tricking orderings is to do the replace on a letter-by-letter basis instead of over the whole string.