i'm having the exact same problem - same API, same error. i believe this is due to organization settings because it works for most of our customers besides one. i'm trying to narrow down and figure out which setting it is... James - any luck finding a resolution for this?