diff --git a/content/guides/webhooks/index.md b/content/guides/webhooks/index.md
index b8c6a60c9..8c1e39b3e 100644
--- a/content/guides/webhooks/index.md
+++ b/content/guides/webhooks/index.md
@@ -18,34 +18,77 @@ alias_paths:
# Webhooks
-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.
+Webhooks let you monitor events in your Box account and receive real-time notifications via HTTP POST requests to a URL you specify. This enables you to automate workflows based on actions like file uploads, downloads, or deletions.
+
+For example, you might want to remove a shared link after a file is downloaded. By setting up a webhook on the file to listen for the `FILE.DOWNLOADED` event, your application can trigger a script to delete the shared link when the event occurs.
-## Versions
+## Webhook Versions
-There are two types of webhooks: V1 and V2, which are compared below.
+Box offers two versions of webhooks: V1 and V2. While both allow you to receive event notifications, V2 provides enhanced features and is recommended for most use cases.
- For the ease of use, better security, more event triggers to choose from,
- and automatic retries we recommend to use V2 webhooks.
+ For improved security, more event triggers, and automatic retries, we recommend using V2 webhooks.
-| V1 | V2 |
-| --------------------------------------------------------------------- | -------------------------------------------------------------------- |
-| Created in the [Developer Console][console]. | Created in the [Developer Console][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 10 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. |
-
-[console]: https://app.box.com/developers/console
\ No newline at end of file
+### Comparison of V1 and V2 Webhooks
+
+| Feature | V1 | V2 |
+|---------------------------------|--------------------------------------------------|---------------------------------------------------------------------|
+| Creation Method | Developer Console | Developer Console or API |
+| Target Scope | Root level only | Specific files or folders (not root) |
+| Event Triggers | 14 events | Over 30 events |
+| Payload Content | Selected callback parameters | Full object details with additional context |
+| Retry Mechanism | None | Retries up to 10 times on delivery failure |
+| Payload Verification | Not supported | Supported via HMAC signatures |
+| Notification URL Protocol | HTTP or HTTPS | HTTPS only |
+| Scalability and Reliability | Limited | High scalability and reliability |
+
+## Creating V2 Webhooks
+
+You can create V2 webhooks either through the Developer Console or via the API.
+
+### Using the Developer Console
+
+1. Navigate to your application in the [Developer Console](https://app.box.com/developers/console).
+2. Select the **Webhooks** tab.
+3. Click **Create Webhook**.
+4. Choose **V2** from the version dropdown.
+5. Fill in the required details:
+ - **Target Type**: `file` or `folder`
+ - **Target ID**: ID of the file or folder
+ - **Triggers**: Events to listen for (e.g., `FILE.UPLOADED`)
+ - **Notification URL**: HTTPS endpoint to receive notifications
+6. Click **Create Webhook** to save.
+
+### Using the API
+
+Ensure your application has the `Manage Webhooks` scope enabled.
+
+Here's an example using `curl`:
+
+```bash
+curl -X POST https://api.box.com/2.0/webhooks \
+ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "target": {
+ "id": "123456789",
+ "type": "file"
+ },
+ "address": "https://yourdomain.com/webhook",
+ "triggers": ["FILE.UPLOADED"]
+ }'
+```
+
+## Testing Webhooks
+
+Before deploying, it's crucial to test your webhook integrations. Here are some tools you can use:
+
+| Tool | URL | Description |
+|-----------|--------------------------------------------------|--------------------------------------------------------------|
+| Beeceptor | [https://beeceptor.com](https://beeceptor.com) | Create custom endpoints and inspect incoming webhook calls. |
+| Pipedream | [https://pipedream.com/requestbin](https://pipedream.com/requestbin) | Capture, log, and debug webhook payloads with ease. |