diff --git a/content/docs/platform/developer/webhooks/index.mdx b/content/docs/platform/developer/webhooks/index.mdx
new file mode 100644
index 000000000..f3603f1fe
--- /dev/null
+++ b/content/docs/platform/developer/webhooks/index.mdx
@@ -0,0 +1,190 @@
+---
+title: 'Webhooks'
+pageTitle: 'Webhooks'
+description: 'Receive notifications when events occur in your Novu account'
+---
+
+Webhooks makes it possible for your external systems to receive real-time notifications when specific events occur within your Novu account. They are POST requests sent to a pre-determined endpoint that you configure.
+
+This webhook feature is only have in the Team and Enterprise plans.
+
+## How it works
+
+You provide Novu with a URL (endpoint), and we send a JSON payload to that URL whenever an event happens, such as a workflow update or message delivery.
+
+For example, to receive updates at `https://api.yourservice.com/novu/webhook/`, you must configure this as your endpoint. Your server then acknowledges receipt by returning a 2xx status code (200-299).
+
+## How to add a webhook endpoint
+
+To start listening to messages, you must register your endpoint in the Novu dashboard.
+
+1. Go to the **[Webhooks](https://dashboard.novu.co/webhooks)** page in the Novu dashboard.
+2. Select the **Endpoints** tab.
+3. Click **Add Endpoint**.
+4. Select a webhook integration from the list.
+ 
+4. In the **Endpoint URL** field, enter the HTTPS URL where you want to receive the payload. You can use tools like [Webhook.site](https://webhook.site/) or [RequestBin](https://requestbin.com/) to generate a temporary URL for testing.
+5. In the **Description** field, enter a description to identify this webhook.
+6. Next, select the specific event types you want this endpoint to subscribe to.
+ 
+7. (Optional) Configure [advanced settings](/platform/developer/webhooks#advanced-configuration) for rate limits, transformations, and custom headers.
+8. Click **Create**.
+
+For frameworks that enable CSRF protection disable them and also verify the signature and timestamp when processing them.
+
+### Advanced configuration
+
+When adding or editing an endpoint, you can utilize the advanced configuration option to fine-tune how Novu communicates with your server.
+
+- **Rate limiting (Throttling)**: You can configure rate limits to effectively throttle the webhooks, ensuring Novu only sends a specific number of requests per second.
+- **Custom headers**: Custom headers can only be configured after the endpoint has been created.
+- **Transformations**: Novu uses Svix transformations feature, it let's you modify a webhook's payload and redirect it to a different URL. Visit Svix documentation to learn more.
+
+### Testing endpoints
+
+After you've added an endpoint, you can test it to be sure it's working. To do this:
+1. Click on the endpoint you want to test.
+2. Click the **Testing** tab.
+3. Select an event type you want to test with.
+ 
+4. Click **Send Example**.
+
+After sending an example event, you can view the message payload, all of the message attempts, and whether it succeeded or failed.
+
+
+
+## Verifying your webhooks signatures
+
+You must verify that the requests hitting your endpoint are actually from Novu and not a malicious actor.
+
+Novu uses Svix to sign webhooks. Svix offers a set of libraries for verifying signatures.
+
+```tsx
+import { Webhook } from "svix";
+
+const secret = "YOUR_WEBHOOK_SECRET_KEY";
+
+// These were all sent from the server
+const headers = {
+ "webhook-id": "msg_p5jXN8AQM9LWM0D4loKWxJek",
+ "webhook-timestamp": "1614265330",
+ "webhook-signature": "v1,g0hM9SsE+OTPJTGt/tmIKtSyZlE3uFJELVlNIOLJ1OE=",
+};
+const payload = '{"test": 2432232314}';
+
+const wh = new Webhook(secret);
+// Throws on error, returns the verified content on success
+const verifiedPayload = wh.verify(payload, headers);
+```
+
+Check out the Svix webhook verification documentation, for more instructions and examples of how to verify signatures.
+
+## Recovery and resending failed messages
+
+When your service experiences downtime or your endpoint is misconfigured, you can replay failed messages once you are back online.
+
+### Delivery attempts
+
+When an event cannot be delivered, Novu retries using exponential backoff. Each message is attempted based on the following schedule, where each period is started following the failure of the preceding attempt:
+
+- Immediately
+- 5 seconds
+- 5 minutes
+- 30 minutes
+- 2 hours
+- 5 hours
+- 10 hours
+- 10 hours (in addition to the previous)
+
+For example, an attempt that fails three times before eventually succeeding will be delivered roughly 35 minutes and 5 seconds following the first attempt.
+
+You can find all the historical delivery attempts for each webhook endpoint in the webhook activity tab of that endpoint.
+
+
+When your endpoint is unavailable, Novu keeps retrying according to the retry schedule. When all attempts fail for 5 days consecutively, the endpoint will be disabled and you have to manually re-enable it.
+
+### Resend a single failed event
+
+To resend an individual event:
+1. Click the **Logs** tab and find the failed message you want to replay.
+2. Under the **Webhook Attempts** section, Click the (**...**) icon
+ 
+3. Click **Resend** to attempt delivery again.
+
+### Recover all failed messages
+
+This operation causes all failed messages to a particular endpoint to be resent. To do this:
+1. Click on the endpoint from the **Endpoints** tab.
+2. Click the (**...**) icon.
+ 
+3. Click **Recover failed messages**.
+4. On the menu, select a time window to recover all failed messages from that period. For example, you can recover all fialed messages in the last 8 hours.
+ 
+
+### Replay missing messages
+
+This operation causes all messages that were never attempted for a particular endpoint to be resent. To do this:
+
+1. Click on the endpoint from the **Endpoints** tab.
+2. Click the (**...**) icon.
+3. Click **Replay missing messages**.
+4. On the menu, select a time window to replay all failed messages from that period. For example, you can replay all missing messages from the last 8 hours that were never attempted.
+ 
+
+## Managing webhooks endpoints
+
+### Enable or disable an endpoint
+
+Endpoints can be manually enabled or disabled at any time. Novu also automatically disables an endpoint when all deliveries fail for 5 consecutive days.
+
+To enable or disable an endpoint:
+1. Go to the webhook page of the Novu dashboard.
+2. Find the endpoint you want to enable or disable from the list.
+3. Click the (...) icon.
+ 
+4. Click **Disable Endpoint** or **Enable Endpoint**.
+
+### Delete an endpoint
+
+Deleting an endpoint immediately stops all future delivery attempts and removes the configuration from your account. This action is permanent.
+
+To delete an endpoint:
+1. Go to the webhook page of the Novu dashboard.
+2. Find the endpoint you want to enable or disable from the list.
+3. Click the (**...**) icon.
+4. Click **Delete**.
+
+## Troubleshooting
+
+There are some common reasons why your webhook endpoint is failing:
+
+### Not using the raw payload body
+
+Using different implementations to convert JSON payloads into strings can produce different string representations of the JSON object, which can lead to discrepancies when verifying the signature.
+
+Verify the payload exactly as it was sent, byte-for-byte or string-for-string, to ensure accurate verification.
+
+### Sending the wrong response codes
+
+When Novu receives a response with a 2xx status code, it is interpreted as a successful delivery even regardless of the response payload. Make sure to use the right response status codes so Novu knows when messages are supposed to succeed or fail.
+
+### Responses timing out
+
+Novu considers all messages that fails to send a response within 15 seconds as a failed message.
+
+For cases where your endpoint is processing complicated workflows, you can have your endpoint receive the message and add it to a queue to be processed asynchronously to avoid getting timed out.
+
+## Frequently asked questions
+
+### How do I secure my webhook endpoint?
+
+To secure your webhook endpoint, you should:
+
+1. Verify the webhook signature using the Svix library
+2. Use HTTPS for your endpoint URL
+3. Implement rate limiting to prevent abuse
+4. Keep your webhook secret secure and rotate it periodically
+
+### How can I test webhooks locally?
+
+To test webhooks locally, you can use a service like ngrok or localtunnel to expose your local server to the internet. Alternatively, you can use webhook testing services like Webhook.site or RequestBin to inspect webhook payloads.
diff --git a/content/docs/platform/developer/webhooks/meta.json b/content/docs/platform/developer/webhooks/meta.json
new file mode 100644
index 000000000..48f1a0db4
--- /dev/null
+++ b/content/docs/platform/developer/webhooks/meta.json
@@ -0,0 +1,4 @@
+{
+ "icon": "Webhook",
+ "pages": ["event-types"]
+}
diff --git a/content/docs/platform/additional-resources/webhooks.mdx b/content/docs/platform/developer/webhooks/webhooks.mdx
similarity index 100%
rename from content/docs/platform/additional-resources/webhooks.mdx
rename to content/docs/platform/developer/webhooks/webhooks.mdx
diff --git a/content/docs/platform/meta.json b/content/docs/platform/meta.json
index 9029a070e..442723fcf 100644
--- a/content/docs/platform/meta.json
+++ b/content/docs/platform/meta.json
@@ -33,6 +33,7 @@
"sdks/server",
"---Developer---",
"developer/environments",
+ "developer/webhooks",
"---Account---",
"account/authentication",
"account/roles-and-permissions",
diff --git a/public/images/developer-tools/add-webhook.png b/public/images/developer-tools/add-webhook.png
new file mode 100644
index 000000000..f9ec238eb
Binary files /dev/null and b/public/images/developer-tools/add-webhook.png differ
diff --git a/public/images/developer-tools/after-testing.png b/public/images/developer-tools/after-testing.png
new file mode 100644
index 000000000..8cef736f6
Binary files /dev/null and b/public/images/developer-tools/after-testing.png differ
diff --git a/public/images/developer-tools/delivery-attempts.png b/public/images/developer-tools/delivery-attempts.png
new file mode 100644
index 000000000..67d8e58d2
Binary files /dev/null and b/public/images/developer-tools/delivery-attempts.png differ
diff --git a/public/images/developer-tools/disable-endpoint.png b/public/images/developer-tools/disable-endpoint.png
new file mode 100644
index 000000000..3994c5cb1
Binary files /dev/null and b/public/images/developer-tools/disable-endpoint.png differ
diff --git a/public/images/developer-tools/recover-menu.png b/public/images/developer-tools/recover-menu.png
new file mode 100644
index 000000000..7cb0ca5e9
Binary files /dev/null and b/public/images/developer-tools/recover-menu.png differ
diff --git a/public/images/developer-tools/recover.png b/public/images/developer-tools/recover.png
new file mode 100644
index 000000000..f74d47aa5
Binary files /dev/null and b/public/images/developer-tools/recover.png differ
diff --git a/public/images/developer-tools/replay-menu.png b/public/images/developer-tools/replay-menu.png
new file mode 100644
index 000000000..df0514105
Binary files /dev/null and b/public/images/developer-tools/replay-menu.png differ
diff --git a/public/images/developer-tools/resend-event.png b/public/images/developer-tools/resend-event.png
new file mode 100644
index 000000000..4c1144df3
Binary files /dev/null and b/public/images/developer-tools/resend-event.png differ
diff --git a/public/images/developer-tools/testing-endpoints.png b/public/images/developer-tools/testing-endpoints.png
new file mode 100644
index 000000000..586cbffce
Binary files /dev/null and b/public/images/developer-tools/testing-endpoints.png differ
diff --git a/public/images/developer-tools/webhook-integrations.png b/public/images/developer-tools/webhook-integrations.png
new file mode 100644
index 000000000..608931b78
Binary files /dev/null and b/public/images/developer-tools/webhook-integrations.png differ