It appears that the object returned by the Tropo third-party service is now an InputStream rather than a JSON object, as it used to work for a successful submittal. This caused the plugin to throw an exception, as the logic to determine if the submittal was successful assumed the response would either be a map or a JSON object. We modified the expectation so that it only trys to use the put method if the resulting object was a map. This fixed the plugin in our application.