Webhooks overview

Webhooks allow you to monitor Box content for events, and receive notifications to a URL of your choice when they occur. For example, a workflow may include waiting for a file to be downloaded to delete a shared link. A webhook can be set on the file and upon notification of the download event, a script can launch to make an API call to delete the shared link.

Versions

There are two types of webhooks: V1 and V2, which are compared below.

For the ease of use, better security, more event triggers to choose from, and automatic retries we recommend using V2 webhooks.

V1	V2
Created in the Developer Console.	Created in the Developer Console or with an API call.
Set at the root level.	Set on specific files/folders, but cannot set at the root.
Select from 14 event triggers.	Select from 30+ event triggers.
Provides selected callback parameters.	Payload includes full object response & additional context info.
No retry mechanism after notification delivery failure.	Retries up to 5 times after notification delivery failure.
Does not support payload verification.	Supports payload verification.
Notification URL can be HTTP or HTTPS.	Notification URL must be HTTPS.
Does not scale well.	Scales well and has increased reliability.

Quick example

Create a V2 webhook that notifies your endpoint when a file is downloaded:

curl -X POST https://api.box.com/2.0/webhooks \
  -H "Authorization: Bearer ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "target": { "id": "FILE_ID", "type": "file" },
    "triggers": ["FILE.DOWNLOADED"],
    "address": "https://example.com/webhook"
  }'

Last modified on September 18, 2026

Getting started

Applications & integrations

Identity & access

Using the API

Troubleshooting

Content

Collaboration

Metadata & search

Events & webhooks

Users

Intelligent workflow

E-signatures

Security & compliance

Versions

Quick example

​Versions

​Quick example

Versions

Quick example