Replay Webhook

Queue past events for this subscription again, with their original event_id.

Re-sent deliveries carry X-PuntersEdge-Replay: true, restart the retry schedule, and keep the event_id they first had, so a receiver that deduplicates on it ignores what it already processed. At most 1,000 events per call and one call per key per minute; an event already waiting to be sent is not queued twice.

Delivery is at-least-once: the same event can arrive more than once, so deduplicate on event_id (in the body, and sent as the X-PuntersEdge-Id and Idempotency-Key headers). There is no ordering guarantee between events. Each delivery carries X-PuntersEdge-Timestamp, X-PuntersEdge-Attempt and two signatures: X-Webhook-Signature: sha256=<hex> (HMAC-SHA256 of the raw body with your secret) and X-PuntersEdge-Signature: t=<unix seconds>,v1=<hex> (HMAC-SHA256 of <t>.<raw body>; refuse a t more than 5 minutes from now to block replays). Any 2xx answer is success. A 5xx, 408, 429, timeout or connection failure is retried after 1 min, 5 min, 30 min, 2 h, 6 h (6 tries in all, about 8.5 hours), honouring Retry-After up to the next step; any other answer is final. After 10 consecutive undeliverable events, or a day of continuous failure, the subscription is paused and the owner is emailed; POST /v1/webhooks/{id}/resume restarts it with the same secret, and POST /v1/webhooks/{id}/replay re-sends what was missed. The delivery log returns the newest 50 rows unless limit says otherwise.