What is changing?

We’ve introduced new read-only and full-access OAuth scopes for Webhooks, which allow apps to create, fetch and delete webhooks on users’ behalf.

webhooks:read

When the webhooks:read scope is selected, an app can access the endpoint below, allowing it to list webhooks associated with its user.

• GET /v1/webhooks

webhooks:full

When the webhooks:full scope is selected, an app can access the endpoints below, allowing it to list webhooks associated with its user, create and delete webhooks for them.

• GET /v1/webhooks
• POST /v1/webhooks
• DELETE /v1/webhooks/{id}

Learn more about Pipedrive webhooks here and about scopes and permission here.

Why is it changing?

We’ve implemented this change to allow flexible, more granular access to users’ data and improve app accessibility.

Migration guide

Please note that webhook-specific endpoints are still available under the admin scope. No changes were made to existing public or private apps.

We’re also working on a separate solution that would allow apps with webhooks to switch from the admin scope to a new scope without asking users to re-install the app. We’ll share more details about it soon!

If you still want to add or remove the scopes of an approved or published app, learn how changing the scopes will affect your app's existing users.

If you have any questions or comments, please let us know in the Developers’ Community.