> ## Documentation Index
> Fetch the complete documentation index at: https://ngrok.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Dropbox Webhooks

> Develop and test Dropbox webhooks from localhost.

<Note title="Need a different webhook provider?">
  If you don't see your preferred webhook provider, you can [request support for it](https://dashboard.ngrok.com/early-access#webhook-providers).
</Note>

This guide explains how to use ngrok to receive Dropbox webhooks on your localhost app.

By integrating ngrok with Dropbox, you can:

* Develop and test Dropbox webhooks locally without deploying to a public environment or setting up HTTPS.
* Inspect and troubleshoot requests from Dropbox in real time via the inspection UI and API.
* Modify and replay Dropbox webhook requests with a single click instead of reproducing events manually in your Dropbox account.
* Secure your app with Dropbox webhook validation provided by ngrok.
  Invalid requests are blocked by ngrok before reaching your app.

## What you'll need

* An [ngrok account](https://ngrok.com/signup) and your [authtoken](https://dashboard.ngrok.com/get-started/your-authtoken).
* The [ngrok agent](https://ngrok.com/download) installed.
* [Node.js](https://nodejs.org/) installed (for the sample app, or use your own app).
* A Dropbox account.

## 1. Start your app

For this tutorial, you can use the [sample Node.js app on GitHub](https://github.com/ngrok/ngrok-webhook-nodejs-sample).

To install the sample, run the following in a terminal:

```bash theme={null}
git clone https://github.com/ngrok/ngrok-webhook-nodejs-sample.git
cd ngrok-webhook-nodejs-sample
npm install
```

Then start the app:

```bash theme={null}
npm start
```

The app runs on port 3000 by default.

You can confirm it's running by visiting `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](https://dashboard.ngrok.com/get-started/your-authtoken) from the dashboard.

<Tip>
  The ngrok agent uses your authtoken to authenticate when you start a tunnel.
</Tip>

* Start ngrok:

  ```bash theme={null}
  ngrok http 3000
  ```

* Copy the URL ngrok displays.
  Your app is now exposed at that URL for use with Dropbox.

## 3. Configure Dropbox to send webhooks

Dropbox delivers webhooks through a Dropbox app.
Follow [Dropbox's webhooks documentation](https://www.dropbox.com/developers/reference/webhooks) to create an app and add your webhook, and set the following:

* **Webhook URI**: your ngrok URL (for example, `https://1a2b-3c4d-5e6f-7g8h-9i0j.ngrok.app`).

When you add the URI, Dropbox sends a one-time verification request with a challenge parameter.
Confirm your localhost app receives that request and logs the challenge in the terminal, and that the webhook shows as enabled.

### Run webhooks with Dropbox and ngrok

Dropbox sends a POST request to your app when files change in the folder your app can access.
To trigger a call, upload a file to that folder, then confirm your localhost app logs the request headers and body in the terminal.

<Note>
  The payload does not include file or folder changes; it only indicates which users have changes.
  Your app must call the Dropbox API to get the latest changes for each user.
</Note>

<Tip>
  You can grant your app full Dropbox access to receive notifications for any folder.
</Tip>

### Inspecting requests

ngrok's [Traffic Inspector](https://dashboard.ngrok.com/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.

<Info>
  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](https://dashboard.ngrok.com/settings) to capture complete request and response data.
</Info>

Use the traffic inspector to:

* 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:

1. Send a test webhook from your service to generate traffic in your Traffic Inspector.

2. Select the request you want to replay in the traffic inspector.

3. Choose your replay option:
   * Click **Replay** to send the exact same request again
   * Select **Replay with modifications** to edit the request before sending

4. (Optional) Modify the request: Edit any part of the original request, such as changing field values in the request body.

5. Send the request by clicking **Replay**.

Your local application will receive the replayed request and log the data to the terminal.

## Secure webhook requests

ngrok can verify that incoming requests are from your Dropbox webhook so only that traffic reaches your app.

<Note>
  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](/docs/pricing-limits/traffic-policy-unit-pricing/) for details.
</Note>

To add verification:

* On the [Dropbox developer site](https://www.dropbox.com/developers/apps), click your app, open the **Settings** tab, click **Show** for **App secret**, and copy the value.

* Create a Traffic Policy file named `dropbox_policy.yml`.
  Replace `{your app secret}` with the value you copied:

  ```yaml theme={null}
  on_http_request:
    - actions:
        - type: verify-webhook
          config:
            provider: dropbox
            secret: "{your app secret}"
  ```

* Restart ngrok with the policy file:

  ```bash theme={null}
  ngrok http 3000 --traffic-policy-file dropbox_policy.yml
  ```

* Upload a new file to your app folder in Dropbox to trigger the webhook.

Your app should receive the request and log it in the terminal.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.