There are many reasons that you may get an error back from WSO2 when making an API call. In order to narrow down what is causing the error there are a few steps to follow:
- Identify whether the error is coming from WSO2 or the API by following this guide
- If the error is coming from the API itself and not WSO2, then you will want to get in touch with the API Publisher (the best way to do this is by posting a question on Ask)
- If the error is coming from WSO2 then we can try to narrow down the problem by following specific troubleshooting steps based on the error code
- Find the error code that you are getting in the response body on the table below
- Identify the cause of the error listed in the table
- Follow the troubleshooting steps given (if available)
- If, after identifying the cause of the error and following any available troubleshooting steps, you are still unable to resolve the issue you are having, get in touch with the contact point listed in the table for the specific error
- If your issue has still not been resolved after following all of the steps listed above then please post your question on Ask
Error Code | Reason | Troubleshooting Steps | Point of Contact |
101000 | WSO2 Receiver Error | WSO2 Team | |
101001 | WSO2 Receiver Error | WSO2 Team | |
101500 | WSO2 Sender Error | WSO2 Team | |
101501 | WSO2 Sender Error | Link | WSO2 Team |
101503 | Connection to the backend failed | API Publisher | |
101504 | Connection to the backend timed out | API Publisher | |
101505 | Connection to the backend closed | API Publisher | |
101506 | NHTTP protocol violation | WSO2 Team | |
101507 | Connection to the backend canceled | API Publisher | |
101508 | Connection to the backend timed out | API Publisher | |
101509 | Send abort | WSO2 Team | |
101510 | Response processing failed | WSO2 Team |