A Webhook API is essentially a notification in the form of code that VersionOne sends when a change is made inside the application. Instead of querying VersionOne every X number of minutes to see any changes, VersionOne posts to the webhook with the updated data when a change occurs. Outside applications are then able to consume and use this data. This allows for almost instantaneous and consistent data across all applications. Additionally, this allows for more efficient use of computing resources.


^It appears this functionality is built in VersionOne, but is not exposed for development.

Feature description through analogy, via www.sendgrid.com/blog/webhook-vs-api-whats-difference/ :
Baseball managers could really use webhooks. As the game progresses, they often want to change pitchers. To do this requires the new pitcher to first warm up in the bullpen, which is usually over 300 feet from the team’s dugout. If you watch baseball on television, you’ll often see the manager pick up a phone in the dugout. He’s making a call to the bullpen to check on the new pitcher.
• “Is he warmed up yet?”
• “Not yet”
Then he hangs up the phone. In a few minutes he’ll have to call again. Programmers would call this polling and it’s process-intensive for both sides. A webhook lets you say, “call me when he’s warmed up


  • As of 18.3, VersionOne has support for webhooks, please checkout the 18.3 release notes. The release notes provide a link to the API docs and describes how to setup a webhook via the admin section.