From 35c1ad005381030d81a1106b352a716048307e3e Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Tue, 16 Jun 2026 08:11:18 +0000 Subject: [PATCH 1/2] docs: document webhook details page and test delivery action --- apps/docs/features/webhooks.mdx | 51 +++++++++++++++++++++++++++++++-- 1 file changed, 49 insertions(+), 2 deletions(-) diff --git a/apps/docs/features/webhooks.mdx b/apps/docs/features/webhooks.mdx index 17dd1d22..ad680de5 100644 --- a/apps/docs/features/webhooks.mdx +++ b/apps/docs/features/webhooks.mdx @@ -40,11 +40,58 @@ Create a serverless function that listens for a `post.published` event from a Ma - Save your webhook, then click the 3 dots on the top right and select **Copy - secret**. You'll need this to verify the authenticity of incoming requests. + Save your webhook, then open it from the list by clicking the 3 dots and + selecting **Details**. On the webhook details page, click **Copy secret** + next to the masked secret value. You'll need this to verify the + authenticity of incoming requests. +## Inspecting webhook deliveries + +Every time an event matches a webhook's subscription, Marble queues a delivery and stores the result. You can inspect this history from the webhook details page in the dashboard. + +To open it, go to **Settings → Webhooks**, click the 3 dots on the webhook's row, and choose **Details**. + +The details page is split into two parts: + +- **Webhook settings** (side panel): edit the webhook's name, URL, payload format, enabled state, and subscribed events. Changes apply to future deliveries only. +- **Deliveries**: a paginated table of every delivery attempted for this webhook, with filters and expandable rows. + +### Filtering deliveries + +Above the deliveries table you can filter by: + +- **Status**: `pending`, `sending`, `success`, `retrying`, or `failed`. +- **HTTP response**: `2xx`, `3xx`, `4xx`, `5xx`, or `No response` (the endpoint never responded, for example on a network error or timeout). +- **Event type**: any of the events the webhook is subscribed to, such as `post.published` or `tag.created`. + +Filters can be combined and the results are paginated. + +### Reading a delivery + +Click a row to expand it and see the full delivery record: + +- **Event ID** and **event timestamp**: identify the workspace event that triggered the delivery. +- **Delivery ID**: matches the `x-marble-delivery-id` header your endpoint received. +- **Sent at**: when the most recent attempt was sent. +- **HTTP response**: the status code returned by your endpoint, or `No response` if the request never completed. +- **Duration**: how long the latest attempt took, in milliseconds. +- **Error message**: shown when the latest attempt failed, for example with a connection error or non-2xx response body. +- **Payload**: the exact JSON body that was sent. Use **Copy payload** to copy it for replay or debugging. + +Use this view to confirm whether your endpoint received an event, what it returned, and what payload it was given. + +### Sending a test webhook + +To verify that your endpoint is reachable and that your signature verification works without waiting for a real content event, click **Send test webhook** on the details page. Marble queues a test delivery against the webhook's configured URL, and a new row appears in the deliveries table once it is sent. + +This is useful when: + +- You've just created a webhook and want to confirm the URL and secret are wired up correctly. +- You've changed your endpoint's deployment or signature verification code. +- A previous delivery failed and you want to retry against the current endpoint without editing real content. + ### Verifying webhook requests To ensure that incoming webhook requests are from Marble and haven't been tampered with, you can verify the request using the webhook secret. From 903004f66743b452d4c1ed5496a31b5bae974bf5 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Tue, 16 Jun 2026 08:12:14 +0000 Subject: [PATCH 2/2] docs: expand webhooks page description for SEO --- apps/docs/features/webhooks.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/features/webhooks.mdx b/apps/docs/features/webhooks.mdx index ad680de5..f4bfb513 100644 --- a/apps/docs/features/webhooks.mdx +++ b/apps/docs/features/webhooks.mdx @@ -1,6 +1,6 @@ --- title: Webhooks -description: "Trigger site rebuilds and automate workflows when your content changes." +description: "Configure Marble webhooks to revalidate static sites, automate workflows, verify signatures, and inspect deliveries when content changes." --- Webhooks provide a powerful way to keep your site's content fresh and automate workflows. When an event occurs in your Marble workspace, such as publishing a post, Marble sends an HTTP POST payload to a URL you configure.