We're currently utilizing the V1 webhook API without specifying any organization URI. If we opt to transition to the V2 webhook API to leverage its latest features, what changes should we anticipate? Would it be necessary to create an organization account, and if so, what would be the process for assigning existing users to the organization?
Hey
An organization is just a part of our account hierarchy, and even single user accounts will have an organization, where the single user is the organization owner. Using just a personal access token, any user can call the get current user endpoint here in order to find your specific organization URI (it’ll be found as the current_organization string).
In the V2 webhook subscription you must define the intake URL, events to subscribe to, your organization URI, user URI, and scope to created a new webhook subscription. Your scope can either be the user who is creating the webhook subscription using their credentials, or an organization if the personal access token is associated with an Owner/Admin in Calendly. You cannot however scope your subscription to a specific user other yourself (or the credentials you are using to create the subscription).
Another key change to the webhook subscription is our move to URI structure for our payloads. So you may need to build in some time to configure your gateway or any code you’ve created for the V1 webhooks as you make that change.
I hope that helps! Happy scheduling! 🙂
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.