Indie SaaS Public Surface Flow

# Webhook Replay Policy Note

Webhook replay is a small feature that becomes operationally important as soon as customers depend on events. A product may send the right event, but if the receiver is temporarily down, the customer experiences it as data loss. A replay policy note explains what the product will do, what it will not do, and what the customer should design for.

## Minimum policy fields
State the retry schedule, maximum retry duration, signing behavior, idempotency key, event retention window, and manual replay availability. If manual replay is not available, say so. Silence creates false expectations.

## Idempotency is part of the contract
Customers need a stable event id or delivery id so repeated webhook deliveries do not create duplicate actions. If the product cannot provide this yet, the docs should tell customers which field is safest to use for deduplication.

## Failure visibility
A small product does not need enterprise-grade delivery dashboards on day one, but it should offer some way to see failed deliveries. Even a simple event log with response status and timestamp can prevent support threads.

## Example wording
“We retry failed webhook deliveries for 24 hours with exponential backoff. Events are signed with the same secret on replay. Use event_id for deduplication. Manual replay is not currently available.”

## Practical rule
Do not publish webhooks without a replay policy. The policy can be limited, but customers need to know the limit before they build automation on top of the product.

Webhook Replay Policy Note

// COMMENTS

ON THIS PAGE