Dropbox webhooks for scoped app are not working properly

This is the expected behavior. Webhook notifications are only sent for changes that occur in accounts that are connected to the app. Generating an access token for the app on your account the first time connects the app to your account. Likewise, you can use the OAuth app authorization flow to have arbitrary end-users connect their own accounts to your app.

peyo, in addition to what Greg said, when you only need to link your own account to the application, generating refresh token will work in the same way as long lived access token did before. Take a look here how you can get to a refresh token. 😉 You don't need to use it, just don't revoke it.

Hope this helps.

Ok, but please include it in the webhooks documentation and tutorial because I've lost 4-5 hours until I found that.
Check this out:

https://www.dropbox.com/developers/reference/webhooks#documentation

Nothing of what you posted here is mentioned in the docs.

---

 Webhooks Overview

With webhooks, your web app can be notified when your users' files change, rather than requiring your app to frequently poll Dropbox for changes. Every time a user's files change, the webhook URI you specify will be sent an HTTP request telling it about the changes. ...

---

peyo, 🤔 What are your users? What file change are you expecting to be noted without users (even one)? There is no valid association without valid token of any kind (actually no user in this case). 😉 Read more carefully!

Hope this clarifies matter.

peyo Thanks for the feedback!

Здравко, I am the user. I've configured webhook for my account. I don't care about other users. I think that it is clear enough for everybody that you have to update the documentation.

If someone follows the tutorial (like me). Then their webhooks won't trigger.