docs(webhooks): remove delivery history

Author: qwerzl

docs-src/webhooks/events.mdx.vel

@@ -54,8 +54,8 @@ squashed into the top-level object. There is no additional `data` wrapper.
 | `webhook-signature` | One or more space-delimited `v1,<base64>` signatures. |
 
 The event id never contains a period, so the Standard Webhooks signed-content
-serialization remains unambiguous. The same event keeps its id across retries,
-multiple endpoints, and manual replay.
+serialization remains unambiguous. The same event keeps its id across retries
+and multiple endpoints.
 
 See [Verifying signatures](/webhooks/verifying-signatures) before processing a
 delivery.

webhooks/delivery.mdx

@@ -1,6 +1,6 @@
 ---
 title: Delivery and retries
-description: Status handling, durable retries, endpoint disabling, history, and replay
+description: Status handling, durable retries, endpoint disabling, and destination security
 ---
 
 Spectrum delivers each event independently to every subscribed endpoint. A
@@ -66,60 +66,15 @@ delivery lane.
 
 If the four-day retry budget expires, Spectrum:
 
-1. records the event as `dead_lettered`;
+1. moves the event to its internal dead-letter queue;
 2. disables the endpoint with reason `delivery_failures`; and
 3. sends an email if `failureNotificationEmail` is configured.
 
 Re-enable the endpoint with `PATCH /projects/{projectId}/webhooks/{webhookId}`
 and `{ "enabled": true }` after fixing it. Future events and any retries that
-are still pending resume in endpoint order; terminal `dead_lettered` events
-require an explicit replay.
-
-## Delivery history
-
-Terminal outcomes are retained for seven days:
-
-```sh
-curl "https://spectrum.photon.codes/projects/$PROJECT_ID/webhooks/$WEBHOOK_ID/deliveries?limit=50" \
-  -u "$PROJECT_ID:$PROJECT_SECRET"
-```
-
-Each row includes the event id, event type, platform, terminal outcome,
-delivery count, final status or reason, timestamps, and whether replay is still
-available. The history table stores metadata, not the webhook payload.
-
-Use `before` for cursor pagination and `outcome=dead_lettered` to show failed
-deliveries only.
-
-## Manual replay
-
-Replay one failed event:
-
-```sh
-curl -X POST \
-  "https://spectrum.photon.codes/projects/$PROJECT_ID/webhooks/$WEBHOOK_ID/deliveries/$EVENT_ID/replay" \
-  -u "$PROJECT_ID:$PROJECT_SECRET"
-```
-
-Or replay up to 100 failures from a time range no longer than seven days:
-
-```sh
-curl -X POST \
-  "https://spectrum.photon.codes/projects/$PROJECT_ID/webhooks/$WEBHOOK_ID/deliveries/replay-failures" \
-  -u "$PROJECT_ID:$PROJECT_SECRET" \
-  -H "Content-Type: application/json" \
-  -d '{
-    "since": "2026-08-01T00:00:00Z",
-    "until": "2026-08-02T00:00:00Z",
-    "limit": 100
-  }'
-```
-
-Replay requires an enabled Fusor endpoint, a `dead_lettered` outcome, and the
-original event to remain in the seven-day source-retention window. It preserves
-the original `webhook-id`, signs the delivery with the endpoint's current
-secret, and increments the history row's replay count. Your idempotency policy
-therefore remains authoritative during replay.
+are still pending resume in endpoint order. Spectrum does not currently expose
+delivery history or manual replay, so reconcile terminal failures from your own
+source of truth.
 
 ## Destination security
 

webhooks/managing-webhooks.mdx

@@ -10,7 +10,7 @@ Webhook management uses project Basic authentication:
 ```
 
 One project can register multiple endpoints. Each endpoint has an independent
-URL, secret, subscription set, retry lane, history, and enabled state.
+URL, secret, subscription set, retry lane, and enabled state.
 
 ## Create an endpoint
 
@@ -74,7 +74,7 @@ Set `failureNotificationEmail` to `null` to remove the notification address.
 
 ## Disable or re-enable an endpoint
 
-Disable delivery without deleting the registration or its history:
+Disable delivery without deleting the registration:
 
 ```sh
 curl -X PATCH \
@@ -99,9 +99,9 @@ curl -X PATCH \
 ```
 
 Re-enabling clears the disable reason. Future events and any retries still
-pending resume in endpoint order; events already recorded as `dead_lettered`
-are not replayed automatically. Replay those eligible failures separately from
-the [delivery history](/webhooks/delivery#delivery-history).
+pending resume in endpoint order. Spectrum does not currently expose terminal
+delivery history or manual replay; reconcile terminal failures from your own
+source of truth.
 
 ## Rotate the Standard secret
 
@@ -131,20 +131,6 @@ A safe rotation sequence is:
 `overlapSeconds` defaults to one day, can be zero for immediate revocation, and
 cannot exceed seven days.
 
-## Inspect and replay failures
-
-Use the delivery endpoints to inspect seven days of terminal outcomes and
-replay eligible failures:
-
-```text
-GET  /projects/{projectId}/webhooks/{webhookId}/deliveries
-POST /projects/{projectId}/webhooks/{webhookId}/deliveries/{eventId}/replay
-POST /projects/{projectId}/webhooks/{webhookId}/deliveries/replay-failures
-```
-
-See [Delivery and retries](/webhooks/delivery) for filters, retention, and replay
-constraints.
-
 ## Retrieve egress addresses
 
 ```sh

webhooks/overview.mdx

@@ -20,7 +20,7 @@ flowchart LR
 ```
 
 You can register multiple endpoints for one project. Each endpoint has its own
-secret, subscriptions, retry lane, delivery history, and enabled state. A slow
+secret, subscriptions, retry lane, and enabled state. A slow
 or failing endpoint does not block another endpoint.
 
 ## Standard Webhooks contract
@@ -69,8 +69,6 @@ See [Events](/webhooks/events) for the complete field reference.
 - A `410 Gone` response disables the endpoint immediately.
 - An endpoint that fails throughout the retry window is disabled. If you set a
   failure-notification email, Spectrum sends a notification.
-- Terminal delivery history is available for seven days. Failed events that
-  remain in source retention can be replayed manually.
 
 See [Delivery and retries](/webhooks/delivery) for status-code handling and
 timeouts.
@@ -106,7 +104,7 @@ integrations should use the Standard headers and the returned `whsec_` secret.
     Implement raw-body verification and safe key rotation.
   </Card>
   <Card title="Delivery and retries" icon="repeat" href="/webhooks/delivery">
-    Understand retries, disabling, history, and replay.
+    Understand retries, timeouts, and endpoint disabling.
   </Card>
   <Card title="Managing webhooks" icon="gear" href="/webhooks/managing-webhooks">
     Configure subscriptions, notifications, secrets, and endpoints.

webhooks/quickstart.mdx

@@ -151,6 +151,6 @@ once, so deduplicate with `webhook-id` even if the first request succeeds.
     See every header and payload field.
   </Card>
   <Card title="Delivery and retries" icon="repeat" href="/webhooks/delivery">
-    Learn the timeout, retry, disable, and replay behavior.
+    Learn the timeout, retry, and endpoint-disable behavior.
   </Card>
 </Columns>

webhooks/troubleshooting.mdx

@@ -3,14 +3,11 @@ title: Troubleshooting webhooks
 description: Diagnose missing deliveries, invalid signatures, retries, and disabled endpoints
 ---
 
-Start by listing the endpoint and its recent delivery history:
+Start by listing the endpoint:
 
 ```sh
 curl "https://spectrum.photon.codes/projects/$PROJECT_ID/webhooks/" \
   -u "$PROJECT_ID:$PROJECT_SECRET"
-
-curl "https://spectrum.photon.codes/projects/$PROJECT_ID/webhooks/$WEBHOOK_ID/deliveries" \
-  -u "$PROJECT_ID:$PROJECT_SECRET"
 ```
 
 ## No requests arrive
@@ -57,15 +54,14 @@ implementation.
 
 At-least-once delivery permits duplicates. A handler can finish its work while
 Spectrum loses the response or reaches its timeout, causing another attempt.
-Manual replay also preserves the original event id.
 
 Use `webhook-id` as a unique idempotency key and acknowledge immediately after
 durably enqueueing the event. Do not wait for slow downstream APIs before
 returning `2xx`.
 
 ## Spectrum keeps retrying
 
-Inspect the final HTTP status and reason in delivery history. Spectrum retries
+Check the responses and errors recorded by your endpoint. Spectrum retries
 `404`, `408`, `429`, `5xx`, network errors, DNS failures, and timeouts. It
 honors valid `Retry-After` values within the four-day retry budget.
 
@@ -96,21 +92,9 @@ curl -X PATCH \
 ```
 
 Re-enabling resumes future delivery and any retries that are still pending in
-the ordered endpoint lane. It does not automatically replay terminal events.
-Filter history with `outcome=dead_lettered` and replay eligible failures after
-the endpoint is healthy.
-
-## Replay is rejected
-
-Replay returns a conflict when any prerequisite is missing:
-
-- the endpoint is disabled or uses legacy delivery;
-- the delivery was not `dead_lettered`;
-- the source event has expired from seven-day retention; or
-- the history row lacks a source sequence.
-
-Enable the endpoint first. If `replayable` is `false`, recover the event from
-your own reconciliation source instead of repeatedly calling replay.
+the ordered endpoint lane. Spectrum does not currently expose terminal delivery
+history or manual replay. Reconcile terminal failures from your own source of
+truth after the endpoint is healthy.
 
 ## Rotation breaks some instances
 

webhooks/verifying-signatures.mdx

@@ -106,10 +106,6 @@ a captured request. Apply both controls:
 2. insert `webhook-id` into a store with a unique constraint before performing
    non-idempotent work.
 
-Manual replay deliberately keeps the original `webhook-id` but receives a new
-signature timestamp. Decide whether an operator-requested replay should be
-ignored, reprocessed, or handled through a separate idempotent recovery path.
-
 ## Rotation without downtime
 
 Call the [rotation endpoint](/webhooks/managing-webhooks#rotate-the-standard-secret)