If you don’t see your preferred webhook provider, you can request support for it.
- Develop and test Box webhooks locally without deploying to a public environment or setting up HTTPS.
- Inspect and troubleshoot requests from Box in real time via the inspection UI and API.
- Modify and replay Box webhook requests with a single click instead of reproducing events manually in your Box account.
- Secure your app with Box webhook validation provided by ngrok. Invalid requests are blocked by ngrok before reaching your app.
What you’ll need
- An ngrok account and your authtoken.
- The ngrok agent installed.
- Node.js installed (for the sample app, or use your own app).
- A Box account.
1. Start your app
For this tutorial, you can use the sample Node.js app on GitHub. To install the sample, run the following in a terminal:http://localhost:3000.
The app logs request headers and body in the terminal and shows a message in the browser.
2. Expose your app with ngrok
Once your app is running locally, you’re ready to put it online securely using ngrok.- Copy your ngrok authtoken from the dashboard.
-
Start ngrok:
- Copy the URL ngrok displays. Your app is now exposed at that URL for use with Box.
3. Configure Box to send webhooks
Box V2 webhooks require a custom app that has the Manage Webhooks scope enabled and is authorized for your account. With that app in place, follow Box’s documentation for creating a V2 webhook, and set the following:- URL Address: your ngrok URL (for example,
https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app). - Content Type: a folder in your Box account for the webhook to monitor.
- Triggers: choose which events trigger the webhook (for this example, File Uploaded).
Run webhooks with Box and ngrok
With the File Uploaded trigger, Box notifies your app when a file is uploaded to the folder you selected. To trigger a webhook call, upload a file to that folder in Box. Confirm your app receives the FILE.UPLOADED event and logs the headers and body in the terminal.Inspecting requests
ngrok’s Traffic Inspector captures all requests made through your ngrok endpoint to your localhost app. Select any request to view detailed information about both the request and response.To avoid exposing secrets, accounts only collect traffic metadata by default.
You must enable full capture in the Traffic Inspector section of your account settings to capture complete request and response data.
- Validate webhook payloads and response data
- Debug request headers, methods, and status codes
- Troubleshoot integration issues without adding logging to your app
Replaying requests
Test your webhook handling code without triggering new events from your service using the Traffic Inspector’s replay feature:- Send a test webhook from your service to generate traffic in your Traffic Inspector.
- Select the request you want to replay in the traffic inspector.
-
Choose your replay option:
- Click Replay to send the exact same request again
- Select Replay with modifications to edit the request before sending
- (Optional) Modify the request: Edit any part of the original request, such as changing field values in the request body.
- Send the request by clicking Replay.
Secure webhook requests
ngrok can verify that incoming requests are from your Box webhook so only that traffic reaches your app.Webhook verification is limited to 500 validations per month on free accounts.
If you need more, you can upgrade to Hobbyist or Pay-as-you-go.
See TPU Pricing for details.
- In the Box Developer Console, open your app, go to the Webhook tab, and click Manage Signature Keys.
- On Manage Signature Keys, click Generate Key in Primary Key and click COPY to copy the primary key value.
-
Create a Traffic Policy file named
box_policy.yml. Replace{your primary key}with the value you copied: -
Restart ngrok with the policy file:
- Upload a file to the folder you selected for the webhook to trigger a request.