How can I troubleshoot Conversation API?

If you encounter any issues while using Sinch Conversation API, you may troubleshoot your issue in the following ways:

• Ensure that your Conversation API credentials have been properly included in whatever API calls you make. If this is the cause, you will normally receive an HTTP status code of 401.
   
• Determine whether you are overloading your solution by comparing your workload against the default Conversation API rate limits. If this is the cause, you will normally receive an HTTP status code of 429.
   
• If you are receiving any other HTTP error codes when you make calls, compare the HTTP code and payload against our API reference documentation. You may also review a list of common Conversation API error responses. These may provide more insight into your issue.
   
• If no HTTP errors are being returned, but you are not getting the expected result, review any Conversation API callbacks you have received for more information. These can provide insight into more downstream obstacles.
   
• Ensure that the server you are targeting in your API calls is in the same region as the one for which your Conversation API app is configured.
   
• Review the corresponding channel documentation for any channel-specific information that may be interfering with your solution.
   
• Reach out to your Sinch Account Manager for general information and to determine whether there are any issues with Sinch's system.