We Want to Hear From You! What Do You Want to See on the Community? Tell us here!
Forum Discussion
codeAndchill
12 days agoNew member | Level 2
Webhook does not trigger
Hello,
I have some trouble with a webhook. I think, that I gave all necessary permissions and I have enabled the webhook URL. But when moving a file to dropbox, the webhook doesn't trigger.
Here is a video:
https://www.loom.com/share/60cce3bc323b46c789a39497f838fcda
Thank you for your help
There are a few reasons you may not be seeing webhook notifications:
- Have you "linked" or "connected" or "authorized" the app to your account, before making the file changes? Webhook notifications will only be sent for changes in accounts that are connected to the app. When you create a Dropbox API app as a developer, it is not automatically connected to your account as if you were an end-user of the app. You will need to connect to it, as covered in the OAuth guide.
- Are you making changes in the same account that you've linked to the app? Similar to the above, make sure you're making changes in the correct account.
- If your app is registered for the "app folder" permission, are you making changes in the special app folder created for the app? Webhook notifications will only be sent for changes that the app can access, so Dropbox won't send webhook notifications to an app folder app for changes outside its app folder.
- Was your app configured with the "files.metadata.read" scope before you connected it to your account? For scoped apps, webhooks will only be sent for apps authorized with that scope. If you only added that scope after connecting the app to your account, you'll need to re-authorize the app to access your account with that scope enabled.
- Are you sure you've properly configured your server to handle webhook notifications at your specified URL? It may be helpful to add some logging along that code path to see where it may be breaking down.
2 Replies
- DB-Des12 days ago
Dropbox Community Moderator
There are a few reasons you may not be seeing webhook notifications:
- Have you "linked" or "connected" or "authorized" the app to your account, before making the file changes? Webhook notifications will only be sent for changes in accounts that are connected to the app. When you create a Dropbox API app as a developer, it is not automatically connected to your account as if you were an end-user of the app. You will need to connect to it, as covered in the OAuth guide.
- Are you making changes in the same account that you've linked to the app? Similar to the above, make sure you're making changes in the correct account.
- If your app is registered for the "app folder" permission, are you making changes in the special app folder created for the app? Webhook notifications will only be sent for changes that the app can access, so Dropbox won't send webhook notifications to an app folder app for changes outside its app folder.
- Was your app configured with the "files.metadata.read" scope before you connected it to your account? For scoped apps, webhooks will only be sent for apps authorized with that scope. If you only added that scope after connecting the app to your account, you'll need to re-authorize the app to access your account with that scope enabled.
- Are you sure you've properly configured your server to handle webhook notifications at your specified URL? It may be helpful to add some logging along that code path to see where it may be breaking down.
- codeAndchill11 days agoNew member | Level 2
Hi DB-Des ,
thank you. I haven't implemented oauth. That solved the issue.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.6,035 PostsLatest Activity: 2 hours ago
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!