Webhook not receiving events from Sinch

[rms-ak]

Hello,
I've configured a webhook to accept payloads and works well using examples from the documentation manually via Postman, however I don't receive any events from Sinch when processing an SMS Conversation.

I also tried using webhook.site and I can see from their logs there are Sinch events, but checking my own logs I don't see any coming from Sinch. Is there anything I could be missing in the configs? 

[Sam_Williams]

Hello, thank you for reaching out!

To clarify, are you using Conversation API's SMS channel, or are you using the standalone SMS API? Also, can you let us know what specific events (and, in the case of Conversation, what corresponding triggers) you are trying to receive (for example, inbound messages, delivery reports, etc.)?

I'll provide some general information and resources below. Since you have already reviewed some of our documentation and tested functionality on Postman and webhook.site, you may have already seen some of this content. Note that the resources and troubleshooting steps will depend on which product you're using.

If you are using Conversation API's SMS channel, you can review this article on webhook configuration. For details on the kind of information that may be included in a Conversation API callback, see the Conversation API reference section on callbacks. When troubleshooting, ensure that you have the appropriate webhook triggers set up for Conversation API and that your target URL has been entered correctly. Additionally, note that you can configure, at most, five webhooks per Conversation API app.

If you are using the standalone SMS API, see the Webhooks section of the SMS API reference. When troubleshooting, confirm that any authentication options are up to date. And, again, ensure that your callback URL has been set for the SMS service API you are using. See our article on assigning a callback URL to an SMS service API for more information.

Note: When using Conversation API's SMS channel, the callback URL assigned to the SMS service API you added to your Conversation API app is automatically updated upon adding that SMS service API to the app. This callback URL must not be changed after configuring the SMS channel of your Conversation API app.

I'll reach out to the corresponding product teams internally. If you have any questions or would like to supply additional information, you may do so in a post here. Alternatively, feel free to send me a direct message with any relevant information or questions.

Thanks again!