This issue occurs for customers using the API through JSON or XML rather than form (application/x-www-form-urlencoded ). For XML and JSON requests, the Mashape proxy parameters are not automatically appended to the request, so the customer will need to pass those through manually. The extra parameters are shown in XML below (JSON would have same values but different format): <password>9275ed1caa1e54519a50490c2f9ff03e8bf41219</password> <accessid>mashape</accessid> <transactionid>1234</transactionid>

Sorry for the inconvenience.