News & Announcements User Community Developer Community

Welcome to the RingCentral Community

Please note the community is currently under maintenance and is read-only.

Make sure to review our Terms of Use and Community Guidelines.
  Please note the community is currently under maintenance and is read-only.
Home » Developers
Validation Token is not returned when creating a subscription webhook
Tags: getting started
Feb 14, 2017 at 2:58am   •   2 replies  •  0 likes
            $filter = array(
                    '/restapi/v1.0/account/~/extension',                      );                                      $paramArray     = array(                      "eventFilters" => $filter,                      "deliveryMode" => array(                                          "transportType"   => "WebHook",                                          "encryption"        => "false",                                          "address"  => "" .  $obj->GetAccessToken(),                                      ),                      );    Post Call return the following error.  WebHook URL working     {    "errorCode" : "SUB-520",    "message" : "Validation Token is not returned",    "errors" : [ {      "errorCode" : "SUB-520",      "message" : "Validation Token is not returned"    } ] 


2 Answers
answered on Feb 15, 2017 at 12:00am  
Yes. It is working now. The problem is that I did not pass validation-token to post request header. After passing validation-token to post request header and return response header with validation-token that was sent, worked properly and SubscriptionWebhook is Green now

answered on Feb 14, 2017 at 8:35am  
The requirements for a webhook to be created include RingCentral servers executing a POST request to the "deliveryMode.address" you define (this is your webhook consumer, and the URI where the webhook event requests will POST).

As part of the subscription creation process, your webhook consumer must:

1. Be web-accessible
2. Accept HTTP POST requests from RingCentral
3. Respond to the "initialization" POST request within 1000ms
4. Include a header named "Validation-Token" in the response to the "intialization" POST
5. Set the value of the "Validation-Token" header in the response to the exact value presented in the "initialization" POST request's header "validation-token" 

The error you have presented in this post, indicates that your webhook consumer (the web server which accepts the HTTP POST requests), is NOT setting a header named "Validation-Token", or if it is setting that header, the value for "Validation-Token" DOES NOT match the precise value which was presented in the "initial" POST request header "validation-token".

Does this make sense?

If not, here is a tutorial about the basics of Push Notifications with Webhooks (built in JavaScript) which shows you how to handle things properly (the tutorial also has demo code which you can easily deploy to Heroku with a one-button deployment):

If you run into issues or have any questions about the tutorial, please feel free to add them in the Github issue tracker here:


A new Community is coming to RingCentral!

Posts are currently read-only as we transition into our new platform.

We thank you for your patience
during this downtime.

Try Workflow Builder

Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!

Try RingCentral Workflow Builder

Developer Platform
Integrated Apps
App Gallery
Developer support
Games and rewards

Resource center
Product Releases
App Download
RingCentral App login
Admin Portal Login
Contact Sales
© 1999-2024 RingCentral, Inc. All rights reserved. Legal Privacy Notice Site Map Contact Us