Welcome to the RingCentral Community

Validation token is sent only once when you create a new subscription. Check out our code sample in the dev guide to implement your webhook notification.

I agree that there is still issue. But this issue may not be related to validation-token. So it's kindly misleading. The real issue is you are receiving empty notifications.

The API documentation states that there needs to be a Token Validation:

https://developers.ringcentral.com/guide/notifications/webhooks/receiving

"To ensure that the endpoints RingCentral interfaces with via webhooks are designed for RingCentral, "validation tokens" are transmitted amongst the HTTP request headers. It is the expectation of RingCentral that your webhook handler echo back this validation token in the response via an HTTP response header. "

I'm going to assume this is the primary problem, until I see otherwise from documentation provided by RingCentral, as this is the first step in the callback process.

Unfortunately, the first sentence of that paragraph in dev guide is unclear and misleading.

"To ensure that the endpoints RingCentral interfaces with via webhooks are designed for RingCentral, "validation tokens" are transmitted amongst the HTTP request headers"

This is only for the validation of the Webhook url for the first time and only one time.

The second part is critical and that is exactly the expectation

"It is the expectation of RingCentral that your webhook handler echo back this validation token in the response via an HTTP response header. "

To ECHO back this validation header. So if the request header does not send, then ECHO none. Meaning that don't set the header in the response because the server did not send it in the request header.

I will check with the author to improve the documentation soon.

There are two sections in this document that details this Validation Token. One section is called "Creating Webhooks", and the information your are providing is accurate to that.

The section I am referring to is called "Receiving Webhooks".

As I wrote, the dev guide is not precise. I will review the doc with the author and change it accordingly.

Meanwhile, I can confirm that the validation token is not required nor should be returned or set when receiving webhooks post for events. This is implemented in all of my apps and developers apps which I ever helped.

This is how I implement in my apps using Node JS.

if(req.headers.hasOwnProperty("validation-token")) {
        res.setHeader('Validation-Token', req.headers['validation-token']);
        res.statusCode = 200;
        res.end();
      } else {
        var body = []
        req.on('data', function(chunk) {
          body.push(chunk);
        }).on('end', function() {
          body = Buffer.concat(body).toString();
          var jsonObj = JSON.parse(body)
          console.log(body);
        });
        res.statusCode = 200;
        res.end();
      }

I have no problem with implementation. I guess I will create a new ticket regarding the empty body (no JSON data). So frustrating as it was working fine on our end for years and then just stopped working with no changes on our end two weeks ago.

Check this thread for a solution.

Actually I am not sure that it is recent change. Are you sure that for every notification message, your could receive a validation-token before? Maybe by design it is optional, if it's not present, you simply ignore it.

Hi Tyler, I do ignore it. But along with there being no validation token, there is also no JSON data.

I can confirm that today we are receiving the presence events (webhooks) of the account on sandbox environment.

Thanks for confirming. I tested and it works normal too.

Hello @Phong Vu, news about this?. Still today not receiving presence events using sandbox environment.

Thank you @Phong Vu, I hope the team can fix it soon, so we can continue testing.