Webhooks V2 Limits
In the limits and restrictions section of the webhooks v2 API documentation, it says that
"There is a limit of 1000 webhooks on each combination of application and user. In other words, you can create up to 1000 webhooks on a particular application for user Alice, but not more. On the other hand, if there are already 1000 webhooks on the app for Alice, you can still create new webhooks on the same app for user Bob, up to another 1000."
However, when creating a webhook, the webhook object does not designate a user to whom the webhook should be assigned. Can you describe further what is meant by the limit of 1000 webhooks for a user?
Thank you!
-
Hello and thank you for bearing with us - I missed this when originally posed but one of my colleagues sent it my way.
You are correct that when creating a webhook, you are not specifying a user. That said, the token used to create it includes who the user is (along with permissions and a few other things). That's how our system knows/tracks that.
Say Alice has app A and app B. App A can create up to 1,000 webhooks as Alice. App B can allso create up to 1,000 webhooks. User Bob can now do the same as well, with app A and B. When we say "create up to 1,000 webhooks" we mean that the app an set notifications on up to 1,000 resources (files or folders, at this point). So Alice's App A could set a webhook on 1,000 folders to notify of uploads, for example.
-
Hi, I have the same question as above in terms of the limit to the number of webhooks and do webhooks added to child folders count against that total? So if I have 999 webhooks will it not add webhooks to another folder with two child folders?
Also, is this limit planning to go away at some point? Can we pay to increase this limit?
Thanks!
サインインしてコメントを残してください。
コメント
4件のコメント