## Developer webhooks

Use this page to explain event delivery, signature verification, retry behavior, local testing, and the reader expectations around webhook debugging.

{% figure src="/docs-images/gitbook-developers-webhooks.png" alt="GitBook developer webhooks page" caption="The developer webhooks guide gives technical readers one public docs route for event delivery expectations, retry behavior, and endpoint troubleshooting." /%}

## What to document

Cover which event families exist, how endpoints are registered, what retry timing readers should expect, and how delivery failures appear in logs or support conversations. Make it clear which webhook behavior belongs to the public developer surface versus internal admin troubleshooting.

## Current state

Keep webhook docs honest about what is live today. If event catalogs, replay tools, or endpoint self-service are incomplete, say so instead of implying the platform is further along than the code.

## Source of truth

Confirm webhook language against the current Convex paths, GitBook route behavior, and any product-specific event docs before publishing examples that look canonical.