Welcome to the new Box Support website. Check out all the details here on what’s changed.

Webhooks, how do they work!?

New post



  • mwiller

     Hi, I'm Matt — I work on the Box .NET SDK and can help you out with this.  The null values you see are totally normal and expected in this case, so the webhook was likely created correctly.  You see the null values in this case because when the Box API returns the webhook object you created, "target" points to an object that only has the type and ID of the folder object you created the webhook — see https://developer.box.com/v2.0/reference/#create-webhook for an example.  Because this is the only information that was sent back from the API, the SDK model object can only have those fields populated.  When you get a webhook message at the URL you configured, you'll get a fuller payload object that includes more information about the item related to the event that triggered the webhook — see https://developer.box.com/v2.0/reference/#webhooks-v2 for more information. 

    Comment actions Permalink
  • clewisjwenergy

     thanks Matt for the explanation, but I'm still a bit confused. One reason is that when I call back the Webhook I created, the URL is null. How do I know what URL is being called by a webhook? 


    My second question is that via https://developer.box.com/v2.0/reference/#webhooks-v2, the docs start to talk about Notifications. When I configure a webhook, that's the payload data it's automatically passing? I do not need to make parameterized urls? That really makes my day if true! 

    Comment actions Permalink

Please sign in to leave a comment.