Dropbox Source Configuration

Dropbox configuration

Create a Dropbox source, keep GET and POST enabled, and provide the configured Webhook Signing Secret values for provider signature. FastHook uses these settings to validate each Dropbox delivery before it enters the routing workflow.

{
  "type": "DROPBOX",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "DROPBOX",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["GET","POST"]
  }
}

GET validation before event POST

1. Dropbox first calls the FastHook Source URL with a GET validation request.
2. FastHook verifies the configured Dropbox token or challenge value and returns Dropbox's expected 2xx response.
3. After validation succeeds, Dropbox sends normal webhook events as POST requests to the same Source URL.

Dropbox request contract

FastHook echoes GET ?challenge=... and verifies POST x-dropbox-signature as HMAC-SHA256 hex over the raw body.

Special response: GET verification returns the exact challenge query value as text.

Dropbox headers

Preserve challenge, x-dropbox-signature when sending Dropbox test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

Dropbox setup

1. Paste the FastHook Source URL into the Dropbox App Console webhook URI field.
2. Keep GET enabled because Dropbox verifies the URI with ?challenge=...
3. Use the Dropbox app secret as the FastHook Webhook Signing Secret.

Continue with Dropbox

• Dropbox webhooks documentation
• Source operations and troubleshooting